Home > Unable To > Emm 77 Error

Emm 77 Error

Contents

Sorry, we couldn't post your feedback right now, please try again later. emm connection failure on new media server. 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 Restart NetBackup daemons.Applies ToNetBackup 7.x.x.

I know you said you can't re-install. Environment Windows 2008 R2 Cause nbdb_upgrade step failed to update the schema. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.  Terms of use for this information are found in Legal Notices. 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 https://www.veritas.com/support/en_US/article.000016925

Unable To Connect To The Enterprise Media Manager Server 77

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 Create/Manage Case QUESTIONS? Open Services (Start > Run... > services.msc).2. Installation of pack NB_60_4_M FAILED Sat Nov 25 12:12:55 CST 2006 Rev. 1.33.4.13.12.13.Unified logging for the nbrb originator ID may show the following messages.# vxlogview -p NB -o nbrb -b "11/28/06

I reinstall netbckup server (i INSTALLED master server ONLY) in my windows 7 laptop now i am getting error like UNABLE TO RETRIVE VERSION OF THE SERVER "KBN-PC". Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE: 77 - When installing a NetBackup maintenance pack, the following error occurs: NetBackup 7.5 Documentation is available here: http://www.symantec.com/docs/DOC5138 0 Kudos Reply Hi revaroo! Solaris forces you to have a unique hostname assigned to each interface.

I reinstall netbckup server (i INSTALLED master server ONLY) in my windows 7 laptop now i am getting error like UNABLE TO RETRIVE VERSION OF THE SERVER "KBN-PC". Unable To Connect To The Enterprise Media Manager Server 92 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! You may also refer to the English Version of this knowledge base article for up-to-date information. Run nbemmcmd -getemmserver wthat does come with any output 8.

NBU is not supported as Master server on Windows 7. 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 Solution To resolve the issue: 1. As per your disscussion windows ...

Unable To Connect To The Enterprise Media Manager Server 92

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 From \Veritas\Netbackup\bin>nbdb_admin -validate -full Should complete with no errors and show successful. Unable To Connect To The Enterprise Media Manager Server 77 Veritas does not guarantee the accuracy regarding the completeness of the translation. Emm Interface Initialization Failed, Status = 334 No Yes How can we make this article more helpful?

Veritas does not guarantee the accuracy regarding the completeness of the translation. Run tpconfig -d and vmoprcmd to verify connection with vmd/EMM/pbx. 15. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Email Address (Optional) Your feedback has been submitted successfully!

Or have you installed NBU in a VM on your laptop? No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities Is there another config. If media server is not, then activity should be normal (which was not). 9.  If vxss is enabled then put in USE_VXSS = PROHIBITED in bp.conf. 10.  Run /usr/openv/netbackup/db/bin/nbdb_ping on the

Restart NetBackup services.Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Email Address (Optional) Your feedback has been submitted successfully! nbpem log:----------5/19/2011 22:07:38.657 [Diagnostic] NB 51216 nbpem 116 PID:8836 TID:3412 File ID:116 [No context] 1 V-116-285 [NBProxy::doConnect] starting nbproxy E:\Program Files\Veritas\NetBackup\var\nbproxy_pem.ior5/19/2011 22:07:38.657 [Debug] NB 51216 nbpem 116 PID:8836 TID:3412 File ID:116

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

Error NetBackup Administrators will see errors stating "unable to connect to EMM server (77)" and "EMM interface initialization failed, status = 334" in application log. Handy NetBackup Links 0 Kudos Reply Hi! Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Look for (traceroute: Warning: Multiple interfaces found; using 136.140.x.x). 18.

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. 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 Stuart_Green Level 6 ‎07-29-2009 04:25 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content You have to ask yourself, if Thank You!

Sorry, we couldn't post your feedback right now, please try again later. Thank You! No Yes Did this article save you the trouble of contacting technical support? Was media server ever upgraded from 5.x? (No it was not.) 12.

You can install Remote Admin Console/or Java console though. 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 Check for bp.conf entries 2. Please resolve and try again.

Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may 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 You may also refer to the English Version of this knowledge base article for up-to-date information. No Yes Did this article save you the trouble of contacting technical support?

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 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 No Yes How can we make this article more helpful? You may also refer to the English Version of this knowledge base article for up-to-date information.

Verify that network access to the EMM server is available and that the services nbemm and pbx_exchange are running on the EMM server. (195) Command did not complete successfully.