restarting the ColdFusion 10 Application Server

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.

/charlie