Emm 77 Error
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile
Unable To Connect To The Enterprise Media Manager Server 77
Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English unable to connect to the enterprise media manager server 92 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet DOCUMENTATION: When connecting emm interface initialization failed, status = 334 to host properties/master server, the following error are received: "unable to connect to EMM server (77)" and "EMM interface initialization failed, status = 334" Article:000033104 Publish: Article URL:http://www.veritas.com/docs/000033104 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem - Unable to connect to EMM server (77)- EMM interface initialization failed, status = 334- Netbackup Event Manager service won't start- Lots of nbproxy processes are running Error Message Netbackup Event Manager service won't start nbevtmgr log:-------------5/19/2011 22:07:35.911 [Application] NB 51216 nbevtmgr 231 PID:4056 TID:9188 File ID:231 [No context] [Error] V-231-190 The NBNosSvc service experienced an error while shutting down The NetBackup Policy Execution Manager service terminated unexpectedly. 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 [No context] 2 [NBPClient::KillNBP] Found an old proxy with ior file: E:\Program Files\Veritas\NetBackup\var\nbproxy_pem.ior shutting it down Cause HKEY_LOCAL_MACHINE\SOFTWARE\NETBACKUP\CURRENT VERSION\CONFIG\ "CLIENT_PORT_WINDOW" has changed to 1024 1024 from 0 0 Solution Administrators may see the following error occur when attempting to connect to the host properties on the master server "unable to connect to EMM server (77)" and "EMM interface initialization failed, status = 334" These errors may occur if the client port window is improperly set. An
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Unable to connect to the EMM server error(77) VOX : Backup and Recovery : NetBackup : Unable to connect to the EMM server error(77) Subscribe to RSS Feed Mark Topic as New Mark https://www.veritas.com/support/en_US/article.TECH51026 Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! 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 a Friend Report Inappropriate Content HI I have installed netbackup 7.5 on windows7 64bit, While i am trying to open activity https://vox.veritas.com/t5/NetBackup/Unable-to-connect-to-the-EMM-server-error-77/td-p/604779 monitor Unable to connect to the EMM server error(77). thanks Naidu Solved! Go to Solution. Labels: 7.5 Backup and Recovery NetBackup Troubleshooting Windows Server (2003-2008) 3 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! 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 Open the attachment in this Technote and it will tell you what OS you can use as a Master server: http://www.symantec.com/business/support/index?page=content&id=TECH76648 Expannd "Operating System" and go through each one. You'll be interested in the NetBackup Server part for each OS. You will notice Windows 7 only shows it's available to use in NetBackup as a client. 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 01:47 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Please post output of all of these commands from cmd: hostname ipconfig /all bpclntcmd -self (command is in
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas https://www.veritas.com/support/en_US/article.000034032 Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet EMM Initialization Failed - 77, Failed to open device mappings Article:000034032 unable to Publish: Article URL:http://www.veritas.com/docs/000034032 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article unable to connect Languages Subscribe to this Article Manage your Subscriptions Problem EMM Initialization Failed - 77, Failed to open device mappings Solution ISSUE: Enterprise Media Manager (EMM) Initialization Failed - 77, Failed to open device mappings ERROR CODE/MESSAGE: 77/195/189 ENVIRONMENT/CONDITIONS: Media server (136.140.x.y) talks with master server (136.140.x.z) with multiple NIC interfaces over a WAN with connection problems. Master's multiple network interfaces were for production and backup network with different subnets. 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) # nbdb_ping MASTER SERVER: Database [NBDB] is alive and well on server [NB_nbu0]. MEDIA SERVER: Database [NBDB] is not available. 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. Not allowing pe