Backup Exec 2012 Agent Error Connecting To The Remote Computer
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 Lewan Technology is a business technology and managed service provider serving Colorado, Wyoming, New Mexico and beyond. Sorry, we couldn't post your feedback right now, please try again later. Only thing of note on the old box is a copy of vmware 2 hosting an accounts application Is there any way vmware will be blocking the ports I need? have a peek here
Re-attempt the push installSystem account could be blocking the setup. If a push/local install of RAWS fails with the error 1603 still and is accompanied by the below event log Check It Out Suggested Solutions Title # Comments Views Activity Commvault (I think) Icons 4 53 81d Dell Powervault 3220i... Agent has been installed very good on the other server. Ensure that the server is available, has WMI enabled, and is not blocked by a firewall.24" To fix this problem try the following on the remote computer: Run Group Policy Editor
Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available
No Yes How can we make this article more helpful? AndEvent ID 4672 for my "backup-user": SeCreateTokenPrivilege SeSecurityPrivilege SeBackupPrivilege SeRestorePrivilege SeTakeOwnershipPrivilege SeDebugPrivilege SeSystemEnvironmentPrivilege SeLoadDriverPrivilege SeImpersonatePrivilege 0 Kudos Reply I installedRAWS64(Local). Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall.
- Written by Lewan Solutions View & Submit Comments [fa icon="envelope"] Subscribe to Email Updates Search Blog Posts in Google [fa icon="comments-o"] Follow us Get even more great content, photos, event info
- Join the community of 500,000 technology professionals and ask your questions.
- Its 14.
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. Additional we planned to use Symantec NetBackup7 to backup to tape media for disaster recovery. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603." Error Message Error connecting to the remote server. Backup Exec Cannot Connect To The Remote Computer But now: Microsoft DenisFrolov Level 3 04-30-2013 01:28 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ok.
Reboot the Workstation or Server wherein this DCOM change occurred.10. The Backup Exec Server Could Not Connect To The Remote Computer No Yes Did this article save you the trouble of contacting technical support? Followed the above procedure and afterwards, the push install worked. Click Start | Run | dcomcnfg4.
The Backup Exec Server Could Not Connect To The Remote Computer
The remote computer may not be running the Backup ExecRemote Agent for Windows/Linux. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available Thank You! Backup Exec Remote Agent Error 1603 Email Address (Optional) Your feedback has been submitted successfully!
Showing results for Search instead for Do you mean VOX : Blogs : Backup & Recovery Community Blog : Fix for Error 1603 When trying to push install age... http://sovidi.com/backup-exec/backup-exec-remote-agent-error-connecting-to-the-remote-registry.php Request a Free Review How To: Azure Resource Manager VM Level Backup & Restore Without Snapshots NetScaler Website Redirection - The Nice & Elegant Way Paper Weight & Printing - how 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 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 How To Install Backup Exec Remote Agent Manually
Sorry, we couldn't post your feedback right now, please try again later. The error is: Error connecting to the remote computer. 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. Check This Out 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 Services Overview
I checked the workstations and their firewall settings all had WMI and File and Printer Sharing on. You may also refer to the English Version of this knowledge base article for up-to-date information. For more information on using "netsh advfirewall firewall" commands instead of "netsh firewall", see KB article 947709 at http://go.microsoft.com/fwlink/?linkid=121488 .
Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?
Try to install Backup Exec agent again after rebooting the remote server. http://www.symantec.com/business/support/index?page=content&id=TECH180429 will it work? Veritas does not guarantee the accuracy regarding the completeness of the translation. My DB have size 50Gb 0 Kudos Reply ...check this CraigV Moderator Partner Trusted Advisor Accredited 04-30-2013 01:06 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print
But, the Exec show me the size0 Kb ofmy DB! Apologies for the misquote in the OP, the full error is "Error connecting to the remote computer.