This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 28.999999999999996%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECS%3C/text%3E%3C/svg%3E)
VC++ Windows Service (VS2019 Platform toolset, Win SDK 10) is not getting started and displays alert message like "Windows could not start the <service name> service on Local computer.
Error 1053: The service did not respond to the start or control request in a timely fashion".
It is happening after it is getting migrated to Win Server 2019. Same service works fine in Win Server 2012 without any issue. Another vc++ windows services is running fine in the same server. Issue related service is using RPC and other components when compared to the one which works fine.
Have already tried adding ServicesPipeTimeout in registry, Admin mode to run service etc but no luck.
Please suggest if anyone has any clue on this issue.
If the problematic service is dependent on other services have you identified those dependencies to Windows so that it knows to start the problematic service when the dependencies are available?
Hi @RLWA32, When I have checked the existing or current server configuration (win server 2012) the service has only dependency as RPC (Remote Procedure Call). The same is already available in the service available in Win server 2019 and it is in running state as well.
When the service first receives control from the SCM it could spin up a separate thread for its initialization so that it can quickly return service running. Another option while the service is initializing is to use checkpoints and wait hints to keep the SCM from determining that the service has stopped responding.
Hi @RLWA32 We have not made any changes to the code. When I have tried to reinstall in Win 2012 server and try to bring up service in services list, it is running fine. But, the same service is not getting started in Win 2019 server. We have another VC++ windows service which is running fine but only the difference is, it was installed using batch file (<>.exe -install ...) but the issue related service is installed using "sc" command from command prompt. Does the "sc" command has any behavioral issues in Win Server 2019? Or any other clue?
@Chandra Sekhar K, Up to this point you have not provided any specifics about the service that doesn't start. Have you tried implementing any of my previous suggestions regarding service start-up?I don't know what the batch file installation of your service (.exe -install) does so I can't comment about whether that is equivalent to installing your service using the sc command. Since no useful information for diagnosing the problem has been given to us we are left to play a guessing game. Finally, have you tried debugging your service when it is started?
By the way, what value did you use for the registry entry you made for ServicesPipeTimeout?
@RLWA32 Sorry for late reply. After so much analysis, I was be able to resolve the issue. It is due to some application registry setting which is missing. The services which I have mentioned are VC++ 32 bit services developed/migrated to VS2019 couple of months back and you had helped me in resolving issues earlier. I am very thankful for the same. These services are using Visual Studio 2019 toolset and Win SDK 10. I have verified threads and tried to debug the service by keeping logs and got issue with missing registry values. We are using ServicesPipeTimeout registry value as 60000 (decimal). Thanks for giving suggestion on checking the issue and I am able to identify to resolve it too. Please convert your comment posted on Jan 26 to answer so that I will accept it as I have got clue from your post only.
By keeping logs in each code block in service and as suggested by @RLWA32 , I was be able to identify the issue related to one of the application registry setting missing. After that registry key, service has started running without any issue.
Glad to hear that you have resolved the issue. Don't forget to revert the registry change you made for ServicesPipeTimeout.
Thanks. I did the same.