EMM interface initialization failed, status = 334

[stephen_frasset]

Has anyone received the above error "EMM interface initialization failed, status = 334"? I am getting it constantly in the Application log of Event Viewer. My server is a 64-bit Windows Server 2K3. This error is causing Netbackup 6 MP4 to not be able to access any storage devices, causing my backups to not start or me to modify any settings.

I have an open case with Symantec, but do not have a resolution yet.

[zippy]

Stephen,

Search my ID, I am almost sure I had the same problem 5 or 6 months ago. While you look I will too.

[zippy]

http://forums.veritas.com/discussions/thread.jspa?threadID=60400

http://seer.support.veritas.com/docs/281817.htm

http://seer.support.veritas.com/docs/284616.htm

http://www.tek-tips.com/viewthread.cfm?qid=1298344&page=1

http://www.google.com/search?hl=en&q=EMM+interface+initialization+failed%2C+status+%3D+334&btnG=Google+Search

[Dennis_Strom]

Sometimes you can fix it by stopping netbackup, then stopping pbx then starting pbx then starting netbackup.

[Sathyam_G]

Hi,

I am also facing the same problem. I have already installed NB 6 with MP 4 on w2k3 R2 with HP MSL 6060 drives (2 no's ) in SAN.

Now i am trying to add 2 linux servers as SAN media server with NB6. The OS is RedHat Linux Advance server version 4.

I am able to see the drives from the OS as well as locally if i run the command

#scan -tape
but also gives " unable to intialize device mapping file, satus=77)


#tpconfig -d also gives the same error message "" unable to intialize device mapping file, status=77"

I have added linux server as a media server using "nbemmcmd "command . I am not able to detect the drives and robots in the device config wizard from master server.

Logs shows "EMM intialization failed"

Other windows SAN media servers are working fine.

Kindly help to solve this.

Sathyam G

[Stumpr2]

can the OS see them?