-
Notifications
You must be signed in to change notification settings - Fork 91
Description
Create a sidekick service in Windows Server 2016, but cannot start, error code 1053 is returned
Expected Behavior
The service can start normally
Current Behavior
In Windows Server2016, I use sc to create a service. The command is as follows:
sc create sidekick binPath= "C:\Users\Administrator\Desktop\sidekick\bin\sidekick.exe --insecure --key C:\Users\Administrator\Desktop\sidekick\certs\private.key --cert C:\Users\Administrator\Desktop\sidekick\certs\public.crt --address :44090 --health-path /minio/health/ready https://127.0.0.1:44090" type= own start= auto DisplayName= "sidekick" , the service type is LocalSystem, prompt when starting the service: The service did not respond to the start or control request in time, the error code is 1053
Possible Solution
Steps to Reproduce (for bugs)
-
check the system event log, Modify the registry ServicesPipeTimeout to 12000ms.
-
Log in to the machine as administrator, manually execute the service start command, and it can run normally, the command:
C:\Users\Administrator\Desktop\sidekick\bin\sidekick.exe --insecure --key C:\Users\Administrator\Desktop\sidekick\certs\private.key --cert C:\Users\Administrator\Desktop\sidekick\certs\public.crt --address :44090 --health-path /minio/health/ready https://127.0.0.1:44090 -
startup failed like this:
sc start sidekick
Context
Regression
Your Environment
- Version used (
sidekick version): v7.0.2 - Environment name and version (e.g. nginx 1.9.1):
- Server type and version: Windows Server 2016 amd64
- Operating System and version (
uname -a): Windows Server 2016 - Link to your project: