Error Connecting To Oprd On Machine Protocol Error 39
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 Corporate Leadership Newsroom error connecting to oprd on server Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français
Error Connecting To Oprd Status(96)
Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet network protocol error(39) and oprd returned abnormal
Error Connecting To Oprd 70
status(96) Article:000009880 Publish: Article URL:http://www.veritas.com/docs/000009880 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
Error Connecting To Oprd 196
in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem When trying to restart media server from the GUI->devices->media servers gets the errors Error Message Network protocol error(39) or oprd returned abnormal status Cause Media server had left over nbrb allocations causing ltid netbackup error connecting to oprd not to start properly on the media server Solution Use the nbrbutil command to clear the allocation holds that the media server has placed. The command can be run from the media server itself or the master server and is in the following path: Windows: \NetBackup\bin\admincmd Unix: /usr/openv/netbackup/bin/admincmd Command syntax: nbrbutil -resetMediaServer 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 have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes Did this article save you the trouble of contacting technical support? No Yes How can we make this article more helpful? Email Address (Optional) Your feedback has been submitteSERVICES 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 error connecting to media manager network protocol error 39 About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers veritas netbackup network protocol error 39 Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas nbrbutil -resetmediaserver PartnerNet Getting error "error connecting to oprd on server xxx ,oprd returned abnormal status 96" when running the device configuration wizard Article:000008823 Publish: Article URL:http://www.veritas.com/docs/000008823 Support / https://www.veritas.com/support/en_US/article.000009880 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 Languages Subscribe to this Article Manage your Subscriptions Problem Getting error "error connecting https://www.veritas.com/support/en_US/article.000008823 to oprd on server xxx ,oprd returned abnormal status 96" when running the device configuration wizard.Also unable to expand the devices tab ,getting error "error connecting to oprd,network protocol error 39" Error Message Error connecting to oprd on server xxx ,oprd returned abnormal status 96 Error connecting to oprd,network protocol error 39 Cause Stale entries for deleted devices in the NetBackup EMM database.Or if a media server is not correctly decommissioned. Solution Step 1:Windows only:From command prompt run set devmgr_show_nonpresent_devices=1Open the device manager click 'view' >show hidden devices > tape drives >check for ghost drives which are no longer connected to the server,if any remove them (repeat this for each media server)Step 2:Stop NetBackup services Windows
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton https://support.symantec.com/en_US/article.TECH148082.html Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical http://www.ehow.co.uk/how_7417537_fix-protocol-error-39_-message.html Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local error connecting Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English error connecting to Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Network Protocol Error (39) TECH148082 August 16th, 2011 http://www.symantec.com/docs/TECH148082 Support / Network Protocol Error (39) Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation When launching the Java Administration Console from a Windows workstation, the administration console becomes non-responsive when clicking in the "Activity Monitor" or "Device Monitor". Once the Java logs are enabled in the Windows workstation, the error "Network Protocol Error (39)" can be found when attempting to obtain device information for a media server. Cause Attempting to restart the services in the media server will show that multiple oprd.exe processes were unable to be terminated. After confirming that name resolution in the
Oprd Network Protocol Error 39" Message How to Fix an "Error Connecting to Oprd Network Protocol Error 39" Message Written by charles poole Share Tweet Share Pin Email Fix your Error 39 problem with Symantec software. (computer image by blaine stiger from Fotolia.com) Error 39 on your Symantec software restricts you from connecting to the Symantec network. This error is caused by you changing the default port settings in the Symantec NetBackup Enterprise software on your system. You can easily fix this problem by changing the port defaults back to what they were. Skill level: Easy Other People Are Reading Instructions 1 Click on the "NetBackup Administration Console" icon on your computer. Click the "Connect" button to connect to the "Master Server." 2 Click on the "+" sign to expand the "Host Properties" tab on the left-hand side of the page. 3 Click on the "Master Server" icon, then on the renamed version of the server in the window. 4 Click on the "Server Properties" window, then on the "Port Ranges" button. 5 Change the "Client Reserved Port" values to the default values, which should be from 512 to 1023. 6 Change the "Server Port Windows" values to the default values, which should be from 1025 to 5000. 7 Change the "Server Reserved Port Windows" values to the default values, which should be from 511 to 1023. 8 Click the "OK" button. Don't Miss 20 of the funniest online reviews ever 14 Biggest lies people tell in online dating sites Hilarious things Google thinks you're trying to search for Top 13 companies to work for in the UK 10 Conspiracy theories that turned out to be true 14 Brain-melting paradoxes that will destroy you References Symantec: How To Fix OPRD Error Editors’ pick Tips for winning at FTL: Faster Than Light You may also like… Filter: All types Articles Slideshows Videos Sort: Most relevant Most popular Most recent No articles avai