Home > Backup Exec > Backup Exec Remote Agent Error Connecting To The Remote Computer

Backup Exec Remote Agent Error Connecting To The Remote Computer

Contents

Its 14. Create/Manage Case QUESTIONS? Featured Post Anonabox PRO Tor & VPN Router Promoted by Experts Exchange PRO is the most advanced way to fortify your privacy and online anonymity by layering the Tor network with Open your command prompt on the workstation. Source

Hopefully I will get the same result! 0 Kudos Reply Thanks again! Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. Sorry, we couldn't post your feedback right now, please try again later. Get 1:1 Help Now Advertise Here Enjoyed your answer?

Backup Exec Remote Agent Error 1603

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Join & Ask a Question Need Help in Real-Time? It is recommended that a complete backup of the registry and workstation be made prior tomaking any registry changes.Goto the following registry key: HKEY_CLASSES_ROOT\CLSID\ Locate the 'AppID' String Value key and if i install thebe5204R180429_x64bit.exe 0 Kudos Reply ...if that patch hasn't been CraigV Moderator Partner Trusted Advisor Accredited ‎04-30-2013 01:30 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed

  • 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 Veritas.com Support Communities
  • Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec 2010 R3 jobs fails with the error: 0xe0009b86 - Backup
  • It will prompt to authorize the server or not.
  • VOX : Backup and Recovery : Backup Exec : Agent Update: Error connecting to the remote regis...
  • 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 Veritas.com Support Communities
  • Join the community of 500,000 technology professionals and ask your questions.
  • Use both together or separately, and without needing to download software onto your devices.
  • It was not listed under my firewall settings however (due to group policy).
  • DenisFrolov Level 3 ‎04-30-2013 01:04 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I installedRAWS64(Local).
  • Veritas does not guarantee the accuracy regarding the completeness of the translation.

And it didn't solve the problem. "Microsoft Exchange 2010 database backup fails with v-79-57344-913 database was not found" 0 Kudos Reply « Previous 1 2 Next » Contact Privacy Policy Terms But Exec is very DenisFrolov Level 3 ‎04-30-2013 05:48 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Instaled. Ensure that the computer is available, has WMI enabled, and is not currently blocked by a firewall.14" I've tried turning off the firewall as per http://www.symantec.com/business/support/index?page=content&id=TECH148594 in all 3 modes, still Symantec Backup Exec Remote Agent Or do you use the same login for the BE Server as for the Agent update too?

If you've already registered, sign in. Thank You! Hope you’ll enjoy it and will choose the one as required by you. Add the User 'LOCAL SERVICE' to the Group or user names list and give Allow access for these permissions:   Local Launch Remote Launch Local Activation Remote Activation   Fig 7 Click

Push-install the remote agent to one or more remote computers from the media server. Backup Exec 12.5 Remote Agent Nick_Elmer Level 6 Employee ‎09-14-2011 07:32 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Thank you for your feedback Followed the above procedure and afterwards, the push install worked. Backup Exec 2010 R2 - Remote Agent Install Error Code 1603 [fa icon="long-arrow-left"] Back to all posts [fa icon="pencil'] Posted by Lewan Solutions [fa icon="calendar"] September 28, 2010 Tweet While onsite

Backup Exec Remote Agent Install Failed With Error Code 1603

No Yes Did this article save you the trouble of contacting technical support? The servers that already had remote agent on them from BE 2010 had no problem ungrading. Backup Exec Remote Agent Error 1603 Serves run with local system account. Backup Exec 12 Remote Agent Ensure that the computer is available,has WMI enabled, and is not blocked by a firewall. 14" http://www.symantec.com/docs/TECH148594 0 Message Author Comment by:Paul-Brooks2013-01-23 Thanks for your help.

Go to the Agent directory under the BE installation directory and then copy either the RAWS32/RAWS64 directory over to the remote machine and then do the agent installation from the copied http://gatoisland.com/backup-exec/backup-exec-error-connecting-remote-computer-wmi.php Check It Out Suggested Solutions Title # Comments Views Activity How to backup Master server with Media server 4 51 89d Windows 2012 R2 -- file "USAGE" report ? 2 45 I checked the workstations and their firewall settings all had WMI and File and Printer Sharing on. We also have Server 2008 acting as a fileserver. Backup Exec 11d Remote Agent

It is possible that updates have been made to the original version after this document was translated and published. Hope this helps, Nick 0 Kudos Reply I've just experienced the BMcGinnis Level 2 ‎07-28-2011 09:54 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to It is possible that updates have been made to the original version after this document was translated and published. have a peek here You may also refer to the English Version of this knowledge base article for up-to-date information.

Make sure that the computer is available, WMI is enabled and not blocked Windows Firewall.14 Firewall is turned off, antivirus is empty, the WMI service is enabled. Backup Exec Linux Remote Agent Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. This is another way to establish the trust relationship between remote computer and media server.3.

I entered the correct remote computer credentials in this window: Theaccount thatIuseisdefinitelya localadminonallservers.Withthis account,theBackupExecservices run, too.

Solution 2: NDMP using different ports on media server and remote server NDMP by default runs on port 10000.If the media server is running on port 10000 and if the remote http://www.symantec.com/business/support/index?page=content&id=TECH180429 will it work? So you can use the window remote computer credentials successful? Backup Exec Exchange Remote Agent If the Backup Exec 2010 R3 or above Remote agent for Windows (RAWS) is installed manually, the trust must be established before selecting the remote computer for backup or an existing selection list

Ensure that the computer is available, has WMI enabled, and is not currently blocked by a firewall" There is no active firewall and WMI is active and I can ping the If problem persist, install Remote Agent for Windows Servers (RAWS) using manual method following instructions listed here.   Terms of use for this information are found in Legal Notices.

Related Articles Email Address (Optional) Your feedback has been submitted successfully! Check This Out Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall.

Labels: 10.x and Earlier Agent for Microsoft Exchange Server Agents Backup and Recovery Backup Exec Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 10 Replies Hi, Check out the TN CraigV No Yes Did this article save you the trouble of contacting technical support? Machine Creation Services (MCS) 3 Questions to Ask When Evaluating Managed Print Services companies Error fix: Microsoft SCCM 2012 Error Code Ox87D00668 (.NET Patching Issue) Controlling Printing Costs with Print Governance Only when I logged into the media server and ran the console as a domain admin was i able to successfully push the agent.

I tried instal with local administrator account and gave all sorts of rights, but to no avail. I suspect there is a bug when the remote hosts are verifying the installation to check if you haves RAWS installed and what version you are running. However, when I tried to push install Agent for Windows to our other workstations (XP or 7), I recieved the status "Error connecting to the remote computer. Even specifying the domain admin credentials through the wizard for the RAWS installation account I was receiving the remote registry error.

Join Now For immediate help use Live now! But, the Exec show me the size0 Kb ofmy DB! Make sure... From the error, it looks like the account specified, does not have the necessary permissions to do so.

© Copyright 2017 gatoisland.com. All rights reserved.