error 1053 the server did not respond to the start or control request in a timely fashion

William Kent 1 Reputation point
2020-11-10T01:22:28.767+00:00

I have installed a Windows Service on Windows Server 2019 DataCenter that we used on Windows Server 2016 DataCenter and configured it identically. Logon is as Administrator.

But it fails to start.

Have tried increasing the ServicesPipeTimeout but it still fails to start... error 1053 the server did not respond to the start or control request in a timely fashion

What could have changed in Windows Server 2019 to cause the error?

Windows Server Setup
Windows Server Setup
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
243 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Carl Fan 6,836 Reputation points
    2020-11-10T08:44:06.957+00:00

    Hi,
    This message does not indicate that an error has actually occurred within the service. It simply means that the Services snap-in has timed out.
    First make sure the computer where the Laserfiche Server will be installed is first fully up to date with Windows updates. Reboot as necessary.
    Also it may related to your code rather than the framework. Did you publish service while it was in debug mode?
    You can use the Windows Event Viewer to see what happens when you start your Windows Service.
    Event Viewer >Windows Logs and then Application
    The service could run fine on Windows Server 2016, but we can’t confirm if it is compatible with Windows Server 2019.
    Hope this helps and please help to accept as Answer if the response is useful.
    Best Regards,
    Carl

    1 person found this answer helpful.
    0 comments No comments

  2. William Kent 1 Reputation point
    2020-11-26T06:58:23.973+00:00

    What Laserfiche Server got to do with this?

    So no known Windows 2019 issues when running a service that has worked ok on all previous versions?

    0 comments No comments