"The mind of a Mad Tech!"

On extremely slow or very heavily loaded Windows systems, the main ColdFusion MX Application Server service might not automatically start on system restart using the default service startup timeout values. Instead, the following error will be seen:

 The ColdFusion MX Application Server service terminated with
 service-specific error 2.

This behavior can occur on slower systems or systems with a large number of services that need to initialize at the same time, causing the ColdFusion MX Application Server service to timeout.

Beginning with ColdFusion MX 6.1, the -starttimeout switch is added to the command line executable, allowing the startup timeout value to be permanently modified.

If the ColdFusion Application Server Service does not start on system reboot, the following workaround can be used to modify the time allowed for service startup:

1. Shut down the ColdFusion MX Application Server service.
2. Open a DOS command window.
3. Run the following command to change directories:

    cd cf_rootruntimebin

4. Run the following command to change the timeout value:

    jrunsvc.exe -starttimeout 900"ColdFusion MX Application Server"

   where 900 is equal to the number of seconds allowable before the ColdFusion service startup will timeout.

   This value can be adjusted according to the specific needs of the system on which ColdFusion is installed. To change it, simply run the command in step 4 again with a different value. You can replace “ColdFusion MX Application Server” accordingly depaending on the CF instance. For example if it is CF8, you would run jrunsvc.exe -starttimeout 900“ColdFusion 8 Application Server”.

This entry was posted on Wednesday, May 7th, 2008 at 6:28 am and is filed under ColdFusion. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.