Error Connecting To The Remote Computer Backup Exec 1603
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 Research Exchange Investor Relations Careers Legal Contact Us backup exec remote agent error 1603 English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas backup exec remote agent install error 1603 Veritas PartnerNet A push install of the remote agent fails with: "Error connecting to the remote computer. Ensure that the computer backup exec error connecting to the remote computer ensure that the computer is available is available, has WMI enabled and is not blocked by a firewall" Article:000015581 Publish: Article URL:http://www.veritas.com/docs/000015581 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account
Backup Exec Cannot Connect To Remote Computer
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 Push install of the Backup Exec Remote Agent to a Remote Windows Server fails with error: "Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled and is not backup exec error connecting to the remote registry blocked by a firewall" Error Message Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. Solution Solution 1: Manually install the remote agent Copy the RAWS32/RAWS64 (from X:\Program Files\Symantec\Backup Exec\Agents) and the MSXML folders on the particular remote server where you want to install Remote Agent.On the remote server, run setup.exe from the RAWS32/RAWS64 folder and complete the install.Make sure to enable "Publishing" on the remote agent. For that launch Remote Agent Utility from Programs list or double click on the Remote Agent icon in the system tray. 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 server has NDMP running on any port other than 10000, then this can also cause the failure.To check which port NDMP is using, follow the article: www.symantec.com/docs/TECH24256If there is no entry in the services file (located at C:\Windows\System32\Drivers\etc) for NDMP, means its using the default port 10000.If the ports are different on both, the media server and remote server, then make them use the same port and then try the push installation again.
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers error connecting to the remote registry backup exec 2010 Blogs Groups Vision 2016 Sign In CommunityCategoryBlogResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Blogs : Backup & Recovery Community Blog : https://www.veritas.com/support/en_US/article.TECH177317 Fix for Error 1603 When trying to push install age... Subscribe to RSS Feed Mark as New Mark as Read Bookmark Subscribe Email to a Friend Printer Friendly Page Report Inappropriate Content Fix for Error 1603 When trying to push install agent for windows in Backup Exec 2012 Jeff Hoins (Joins05) Joins05 N/A 07-18-2012 04:31 https://vox.veritas.com/t5/Backup-Recovery-Community-Blog/Fix-for-Error-1603-When-trying-to-push-install-agent-for-windows/ba-p/780507 PM Subscribe to RSS Feed Mark as New Mark as Read Bookmark Subscribe Email to a Friend Printer Friendly Page Report Inappropriate Content 07-18-2012 04:31 PM After upgrading to BE 2012,I wanted to set up backups for all of our workstations. I had previously only backed up our servers and workstations needed for our daily production at our sign shop. The decision to backup all workstations was due to a new need for better safetyguards for our workstations going down due to me moving too far away to be onsite on a daily basis for any hardware/software failure. Our domain controller is SBS 2003 running exchange, it also runs the backup exec. We also have Server 2008 acting as a fileserver. The servers that already had remote agent on them from BE 2010 had no problem ungrading. However, when I tried to push install Agent for Windows to our other workstations (XP or 7), I recieved the status "Error connecti
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Backup Exec 2014 Agent Installasion Want to Advertise Here? Solved Backup Exec 2014 Agent Installasion Posted on 2014-11-27 Storage Software Windows Server 2003 2 Verified Solutions 5 Comments 2,060 Views Last Modified: 2014-12-29 We have recently Upgraded Our backup media Server for Backup exec 2010 R3 to 2014 SP1. I am trying to re install the backup agent on the clients and facing issue. The Nodes are running 2003 R2 OS With SP2 , When I try to Update these servers from the backup exec console on the media Server it gives me the following Error "Error Connecting to the Remote Computer. Ensure that the computer is Available, has WMI Enabled, and is not blocked by firewall. 2147944122" Screen Print Attached for reference I have checked the Connectivity and I am able to Ping the Client servers from the media Servers, also the WMI Service is restarted on both the nodes, But I Still face the Error. I Also tried uninstalling the previous version of the Agent from the Server and tried a Manual install by transferring the "RAWS32" folder from the media Server, But it Still fails with the following Error (Attached is the Installation Log file for reference) 11-26-2014,19:41:15 : AgentSeqDlgs::AgentInstaller 11-26-2014,19:41:15 : Executing runtime installer package vcredist_x86.exe. 11-26-2014,19:41:15 : C:\VCRedist\V10.0\vcredist_x86.exe /q /norestart /log "C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\V10.0_x86_msruntime_install.log" + 11-26-2014,19:41:15 : ERROR - 3: Failed to execute SQL Express setup. 11-26-2014,19:41:16 : Return Value of Microsoft Visual C++ 2010 Redistributable (x86) : 1603 + 11-26-2014,19:41:16 : V-225-298: ERROR: Failed to execute VC 10.0 runtime installer. Error code 1603. ***To search for information about this error, click here + 11-26-2014,19:41:16 : Review this log file for details: C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\V10.0_x86_msruntime_install.log 11-26-2014,19:41:16 : The return value for Microsoft VC++ Redistributables (x86) returned e