Problem

STATUS CODE 153: 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
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 Application log notes the 153 error:

Figure 3 The Event Viewer System log notes the 153 error:

Additional Event Application error messages: Event id 0 : Failed to validate this host with the EMM server Event id 516 : <server name > is not the primary server <server name> ... exiting

One 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. On 6.0, for example, this may be any of the following services: * 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\Serv er (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 (Figure 6). Click OK. Note: Regedt32 screens may vary in appearance between Windows NT, 2000, and 2003. Figure 4 Server tuvok precedes francesco, but francesco is the Master Server and should be first:

Figure 5 The Server value has been opened for editing:

Figure 6 The Server value has been changed to place francesco, the Master Server, first:

Close the registry editor, and start the NetBackup Database Manager service. 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.