| Event Id | 0 |
| Event Source | NetBackup Device Manager |
| Description | EMM interface initialization failed, status = 334 |
| Event Information | According To Veritas: Troubleshooting: Several symptoms listed below all point to a similar problem. Master Log Files: 1. The open database connectivity (ODBC) Data Source Administrator, under Administrative Tools > Data Sources (ODBC), shows VERITAS NB Adaptive Server Anywhere 9.0.1 as "Not marked" in the Version and Company fields on the Drivers tab. 2. The NetBackup Device Manager service will display this error in the Application Event Log 3. The services called NetBackup Enterprise Media Manager and NetBackup Resource Broker dont error, but wont remain started. 4. The command line process \<InstallPath>\VERITAS\NetBackup\bin>nbdb_ping fails with, "Database [NBDB] is not available." 5. The log \<InstallPath>\VERITAS\NetBackup\logs\admin records this error after the failed nbdb_ping: 14:03:37.687 [3612.540] <16> nbdb_ping: ODBC connection failed. 14:03:37.687 [3612.540] <16> nbdb_ping: ErrMsg Specified driver could not be loaded due to system error 126 (VERITAS NB Adaptive Server Anywhere 9.0.1)., ErrCode -1, Sqlstate IM003 6. The VXUL Logs will show this sequence of errors: (syntax used to collect the log sample: vxlogview -t 00:10:00 -d all) 2/7/2006 18:58:55.104 [Diagnostic] NB 51216 nbemm 111 PID:3752 TID:3744 [No context] 1 V-111-1049 [ConnectionManager::OpenConnection] EMMServer generic error = Cant connect to the database (Specified driver could not be loaded due to system error 126 (VERITAS NB Adaptive Server Anywhere 9.0.1). <-1> ) 2/7/2006 19:26:20.661 [Debug] NB 51216 nbrb 118 PID:3852 TID:740 [No context] 1 [RBDatabase::connectDatabase()] ODBC connection failed. ErrMsg: Specified driver could not be loaded due to system error 126 (VERITAS NB Adaptive Server Anywhere 9.0.1). ErrCode: -1 DBErrCode: 160 Sqlstate: IM003 2/7/2006 19:26:20.661 [Application] NB 51216 nbrb 118 PID:3852 TID:740 [No context] [Critical] V-118-55 Unable to connect to database. Ne |
| Reference Links | GENERAL ERROR: The services called NetBackup Enterprise Media Manager and NetBackup Resource Broker dont error, but wont remain started and the NetBackup Device Manager service generates event log error, "EMM interface initialization failed, status = 334" |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.