NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 334

NetBackup status code : 334
HOWTO104246 | 2014-11-20
How To | CMS-XML

GENERAL ERROR: The services called NetBackup Enterprise Media Manager and NetBackup Resource Broker don't error, but won't remain started and the NetBackup Device Manager service generates event log error, "EMM interface initialization failed, status = 334"

status 334 : EMM interface initialization failed. v-118-55 Unable to connect to database.
TECH46255 | 2014-04-09
Technical Solutions | CMS-XML

Unable to start the EMM Service, EMM interface initialization failed, status = 334

Unable to start the EMM Service, EMM interface initialization failed, status = 334
TECH185381 | 2014-01-20
Technical Solutions | CMS-XML

If nbdb_upgrade step fails during upgrade, NetBackup Administrators will see errors stating "unable to connect to EMM server (77)" and "EMM interface initialization failed, status = 334" while accessing many different areas of the GUI

Status 77 Status 334
TECH54607 | 2013-09-20
Technical Solutions | CMS-XML

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
TECH83777 | 2013-08-29
Technical Solutions | CMS-XML

Getting error "EMM interface initialization failed, status = 334"

TAO exception, minor code = 3e (timeout during send; low 7 bits of errno: 62 Timer expired), completed = NO 10:44:42.145 [15686] 16 InitLtidEMM: (-) Translating emm_error_corbatimeout(3000002) to 334 in the device management context 10:44:42.146 [15686] 3 logstderrmsg: EMM interface initialization failed, status = 334
TECH158081 | 2012-01-25
Technical Solutions | CMS-XML

DOCUMENTATION: When connecting to host properties/master server, the following error are received: "unable to connect to EMM server (77)" and "EMM interface initialization failed, status = 334"

DOCUMENTATION: When connecting to host properties/master server, the following error are received: "unable to connect to EMM server (77)" and "EMM interface initialization failed, status = 334 "
TECH51026 | 2011-05-24
Technical Solutions | CMS-XML

GENERAL ERROR: EMM interface initialization failed, status = 334

334
TECH48921 | 2008-01-06
Technical Solutions | CMS-XML

STATUS CODE 334: The Enterprise Media Manager (EMM) Service fails to start. "EMM interface initialization failed" appears in the Activity Monitor.

status 334 : EMM interface initialization failed
TECH48700 | 2007-01-04
Technical Solutions | CMS-XML

NBEMM Don't Start (Error 334) | Symantec Connect

NBEMM Don't Start ( Error 334 )
Connect Forums | HTML

EMM interface initialization failed, status = 334 | Symantec Connect

EMM interface initialization failed, status = 334 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
Connect Forums | HTML

error code 334 on windows event viewer | Symantec Connect

& many have different issues & resolutions. e.g. if you look for 334 in the following, there are 2 pages of TechNotes that could offer you a resolution (***EDIT*** make that one page as the rest is just chaff!): Status Code Chart
Connect Forums | HTML

A backup of a large DFSR data set intermittently finishes with Status 1

11:15:56.520 PM: [5068.7976] 4 tar_base::keepaliveThread: INF - sending keepalive 11:16:36. 334 PM : [5068.5480] 2 ov_log::v_globallog: INF - QueryStatus() returned a failure in the param vss_e_flush_writes_timeout
TECH225512 | 2014-10-20
Technical Solutions | CMS-XML

Ten second connection delays cause status 25 after upgrading mediaserver to NetBackup 7.1

17:50:15.099 [5592.5372] 2 vnet_vnetd_connect_forward_socket_begin: ... 0: ipc_string: 57287 17:50:15. 334 [5592.5372] 2 vnet_vnetd_connect_forward_socket_begin: ... 0: hash_str1: f017547cf7f80e43f64be3005adbfebd The vnetd debug log
TECH162303 | 2014-04-09
Technical Solutions | CMS-XML

GENERAL ERROR: The Veritas NetBackup (tm) Enterprise Media Manager (EMM) service does not start after upgrading NetBackup from 6.0 GA to 6.0 Maintenance Pack 1 (MP1). This may also occur while upgrading from 7.01 to 7.1

01-09-2006,11:49:07 : ERROR failure in updating NetBackup database executing: C:\Program Files\VERITAS\NetBackup\bin\nbdb_upgrade -dbn NBDB; and status 334 : EMM interface initialization failed
TECH46021 | 2013-12-12
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?