Backup Exec services don't start automatically after the backup exec server is rebooted

book

Article ID: 100044967

calendar_today

Updated On:

Description

Error Message

Cause

The Service Control Manager (SCM) uses default time-out value of 30 seconds for service communication. It is possible that some application services could take a longer time to start which causes SCM to time-out and services may not start automatically.

Note: This may also affect the other application services (set to automatic startup) on the Backup Exec Server.

Resolution

Resolution #1:

Increase the timeout value for the service startup.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

1. Open the registry (Start - Run - REGEDIT or REGEDT32) and browse to the path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

2. Create a new DWORD Value if it does not exist already:

ServicesPipeTimeout

3. Set the Value Data to:

120000 (decimal)

Note: The above decimal value is 2 minutes. It can be further increased to 240000 which is 4 minutes. 

 

Resolution #2:

This may not be necessary if resolution #1 has solved the problem, however if not, change the service Startup Type from "Automatic" to "Automatic (Delayed Start)" for those services that still have an issue after making the registry change outlined in Resolution #1 above..

Issue/Introduction

Backup Exec services don't start automatically after the backup exec server is rebooted, even though the startup type is set to Automatic. However, the services can be started manually.