Issue
K2 service is not starting automatically after the server rebooted. There are no issue with starting the K2 service manually.
Resolution
Please note that the resolution here only applies to scenario where your K2 service can start without any errors, but Windows is not starting the service automatically after rebooting the server. If you encounter errors while starting your K2 service, please reach out to Nintex Support for assistance.
If your have production license, Windows will attempt to start the K2 service just like how it attempts to start all other automatic services. If you notice Windows is not starting the K2 service automatically, you can try the following to see if it helps resolve this issue.
- Check if K2 Configuration Service has started. K2 service requires the K2 Configuration Service to be started first. If the K2 Configuration Service is not started first, then Windows will not be able to start the K2 service. You can try starting the K2 Configuration Service manually and see if it starts. If it is unable to start, please reach out to Nintex Support for assistance.
- If the K2 Configuration Service and K2 Server service can be started manually, but for some reason Windows is not able to start them automatically, then try the following:
Open services.msc, right-click on K2 Configuration Service, go to Properties, and change Startup Type to 'Automatic (Delayed Start)'. Do the same for K2 Server service. This basically tell Windows to start the K2 Configuration Service and K2 Server 2 minutes after all other automatic services have started.
- You can consider configuring Recovery options for K2 Configuration Service and K2 Server to force Windows to attempt to start the services if they fail to start.
- Check your Event Viewer for logs that indicate why Windows is unable to star the service.
Windows is responsible for starting the services if you have configured them to start automatically. Depending on your server setup and the number of services you have running on your server, it is not uncommon to see Windows not being able to start the K2 services when it is booting up. In that case, configuring Windows to perform a delayed start for the K2 services can help to resolve the issue.
