Home > Error Connecting > Error Connecting Media Manager Network Protocol Error 39

Error Connecting Media Manager Network Protocol Error 39

Is media server perhaps behind firewall? This corrupted system file will lead to the missing and wrongly linked information and files needed for the proper working of the application. Click here follow the steps to fix Error Connecting Media Manager Network Protocol Error 39 and related errors. This Error Connecting Media Manager Network Protocol Error 39 error code has a numeric error number and a technical description. this contact form

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! 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 Click the 'OK' button. 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

Labels: 7.1.x and Earlier Backup and Recovery Configuring NetBackup 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! This website should be used for informational purposes only. Register now while it's still free! No Yes How can we make this article more helpful?

  • Veritas does not guarantee the accuracy regarding the completeness of the translation.
  • Movies.http://au.movies.yahoo.com 1 Reply 57 Views Switch to linear view Disable enhanced parsing Permalink to this page Thread Navigation VENU 2004-04-05 06:17:08 UTC robertinoau 2004-04-05 11:19:52 UTC about - legalese Loading...
  • The Error Connecting Media Manager Network Protocol Error 39 error may be caused by windows system files damage.
  • Create/Manage Case QUESTIONS?
  • If not master, you need to ensure PBX comms (bi-directional) between media server and robot control host as well.

Newer post » « Older post Powered by Blogger. Email Address (Optional) Your feedback has been submitted successfully! Stop/start NBU daemons. see:The device monitor display for one media server fails with network protocol error (39).

This error is caused by you changing the default port settings in the Symantec NetBackup Enterprise software on your system. Handy NetBackup Links 0 Kudos Reply here is output of bpps -x robertngara Level 3 ‎10-13-2010 12:22 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email That's what I wanted to call my son but the wife said no. Disclaimer: This website is not affiliated with Wikipedia and should not be confused with the website of Wikipedia, which can be found at Wikipedia.org.

If the service is running in the media server, ensure that the service is stopped before attempting to restart the NetBackup services. You may also refer to the English Version of this knowledge base article for up-to-date information. Note: This article was updated on 2016-11-14 and previously published under WIKI_Q210794 Contents 1.What is Error Connecting Media Manager Network Protocol Error 39 error? 2.What causes Error Connecting Media Manager Network To unlock all features and tools, a purchase is required.

What causes Error Connecting Media Manager Network Protocol Error 39 error? Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support Connect Communities Security Center Find a Partner Events Webcasts Contact Us About I see tldcd is running on this media server meaning it's the robot control host? This is common error code format used by windows and other windows compatible software and driver vendors.

basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.) Recommended Solution Links: (1) weblink Compatibility: Windows 7, 8, Vista, XP Download Size: 6MB Requirements: 300 MHz Processor, 256 MB Ram, 22 MB HDD Limitations: This download is a free evaluation version. Sorry, we couldn't post your feedback right now, please try again later. 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 Veritas

Where is the robotic control? Note: The manual fix of Error Connecting Media Manager Network Protocol Error 39error is Only recommended for advanced computer users.Download the automatic repair toolinstead. No Yes Did this article save you the trouble of contacting technical support? navigate here I have added VERBOSE line in the vm.conf file. 0 Kudos Reply Looks like PBX level comms is Marianne Moderator Partner Trusted Advisor Accredited Certified ‎10-13-2010 03:56 AM Options

Instructions To Fix (Error Connecting Media Manager Network Protocol Error 39) error you need to follow the steps below: Step 1: Download (Error Connecting Media Manager Network Protocol Error 39) Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Stop/start NBU.

Thank you for your feedback!

Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. The corrupted system files entries can be a real threat to the well being of your computer. Sorry can't help youPost by VENUThe following error I have got today throughNetbackup Admin console GUIwhile clicking/enlarging on volume pool tab.....but expect volume pool tab everything is fine likereports, plicies,etc..We have Veritas does not guarantee the accuracy regarding the completeness of the translation.

Handy NetBackup Links 0 Kudos Reply Hi Marianne This is what i am robertngara Level 3 ‎10-14-2010 05:36 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print There can be many events which may have resulted in the system files errors. If not master, you need to ensure PBX comms (bi-directional) between media server and robot control host as well. http://winnsecurityproducts.com/error-connecting/error-connecting-to-creative-kit.html Are you aComputer / IT professional?Join Tek-Tips Forums!

Solved! How to Fix Windows Installer Error 1601 How to Fix Time Synchronization Errors How to Fix Security Certificate Error Windows Comp... 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 My master server is running Sles 11 and my media server has AIX 5.3.

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? Click Here to join Tek-Tips and talk with other members! It is possible that updates have been made to the original version after this document was translated and published. Change the 'Client Reserved Port' values to the default values, which should be from 512 to 1023.6.

Click on the 'NetBackup Administration Console' icon on your computer. Personal tools Namespaces Article Search Main Page Applications AOL Internet Explorer MS Outlook Outlook Express Windows Live DLL Errors Exe Errors Ocx Errors Operating Systems Windows 7 Windows Others Windows All the above actives may result in the deletion or corruption of the entries in the windows system files. its had 0. 0 Kudos Reply Where is the robot control?

If FQDN is used anywhere, it must be able to resolve everywhere. If the Removable Storage service is listed as "stopping" and the option to start, stop or restart the service are disabled in the Windows Services window, a reboot of the server stuck tape). This article contains information that shows you how to fix Error Connecting Media Manager Network Protocol Error 39 both (manually) and (automatically) , In addition, this article will help you troubleshoot

Registration on or use of this site constitutes acceptance of our Privacy Policy. Join UsClose How to fix Error Connecting Media Manager Network Protocol Error 39 Error? How about "vmoprcmd" on your master server? 0 Kudos Reply New setup robertngara Level 3 ‎10-12-2010 10:53 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email Change the 'Server Port Windows' values to the default values, which should be from 1025 to 5000.7.

Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. How does it work?