Enterprise Media Manager (EMM) Service will not start, getting status 334: EMM interface initialization failed in the Admin Console or status 77: Unable to connect to the EMM Server

Enterprise Media Manager (EMM) Service will not start, getting status 334: EMM interface initialization failed in the Admin Console or status 77: Unable to connect to the EMM Server

Article: 100022897
Last Published: 2013-08-29
Ratings: 0 0
Product(s): NetBackup

Problem

Enterprise Media Manager (EMM) Service will not start, getting status 334: EMM interface initialization failed in Windows or Java Admin Console or status 77: Unable to connect to the EMM Server

Error Message

EMM interface initialization failed
Unable to connect to EMM Server

Solution

Overview:
When opening the Windows NetBackup Administration Console, status code 334 (EMM interface initialization failed) is reported.

Troubleshooting:
nbnos and nbemm services do not stay started on reboot or service stop/restart.
nbdb_ping test responds normally.
Upon checking the registry, USE_VXSS was found set to "AUTOMATIC" even through VxSS was neither installed nor configured.

Resolution:
1. Stop NetBackup services.

2. With regedit, browse to:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config
For UNIX systems, this is found in:
/usr/openv/netbackup/bp.conf

3. Change the USE_VXSS entry to "PROHIBITED" and save.

4. Restart NetBackup services.

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?