The error message "Windows could not start the NetBackup Database Manager on local computer" and the service specific error 153 are returned when starting the NetBackup Database Manager Service.

Article: 100030828
Last Published: 2015-10-15
Ratings: 0 0
Product(s): NetBackup

Problem

The error message "Windows could not start the NetBackup Database Manager on local computer" and the service specific error 153 are returned when starting the NetBackup Database Manager Service.

Error Message

Windows could not start the NetBackup Database Manager on local computer. For more information, review the System Event log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 153.

Solution

Overview:  
The error message "Windows could not start the NetBackup Database Manager on local computer" and service specific error 153 are returned when starting the NetBackup Database Manager Service (Figure 1).

Figure 1  The Database Manager Service can not be started:

 


Troubleshooting:
As per Figure 2 and Figure 3, the Error Code 153 is present in the System and Application logs of the Windows Event Viewer.

Master Log Files:
Event Viewer
Figure 2  The Event Viewer System log produces the following error
  User-added image
The NetBackup Database Manager service terminated with the following service-specific error: The DosMuxSemWait list is not correct.

Event Viewer
Figure 3 The Event Viewer Application log produces the following error
User-added image
<server name a > is not the primary server <server name b > ... exiting


The cause of the above error message is that the first entry in the server list (located in the registry) is not the name of the Master Server.

This issue may also be seen involving another NetBackup Service other than the Database Manager.
   * Adaptive Server Anywhere - VERITAS_NB - ASA Database service ( NB_dbsrv )
   * Netbackup Client Service ( bpcd )
   * NetBackup Compatibility Service ( bpcompatd )
   * NetBackup Device Manager ( ltid )
   * Netbackup Enterprise Media Manager ( nbemm )
   * NetBackup Job Manager ( nbjm )
   * NetBackup Notification Service  ( nbnos )
   * Netbackup Policy Execution Manager ( nbpem )
   * Netbackup Request Manager ( bprd )
   * NetBackup Resource Broker ( nbrb )
   * NetBackup Service Layer ( nbsl )
   * NetBackup Service Monitor ( nbsvcmon )
   * Netbackup Volume Manager ( vmd )
   * Veritas Private Branch Exchange ( pbx_exchange )


Resolution:
Perform the following on the Master Server:
1. Open the registry using regedt32 and browse to HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config\Server (Figure 4) .
2. Double click on the Server value within this key (Figure 5).
3. Change the order in which the servers are displayed so that the Master Server is first .  Click OK.
 
Note: Regedit screens may vary in appearance between Windows versions.

Figure 4 

  User-added image


Close the registry editor, and STOP any NetBackup Services which might be running.
Start NetBackup services.

The NetBackup Database Manager service should no longer produce the error.

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.
 

 

Was this content helpful?