Last Modified: 20 May 2019
The Director component installed on a Windows Server fails to start automatically after restarting the service.
On a heavy heavily loaded system configuration, the Java launcher for Windows that starts the Director component as a Windows service may not respond to the service control manager in time.
In this case, the NAKIVO Backup & Replication Director service will not start automatically after restarting the service, and the following error event will appear appears in the Windows Application log: “A timeout was reached
A timeout was reached (30000 milliseconds) while waiting for the ServiceName service to connect
To work around the problem, the Windows Server registry can be modified to increase the default time-out timeout value for the service control manager. For details, refer to the Microsoft Knowledgebase Knowledge Base article.