Windows ColdFusion|Jrun weirdness.

Question

We are running ColdFusion 9 on a Windows 2003 web server a in multi-home configuration.
We have four ColdFusion services configured on our system: cfusion, general, pur, and playground.  Looking at the Windows Services panel only the cfusion and playground ColdFusion services are started.  When we tried to start the other two, they fail to start with the following message in the Windows Event logs: "The ColdFusion 9 AS General service terminated with service-specific error 2".
So I started to search for more information about this.  During my research, I thought why not try the ColdFusion Enterprise Manager Instance Manger page in the ColdFusion Administrator.  This is where things become a bit wierd.  All the instances are running according to the Instance manager.  And further testing seems to confirm that this is true.  All the administrator pages work, applications running against each instance are working.  They seem to all be running.
Using the Microsoft|Sys Internals Process Explorer tool, we can see that there are only two jrunsvc processes running, the one for the cfusion instance and the one for the playground instance.  But there are four jrun.exe processes running.  How is this possible?
Looking at the properties of the processes with the Explore tool, we see that the jrun.exe processes that match the jrunsvc have this string:
jrun.exe -config jvm-cfusion.config -nohup -ntservice "ColdFusion 9 Default CFusion-StartEvent" -startByNTService "cfusion"
The two jrun.exe process that do not match a jrunsvc have this string: E:\JRun4\bin\jrun.exe -nohup -start -childVM pur
Can anybody provide some insight what all of this means?

Answer 1

Thank, I'll keep that bit of info in mind.  These do use custom configuration files, but they had not been modified since the server last started correctly.
Doing some more research it sounds like "Error 2" is rather a catch all error for non-starting ColdFusion services.  Our particular problem turned out to be a Network Interface Card (NIC) condfiguration problem.  The server had recently had it's wiring re-configured and they pluged the network cable into a different NIC port, instead of the original one that had a "static" ip configured.  The new NIC was configured to use a DHCP reserved IP of the same value as the static NIC.  This apparently really confused the windows server when it started up and took some amount of time for the poor machine to figure itself out.
Apparently too long for the two ColdFusion services that where configured to log on as a domain user and thus the user could not be authorized by the network controller and the services failed to start.  But by the time a human was notfied of all these problems, the machne had straightend itself out and was sucessfully connected to the network.  The services could be started manually by then with no problem.
Once we traked all that down and straightend out the NIC cards, the server started up just like it is supposed to. and all the CF Services start with no problems.