Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Product Version: 8.6

Last Modified: 20 May 2019

Problem

The Director component installed on a Windows Server fails to start automatically after restarting the service.

Background

On a heavy 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 in the Windows Application log: “A timeout was reached (30000 milliseconds) while waiting for the ServiceName service to connect.”

Workaround

To work around the problem, the Windows Server registry can be modified to increase default time-out value for the service control manager. For details, refer to the Microsoft Knowledgebase article.

  • No labels