phone 983-651-5611
Home > Failed To > Failed To Initialize Orb Netbackup

Failed To Initialize Orb Netbackup

Thank You! The command "nbemmcmd -getemmserver" on a new UNIX based NetBackup 6.5 media server produces the error: "Failed to initialize EMM connection". Please find the below steps which i performed: Tested bpclntcmd from Media Server ( to Master Server: D:\Program Files\Veritas\NetBackup\bin]bpclntcmd -sv D:\Program Files\Veritas\NetBackup\bin]bpclntcmd -pn expecting response from server ksprod75.kcdc.att.com D:\Program Files\Veritas\NetBackup\bin]bpclntcmd -self It is possible that updates have been made to the original version after this document was translated and published. have a peek here

Handy NetBackup Links 0 Kudos Reply Contact Privacy Policy Terms & Conditions Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem BUG REPORT: Intermittent 83 errors using NetBackup Key Management Service (KMS) Solution Symptom: When using You may also refer to the English Version of this knowledge base article for up-to-date information. It is possible that updates have been made to the original version after this document was translated and published. https://www.veritas.com/support/en_US/article.000014919

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 NetBackup does nothave to be up to administer license keys. Sorry, we couldn't post your feedback right now, please try again later. nbemm creates 'EMM' ORB (first ORB)09/20/2011 11:48:35.625 [Debug] NB 51216 libraries 137 PID:18284710 TID:1 File ID:111 [No context] 4 [TAO] TAO (18284710|1) created new ORB C.

No Yes Did this article save you the trouble of contacting technical support? Check PBX logs for detailsH. No Yes How can we make this article more helpful? 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) However, master server was not configured to

CORBA::TRANSIENT09:47:02.205 [5740.4796] <16> emmlib_initializeEx: (-) system exception, ID 'IDLmg.org/CORBA/TRANSIENT:1.0'OMG minor code (2), described as '*unknown description*', completed = NO09:48:29.408 [7764.7376] <16> emmlib_initializeEx: (-) Exception! nbemm 'EMM' ORB is shutdown09/20/2011 11:53:37.221 [Debug] NB 51216 libraries 137 PID:18284710 TID:1 File ID:111 [No context] 2 [Orb::shutdown]       Orb is now shutdown: id = EMM(Orb.cpp:1749)J. [PBX]  After 5 minutes send_handle Review the PBX log (product id 50936, oid 103) for EMM queries coming into the master server for the time when the NetBackup daemons are starting up.Search for the "extension=EMM" string No Yes Registrieren Hilfe Angemeldet bleiben?

It is possible that updates have been made to the original version after this document was translated and published. D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -pn expecting response from server ksprod75.kcdc.att.com mokscy3uvgfpa02.itservices.sbc.com mokscy3uvgfpa02.itservices.sbc.com 135.188.39 .124 54599 D:\Program Files\Veritas\NetBackup\bin>bpclntcmd -self gethostname() returned: mokscy3uvgfpa02.itservices.sbc.com host mokscy3uvgfpa02.itservices.sbc.com: MOKSCY3UVGFPA02.ITServices.sbc.com at 1 35.188.39.124 (0x7c27bc87) host mokscy3uvgfpa02.itservices.sbc.com: MOKSCY3UVGFPA02.ITServices.sbc.com at 1 Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Large number of EMM queries being sent from media servers fills up UNIX nbemm queries PBX for registration09/20/2011 11:49:51.896 [Debug] NB 51216 libraries 137 PID:18284710 TID:1 File ID:111 [No context] 6 [Orb::activate] +++ ENTERING +++ : obj = 2ff21efc (Orb.cpp:1122)09/20/2011 11:49:51.896 [Debug] NB 51216

In the PBX log after the 5 minute hang the following error can be found -09/20/2011 11:53:37.442 PID:16187536 TID:1 File ID:103 [No context] [Error] PBX_Server_Proxy::PBX_Server_Proxy::send_handle failed.3. https://www.veritas.com/support/en_US/article.000016709 Foren-Regeln -- treMKa grn/wei -- Standard Mobile Style Kontakt Archiv Datenschutzerklrung Nach oben Alle Zeitangaben in WEZ +2. Email Address (Optional) Your feedback has been submitted successfully! Tell me if i am wrong somewhere..... 0 Kudos Reply Always remember to clear NBU Marianne Moderator Partner Trusted Advisor Accredited Certified ‎04-20-2012 10:06 PM Options Mark as New Bookmark Subscribe

Verify that network access to the EMM serv er is available and that the services nbemm and pbx_exchange are running on the EMM server. (195) Command did not complete successfully. http://twaproductions.com/failed-to/failed-to-initialize-wep.html Did you create all the logging folders with "mklogdir.bat"? 0 Kudos Reply Re: Problem in NetBackup Administration Console Rami Level 3 ‎10-29-2008 12:14 AM Options Mark as New Bookmark Subscribe Subscribe No Yes Did this article save you the trouble of contacting technical support? 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

Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem EMM connection failure on new media server. No Yes How can we make this article more helpful? Reviewing the output from the nbemmcmd -listhost command confirmed the correct new media server hostname was added3.  Running /usr/openv/netbackup/bin/bpclntcmd -pn command on the new media server confirmed the master server was Check This Out 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

You may also refer to the English Version of this knowledge base article for up-to-date information. Symantec recommends that you download the patch set dated June 2011 (or newer) from the Oracle Support website. Article:000036630 Publish: Article URL:http://www.veritas.com/docs/000036630 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

PBX receives the above number of 'EMM' connection request from different media servers and then hangs[5 minute gap in PBX log]E.

https://support.oracle.com The patch set contains the following minimum recommended patches: ¦ 118777-17 (SunOS 5.10: Sun GigaSwift Ethernet 1.0 driver patch) ¦ 139555-08 (Kernel patch with C++ library updates). ¦ 142394-01 (Internet Create/Manage Case QUESTIONS? Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Solved Go to Solution AK1980 Level 3 Certified ‎04-17-2012 09:08 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content My

Create/Manage Case QUESTIONS? No Yes Did this article save you the trouble of contacting technical support? Check PBX logs for details 11/23/10 14:36:11.879 V-137-103 [Orb::init] CORBA exception: system exception, ID ‘IDL:omg.org/CORBA/BAD_PARAM:1.0' TAO exception, minor code = 1 (endpoint initialization failure in Acceptor Registry; ETIMEOUT), completed = NO this contact form NetBackup 6.53.

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 Sorry, we couldn't post your feedback right now, please try again later. You should only have 1.Do you have this host in DNS too? Still the same error.....please help....... 0 Kudos Reply Accepted Solution!

TCP/IP will not know which interface to respond on. CORBA::NO_PERMISSION 22:41:40.338 [6428.2396] <16> nbemmcmd: Run time failure: Failed to initialize EMM connection. It is possible that updates have been made to the original version after this document was translated and published. 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 Vision 2016 Vision

Verify that network access to the EMM server is available and that the services nbemm and pbx_exchange are running on theEMM server. (195)Command did not complete successfully."I try to open "NetBackup that IP is not showing in your /etc/hosts file.What does bpclntcmd -pn show on the media server (this will tell you what the Master server thinks the IP is. We have 1 master sever and 4 media server, backups are running fine for 3 media servers but for one media server all backups are failing with Error 82 Active monitor Veritas does not guarantee the accuracy regarding the completeness of the translation.

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 Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Getting Error Failed to initialize EMM connection. No Yes How can we make this article more helpful?

Anything in any other NetBackup logs?