EMM interface initialization failed, status = 334

[Michal_Mikulik]

Hello,

NetBackup 6.0, Windows 2k3 Master, Windows&UNIX Media Servers.

I receive error "EMM interface initialization failed, status = 334" in Event Viewer on Windows Media Servers and in Messages file on UNIX media server (each 2 minutes).Consequence is that media servers are not able to propagate to Master, so you are not then able to run device config wizard etc.
Also, vmd on media servers shuts down after a few minutes post start.

In NetBackup logging (volmgr\debug\ltid) on both platforms, I receive following detailed errors:


00:07:05.813 <16> emmlib_initializeEx: (-) Failed to resolve EMM server reference
00:07:10.821 <16> InitLtid: (-) Translating EMM_ERROR_CorbaResolveReference(3000005) to 334 in the device management context
00:07:10.821 <3> logstderrmsg: EMM interface initialization failed, status = 334

I tried to configure EMM server entry in registry on Media servers as hostname, FQDn, IP adress, but result is the same.

Michal

[Michal_Mikulik]

Hello,

Some amendments:
Backups of Media servers (through LAN like clients) work. Both-direction ping etc. work.
Also, error persists after MP1 applying.
Next, error always appear after 120 sec timeouts (so ltid cycles in 120 sec timeout cycles).

Michal

[Brian_Beaulieu]

Hi Michal,

Any solution to this? I get the same error on Windows after an upgrade from 5.1MP3 to 6.0.

Regards,

Brian

[Justin_Curry]

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

[Michal_Mikulik · Accepted solution]

It was only misconfiguration.
Media Server entries were missing on Master Server.

Michal

[Raghuraam]

My issue got resolved after applying Michal's advice.

Thankyou Michal to share the solution.