Follow

arcserve-KB : ASBU | Backup Server || r17/17.5 services are not started automatically after reboot of Windows Server 2016

Last Update: 2017-11-20 17:46:59 UTC
Problem: Arcserve Backup r17/17.5 services are not started automatically after reboot of Windows Server 2016.

Error Message: After reboot  the server unable to access Arcserve Backup Manager. When open Services.MSC you will find below are the Arcserve services which are not running including SQL Server (Arcserve_DB)





If observed the Event logs, you will see the timeout errors:
Log Name:      System
Source:        Service Control Manager
Date:          21-02-2017 08:24:03
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WIN2016TEST.ARCSERVE.COM

Description:
The MSSQL$ARCSERVE_DB service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Log Name:      System
Source:        Service Control Manager
Date:          21-02-2017 08:24:03
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WIN2016TEST.ARCSERVE.COM

Description:
A timeout was reached (30000 milliseconds) while waiting for the MSSQL$ARCSERVE_DB service to connect.
Cause:
The Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all installed Windows services. By default, the Service Control Manager will wait 30,000 milliseconds (30 seconds) for a service to respond. However, certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start and report ready to the Service Control Manager.

Solution:
Therefore, to overcome this issue, we can make a registry tweak by editing or creating the ServicesPipeTimeout DWORD value. The Service Control Manager timeout period can be overridden, thereby giving the service more time to start up and report ready to the Service.

Steps to Perform:
Modify the registry to increase the default time-out value for the service control manager. To increase this value to 60 seconds, follow these steps:

1. Click Start > click Run > regedit.
2. Locate and then click the following registry subkey:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. In the right pane > locate ServicesPipeTimeout entry.
4. On the Edit menu > point to New > DWORD Value.
5. Type ServicesPipeTimeout, and then press ENTER.
6. Right-click ServicesPipeTimeout, and then click Modify.
7. Click Decimal, type 60000, and then click OK(This value represents the time in milliseconds before a service times out).
8. Restart the computer.

Note: If the ServicesPipeTimeout entry does not exist, you must create it by referring to the steps from 4 to 7.



After rebooting the server, you will find all the services are up and running.



​​

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments