Error Connecting To Oprd On 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 error connecting to oprd on server Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) error connecting to oprd status(96) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet network protocol error(39) and oprd
Error Connecting To Oprd 70
returned abnormal 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
Error Connecting To Oprd 196
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 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 error connecting to media manager network protocol error 39 over nbrb allocations causing ltid 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 aSERVICES 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 Research Exchange Investor Relations Careers
Veritas Netbackup Network Protocol Error 39
Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español nbrbutil -resetmediaserver USA Site: Veritas Veritas PartnerNet Netbackup Console Media or Device mangement gives "error connecting to OPRD on :network protocol oprd returned abnormal status (96) error (39)" Article:000008598 Publish: Article URL:http://www.veritas.com/docs/000008598 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 https://www.veritas.com/support/en_US/article.000009880 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 expanding device or media sections of the Netbackup Console, error 39 is observed. Devices are inoperable and Media Server with configured tape drive is in state "Active for disk" only. The LTID process appears to be hung Error https://www.veritas.com/support/en_US/article.000008598 Message error connecting to OPRD on
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 http://www.ehow.co.uk/how_7417537_fix-protocol-error-39_-message.html 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 http://www.tek-tips.com/viewthread.cfm?qid=1179885 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 error connecting 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 error connecting to 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 available No slideshows available No videos available How to fix error 1603 absolutely free How to Fix E
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Symantec: NetBackup Forum at Tek-Tips HomeForumsServer RackBack-up SystemsSymantec: NetBackup Forum Network protocol error when clicking on device monitor thread776-1179885 Forum Search FAQs Links MVPs Network protocol error when clicking on device monitor Network protocol error when clicking on device monitor EnochChum (TechnicalUser) (OP) 20 Jan 06 12:45 I'm getting a network protocol error(39) when I click on the device monitor on the menu on the left-hand side. How do I resolve this issue? Do I need a reboot of the master server?Thanks in advance,Enoch RE: Network protocol error when clicking on device monitor Stumpr (TechnicalUser) 20 Jan 06 13:04 Cool name - Enoch. That's what I wanted to call my son but the wife said no. We settled for Caleb.Anyway. . see:The device monitor display for one media server fails with network protocol error (39). Also, vmoprcmd on the media server fails with media manager error 69: "Failed sending request to VMD." http://seer.support.veritas.com/docs/265760.htmIf this doesn't help then you may have other vmd related problems or perhaps even a now corrupted vmglobdb. Bob StumpJust because the VERITAS documentation states a certain thing does not make it a fact and