I am having a problem with restarting the ColdFusion 10 Application Server.
Normally this happens onze a year and restarting the service resolves it.
the window message says it is a non-Microsoft service an I have to refer to service-specific error code 2.
If you are on Windows platform, then run command prompt as run as Administrator and Remove Adobe ColdFusion 10 Application Server service using the command mentioned belo
sc delete "Adobe ColdFusion 10 Application Server"
Create the service once again from the command mentioned below
sc create "Adobe ColdFusion 10 Application Server" binPath= "C:\coldfusion10\cfusion\bin\coldfusionsvc.exe" displayname= "ColdFusion 10 Application Server" start= auto
NOTE: Make sure you run command prompt as run as Admin
Woah, hold on there. I’d say don’t go removing the service (as Vishu has proposed) until you’ve explored if there may be some other explanation.
Look first at the ColdFusion-out.log and ColdFusion-error.log, in the coldfusion10\cfusion\logs folder (and if you’re on Enterprise/Trial/Dev editions and have created a new instance, look in the coldfusion10\instancename\logs. You may find why it can’t start. And check also the Windows Event Viewer and its application or system logs (they may only point you to the CF logs, but it’s still worth a look).
And @DDo, are you saying “nothing has changed”? Nothing? Not in the windows service definition, like changing the user that starts CF? Nothing in the CF Admin (like a setting that may only take effect upon restart)? And when was the last time that you DID restart it? If it’s been weeks or months, then you or someone could have changed something you may not be considering. Check also the new audit.log (in the CF logs), which since CF10 tracks many (but not all) changes in the CF Admin. Did anyone tweak the jvm.config since the last restart?
Finally, you could also try starting CF from the command prompt, though note that that will run it as the user who is logged in, which may not be the same user it would run when started as a service. You may see something in the console messages that could explain what’s amiss. But again the out log referred to above is the place where CF writes the same log info when started as a service.
But seriously: check the logs before jumping to rebuilding the service. I don’t even see, Vishu, what doing that would really do to help the problem. Do you offer it because this sounds like something where such a recreation of the service DID solve the problem? Was there any additional diagnostic information that prompted that? Or a lack of any, perhaps? Just trying to help others who may read this some day.
Hi Charlie (and VJ),
Removing/re-creating the service is not really in issue... It's easy enough ; )
As expected, it did not resolve the issue.
CF logs didn't provide any useful information and the messages in Windows Event Logs aren't very descriptive either...
Running 'coldfusion.exe -start -console' produces a MS Visual C++ Debug Library popup (and the same Windows Event that is logged when starting the ColdFusion Application Server via the Services Management Console):
This application has requested the Runtime to terminate it in an unsual way.
Please contact the application support team for more information.
(Press Retry to debug the application)
I'm starting to think the cause might have something to do with MS Visual C++ (or perhaps other OS related issues?!) rather than ColdFusion... But that's just a hunch.
Fortunately, the server is a virtual machine so with a snapshot in place we have a little more flexibility in trying out different strategies (restoring a system backup, reinstalling CF). If all else fails, we will just have to rebuild from scratch.
Hopefully, it won't come to that!
@Rudi, so to be clear, you had said at the outset that this was a random, occasional problem. Is it now happening consistently (you can no longer start CF)?
Also, since you mention visual c++, what update of CF10 are you on? You don’t mention. While the error you relate doesn’t directly connect to it, there was an issue with itCF10 update 14. Can you let us know if perhaps this is the issue and solution:
If you have more questions about that in particular, do see the comments there for questions and answers in case they may answer them.
Otherwise, let us know how it goes.
Excuse the late reply. We have been busy getting the server up-and-running. We tried different approaches but eventually we removed CF10 and reinstalled it (incl. update 14 and update 15). That solved the problem (obviously, my hunch about Visual C++ turned out to be wrong ;). FYI, we were running CF10 w/update 14 (both MS Visual C++ 2008 and 2012 redistributable installed).
Of course, after reinstalling we had to configure the server from scratch. A bit of a pain but with a nearly identical test server to check the settings it wasn't too bad.
In the end nobody died and no revenue was lost .
Thanks for support!