Home > Unable To > Emm 77 Error

Emm 77 Error

Contents

Change the USE_VXSS entry to "PROHIBITED" and save.4. A re-installation would give you piece of mind and also when contacting support with any future issues. EVIDENCE: # ./volmgr/bin/tpconfig -d EMM interface initialization failed, status = 77 # ./volmgr/bin/vmoprcmd EMM interface initialization failed, status = 195 failed to initialize a connection to the Enterprise Media Manager (189) CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical

Thank You! Open the attachment in this revarooo Level 6 Employee ‎11-03-2013 12:34 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content No Yes How can we make this article more helpful? No Yes Did this article save you the trouble of contacting technical support?

Unable To Connect To The Enterprise Media Manager Server 77

please let me know the installation steps. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? discussion comment 31 Oct 2013 KBN commented on: error no:-77 HI I have installed netbackup 7.5 on windows7 64bit, While i am trying to open activity monitor Unable

Restart NetBackup daemons.Applies ToNetBackup 7.x.x. Do you have confidence in this installation? As per your disscussion windows ... One time media to master was not working; /14/08 16:26:48.607 V-137-65 [InsecureServerEvaluator::allow_peer] Peer address (136.140.x.y) not in server list.

Solution Stop all NBU services and confirm there are no hung NBU processes. \Veritas\Netbackup\bin>bpdown -f -v stops NBU processes bpps Will list running processes and PID.NOTE: End hung NBU processes with Unable To Connect To The Enterprise Media Manager Server 92 Sorry, we couldn't post your feedback right now, please try again later. No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Check the services configuration -- files, YP, NIS, or NIS+.

Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem EMM Initialization Failed - 77, Failed to open device mappings Solution ISSUE: Enterprise Media discussion comment 01 Nov 2013 KBN commented on: Unable to connect to the EMM server error(77) Hi! But at what price. Email Address (Optional) Your feedback has been submitted successfully!

Unable To Connect To The Enterprise Media Manager Server 92

You may also refer to the English Version of this knowledge base article for up-to-date information. https://www.veritas.com/support/en_US/article.TECH57690 what i have to do it. Unable To Connect To The Enterprise Media Manager Server 77 file that should be checked? Emm Interface Initialization Failed, Status = 334 MEDIA SERVER: Database [NBDB] is not available.

Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. You may also refer to the English Version of this knowledge base article for up-to-date information. Go to Solution Unable to connect to the EMM server error(77) KBN Level 3 ‎11-01-2013 01:44 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Cause NetBackup hostname lookup may have been disrupted during the network changes and this may be recorded in NetBackup's own host cache.

Please post output of all of the commands that I have asked for above. You will notice Windows 7 only shows it's available to use in NetBackup as a client. From \Veritas\Netbackup\bin>nbdb_admin -validate -full Should complete with no errors and show successful. Different IP adresses on the same server should be bound to different hostnames - either local hosts file or DNS.

Handy NetBackup Links 0 Kudos Reply Hi! NetBackup 7.5 Documentation is available here: http://www.symantec.com/docs/DOC5138 View solution in original post 0 Kudos Reply 16 Replies Please post output of all of Marianne Moderator Partner Trusted Advisor Accredited Certified ‎11-01-2013 CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical

It is possible that updates have been made to the original version after this document was translated and published.

Installed device mappings still same error 6.  /opt/VRTSpbx/bin/vxpbx_exchanged restarted 7. Enter to continue, "x" to exit. <16>bpauthorize main: Function connect_to_remote_server(FQDN) failed: 11 system call failed You do not have the proper authorization to perform this task. Not allowing peer to connect 05/14/08 16:26:49.687 V-137-513 [InsecureServerEvaluator::allow_peer] The hostname: usmihqbs1, IP address: 2290882656, port: 32851 Later it was: 06/04/08 11:57:26.587 V-219-1 [ResourceEventMgr_i::updateInfo ] Heartbeat received from host usmihqbs1 06/04/08 The bp.conf file lists the short name for the Master server for all entries (SERVER, CLIENT, and EMMSERVER).

As per your disscussion windows 7 is not supported for NBU server 7.5, So on which platform i have to install i want to install for practice purpose because i am m discussion comment 02 Nov 2013 KBN commented on: Unable to connect to the EMM server error(77) Hi! Here are the errors from the trace: The NetBackup daemon process (bpdbm) was not started. Veritas does not guarantee the accuracy regarding the completeness of the translation.

retval gt; 06/04/08 11:57:27.784 [SSRDbConnection::OpenOdbcView] SOLUTION/WORKAROUND: 1. I am installed Netbackup KBN Level 3 ‎11-01-2013 11:28 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi! Open Services (Start > Run... > services.msc).2.