cancel
Showing results for 
Search instead for 
Did you mean: 

EMM interface initialization failed, status = 334

Cesar_Almada
Level 3
Partner Accredited

Moved to new discussion from https://www-secure.symantec.com/connect/forums/emm-interface-initialization-failed-status-334-3

i have the same problem

but the nbdb_ping command showme the database is runing with out problem

C:\Program Files\Veritas\NetBackup\bin>nbdb_ping.exe
Database [NBDB] is alive and well on server [NB_xxxx]

in the aplication log of my windows 2008 server showme

Faulting application name: nbemm.exe, version: 7.0.2010.707, time stamp: 0x4c358660
Faulting module name: MSVCR80.dll, version: 8.0.50727.4940, time stamp: 0x4ca2b4dd
Exception code: 0xc000000d
Fault offset: 0x0000000000089120
Faulting process id: 0x1d48
Faulting application start time: 0x01ccd39a0900b185
Faulting application path: C:\Program Files\Veritas\NetBackup\bin\nbemm.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\MSVCR80.dll
Report Id: 4fad640a-3f8d-11e1-bcc1-d485647b1a1c

1 REPLY 1

VirtualED
Level 5
Employee Accredited Certified

If nbemm is crashing, I would probable recommend you contact NetBackup support.

But before that, verify you have page file properly configured.  Meaning it should be set to Windows recommended value or have Windows manage the page file?

Verify you have more than 10% freespace on the drive that netbackup is installed.

We need to understand if the Enterprise Media Manager service will run for a while and then crash?  Or does it crash upon startup?

I do not know about any issues with EMM crashing since 6.5.3.1.