Install Best Practices

Related Categories: ColdFusion

This was originally posted to the AZCFUG mailing list. I will update the contents momentarily.... I’ve done multiple installs on my Win2K3 box with no problems. I have CFMX 6.1 Server and CFMX 6.1 J2EE (on JRun4, WebSphere, and SunONE) running with no problems. I even had CF 5.0 thrown into this mix at one point in time. We have seen instances where the installer incorrectly lays down the Hotspot JVM which causes the Web Server Connector tool to fail (an Entry point error: “The procedure entry point JVM_GetClassAccessFlags@8 could not be located in the dynamic link library jvm.dll”) which is addressed in TechNote 19216 (http://www.macromedia.com/support/coldfusion/ts/documents/entry_point_error.htm). Other best practices:

1. Disconnect from the internet (sounds silly but this can prevent port issues)
2. Disable anti-virus (may need to shutdown the service instead of just disabling real-time file checking)
3. Install CFMX Server in stand-alone mode (internal web server), then go back and configure web server connections after completing the Configuration wizard. This step will help diagnose problems by eliminating the web server & connector – Tech Support will appreciate you 
4. Set the proper permissions for the CFMX service account user (default: SYSTEM or LocalSystem). Give this user FULL CONTROL on the entire cfroot (e.g. C:\CFusionMX), read and execute permissions on Windows SYSTEMROOT (e.g. C:\Windows) and SYSTEMROOT\SYSTEM32 (e.g. C:\Windows\System32).
5. Once permissions are set and you have completed the Configuration Wizard, ensure the CF service account has full control on the connector module (e.g. cfroot\runtime\lib\wsconfig\n\jrun.dll).

Comments (0) | Print | Send | del.icio.us | Digg It! | Linking Blogs