Error Message: “Windows could not start the ColdFusion 10 Application Server on Local Computer. For more information review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 0. “
MAXIMUM JVM HEAP SIZE ALLOWED IN A 32-BIT OPERATING SYSTEM.
Error Cause: Allocating 1844 MB or more for ‘Maximum JVM Heap Size (in MB)’ in ‘Java and JVM‘ Settings of CF Admin on a 32-bit processing system.
Note: Any value, greater than 1844, in a 32-bit OS, for Max JVM Heap Size would cause the issue mentioned.
At times, we get errors specifying that the process is running short of JVM Heap memory. So we increase the Max JVM Heap size through CF Administrator. But increasing the Max size, without knowing its boundary value, would land up in getting the issue mentioned below:
Try changing the ‘Maximum JVM Heap Size (in MB)’ value in ‘Java and JVM’ settings of CF Admin to any valuehigherthan1844on a 32bit operating system.
Then click on Submit. An alert appears, as shown below, which asks for a ColdFusion Service restart.
Open Services.msc and try restarting the ColdFusion service.
It throws an error as shown in the below screenshot:
The only way, this issue can be fixed, is by changing the jvm.config file.
Go to CF Installation directory like “C:\ColdFusion10\cfusion\bin\” and there you will find a file jvm.config.
If the file is not found, search for jvm.config file in the installation directory.
Open this file in Notepad and search for “Arguments to VM”.
Change the value after–Xmxto a value less than1844.
Save the file and then restart the ColdFusion Service.