Skip to content
English
  • There are no suggestions because the search field is empty.

Shinydocs Control Center service times out when starting (Error 1053)

If the Shinydocs Control Center service doesn’t start and Windows shows this message, Windows stopped waiting before Control Center finished starting: Windows …

If the Shinydocs Control Center service doesn’t start and Windows shows this message, Windows stopped waiting before Control Center finished starting:

Windows could not start the Shinydocs Control Center service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion.

In Event Viewer, under Windows Logs > System, you may also see event 7000, 7009 or 7011 from Service Control Manager for the same service.

Why it happens

Each time it starts, Control Center brings its database up to date before it tells Windows that it is running. The first start after an upgrade has the most to update, so it takes the longest. A busy server, or security software scanning Control Center’s files, slows it down further. If this takes longer than Windows is willing to wait, Windows reports the error.

Give services more time to start

Raise the time Windows waits for a service to start to 2 minutes (120,000 milliseconds). This is a Windows setting, ServicesPipeTimeout, described in Microsoft’s article A service does not start, and events 7000 and 7011 are logged in Windows Server.

[!WARNING] You need to be a local administrator on the Control Center server. The setting applies to every service on that server, and it takes effect only after a restart, so plan the restart with whoever manages the server.

  1. On the Control Center server, open Command Prompt or PowerShell with Run as administrator.
  2. Run this command: PowerShell
    reg add "HKLM\SYSTEM\CurrentControlSet\Control" /v ServicesPipeTimeout /t REG_DWORD /d 120000 /f 
  3. Restart the server. Windows reads this setting only when it starts.
  4. After the restart, open Services (services.msc) and check that Shinydocs Control Center shows Running. Then open Control Center at https://localhost:9701 or your custom Control Center address.

To use Registry Editor instead, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control. If there is no ServicesPipeTimeout value, create one: Edit > New > DWORD (32-bit) Value. Set it to 120000 with Decimal selected, then restart the server.

If it still doesn’t start
  • Check that your security software excludes the Shinydocs folders and processes. See Endpoint and Security Software Considerations in the Shinydocs Pro Pre-Installation Checklist.
  • Don’t keep raising the timeout. Microsoft recommends finding the cause instead, because a longer wait can hide another problem.
  • Contact Shinydocs Support. Include the time the service failed to start and the Service Control Manager events from Event Viewer.