How to create Service for ColdFusion

Ever landed into a situation, where the installation or instance creation was successful, but ColdFusion Service was not created on windows. Don’t, panic. Here is the tweak.

  1. Launch Command prompt as Administrator
  2. Run this command sc create “ColdFusion 11 Application Server” binPath= C:\ColdFusion11\cfusion\bin\coldfusionsvc.exe start= auto DisplayName= “ColdFusion 11 Application Server”

Now you will be able to locate your instance through the Windows Services Manager. For ColdFusion 10, replace “11” with “10” in the above command. For specific instance the instance name should be appended. Say the instance name is CF11, then the command changes to

sc create “ColdFusion 11 Application Server CF11” binPath= C:\ColdFusion11\CF11\bin\coldfusionsvc.exe start= auto DisplayName= “ColdFusion 11 Application Server CF11”


7 thoughts on “How to create Service for ColdFusion

  1. hi anit. i have a scenario where my coldfusion 9 application server disappears from services list yesterday. i tried looking at bin folder however coldfusionsvc.exe is not there either. i have been running the server for over a year and it has all along been fine. any idea why that happens?


  2. This information will not be there in CF logs. Did you get a chance to look at Windows Event viewer logs (System & Application)? Event viewer logs would definitely have some relevant info.


  3. Hi Anit, thanks for this. But do you have any more on what led to the need to do this workaround (of the SC command)? And is it that you found that the coldfusionsvc.exe approach to create the service had failed also?

    I hit this very issue with someone, for the first time in years of helping install CF10, 11, and 2016. It was on CF11, on Windows 2008. The instance would be created (via Instance Mgr), but no service would be created. We looked in the CF logs (for cfusion and the instance) as well as the event logs, but found no evidence of the problem.

    So of course we tried to run the “coldfusionsvc -install” command to create the instance, but that failed also with an error (“createService failed with error status 123”). In googling for that, the only other reference to that specific error was a single CF forum thread, where the person ended up also just punting and doing the SC command.

    (Curiously, they had been trying the coldfusionsvc because they had NOT thought to check the “windows service” checkbox when creating their instance. So not the same problem but perhaps they would have hit the same problem I did if they had, and perhaps it’s the same one that led you to create this post. 🙂

    So I suppose whatever was making that command-line coldfusionsvc fail was also what made the create of the service in Instance Manager fail. But the question is, what is the cause?

    Did you happen to find any more, before you posted this workaround? It’s disconcerting, of course, to have something not work. I will add that this is a pretty tight security environment in which this client is trying to create these instances. Any thoughts appreciated.


  4. Following up my last comment, we found that in our case, the problem was that the cfusion instance (where we were running the instance manager to create instances) was set to run (in Windows Services) as a user that did had limited permissions. When we changed it to run as “local system”, then the service for a new instance WAS created. Hope that may help someone else.


  5. Yes Charlie, “coldfusionsvc -install” command is the alternative to SC create. But, that didn’t help then to create the services. I don’t recall the error, we got then. I was not able to figure out the root cause, unfortunately. It was only happening only on one out of five servers, the user had.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s