Home > Backup Exec > Backup Exec 2010 Remote Agent Install Error 1603

Backup Exec 2010 Remote Agent Install Error 1603

Contents

No Yes Did this article save you the trouble of contacting technical support? Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Manual installation of the Remote Agent for Windows Systems (RAWS) works fine, Error Message "Error connecting to the remote server. Note: The default path to the folder is C:\Program Files\Symantec\Backup Exec\Agents\RAWS32 (Figure 14); this can be changed during the installation of Backup Exec for Windows Servers. 3. Source

Right click on the server to view logs for more information. Copy the entire RAWS32 folder from the Backup Exec media server's installation folder to the root of the C: drive on the remote server. No Yes How can we make this article more helpful? No Yes Did this article save you the trouble of contacting technical support?

Backup Exec Installation Failed With Error 1603

Sorry, we couldn't post your feedback right now, please try again later. Thank You! Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We Rolling back action:  06-24-2010,12:58:10 : The return code from the MSI is: 1603 06-24-2010,12:58:10 : AgentSeqDlgs::PostInstallActions 06-24-2010,12:58:10 : Cleaning up the symc status key 06-24-2010,12:58:10 : The return value for Symantec Backup

GetLastError = :0  Solution In order for the install to proceed, any information related to the previously installed version will need to be removed.    Navigate to the RAWSINST-2010.log and search Join & Ask a Question Need Help in Real-Time? Start your default browser: In the URL location bar type spideroak.com and press enter: When you see the spideroak site, click the “Try for free” button in the upper ri… PCs Install Backup Exec 10 Remote Agent If Backup Exec 9.x/10.x for Windows 2000/2003, or an earlier version of the Open File Option (OFO) or the Remote Agent is installed on the remote server, uninstall the OFO and

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 It is possible that updates have been made to the original version after this document was translated and published. The server is running MS Server 2003 x64 R2 SP2. Click Start | Run | RegeditWarning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly.

C:\RAWS32\>setupaa.cmd (to install the RAWS only) c. Install Backup Exec 10d Remote Agent Since I only had few machines that required the agent, I haven't tested this and resorted to the first option - local installation.   Symantec Backup Exec 2010 on Windows Small Sorry, we couldn't post your feedback right now, please try again later. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec Remote Agent for Windows installation fails with an unexpected error: Invalid Class

  1. 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
  2. Thank You!
  3. Create/Manage Case QUESTIONS?
  4. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603" Article:000006395 Publish: Article URL:http://www.veritas.com/docs/000006395 Support / Article Sign In Remember me Forgot Password? Don't have
  5. No Yes About Us Our Team Vendor Partners Careers Locations Upcoming Events Technology Solutions VoIP & Video Conferencing Networking & Security Application Delivery & Mobility Virtualization & Cloud Printers & Copiers
  6. Thank You!
  7. ERROR: Installation failed with error 1603.

Manually Install Backup Exec Remote Agent 2010 R3

Veritas does not guarantee the accuracy regarding the completeness of the translation. 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 Installation Failed With Error 1603 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 Install Backup Exec 12 Remote Agent GetLastError = :0 Option 1 - Install locally Copy C:\Program Files\Symantec\Backup Exec\Agents\RAWSX64 folder from Symantec Backup Exec server to a temporary location on a client PC. (If your client is 32bit, copy

It is possible that updates have been made to the original version after this document was translated and published. this contact form It is possible that updates have been made to the original version after this document was translated and published. No Yes How can we make this article more helpful? You may also refer to the English Version of this knowledge base article for up-to-date information. Install Backup Exec 11d Remote Agent

Exiting install. Installation fails with an error on the Media Server: Install failed with error code 1603. ERROR: Installation failed with error 1603. http://sovidi.com/backup-exec/backup-exec-2010-remote-agent-install-error-connecting-remote-registry.php Comodo Backup is another solution for backing up your computer.

Solved Backup Exec Error 1603 when installing a remote agent Posted on 2009-02-05 Storage Storage Software Enterprise Software 1 Verified Solution 6 Comments 29,542 Views Last Modified: 2013-11-14 I'm attempting to Install Backup Exec Remote Agent Without Reboot Bug FIx: View Templates Folder in Azure Resource Manager Premium Storage Error Fix: "The App-V server addresses must be valid URLs" in XenApp/XenDesktop 7.9 About Us We manage your printing and Registry modifications should only be carried-out by persons experienced in the use of the registry editor application.

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

Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603 Windows System Event log on the remote Windows Workstation or Server shows below:Fig 1  Remote Agent No Yes How can we make this article more helpful? Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec (BE) 2010 push install of the Backup Exec Remote Agent Manually Install Backup Exec Remote Agent 2014 GetLastError = :0   Other errors observed:  The install failed with an unexpected error: Object reference not set to an instance of an object.   ERROR: Installation failed with error -1073741819.

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 The command line interface. blog comments powered by DISQUS back to top Follow @s_s_d_i Newsletter Subscribe to receive occasional updates on new posts. http://sovidi.com/backup-exec/backup-exec-remote-agent-install-error-1603.php Email Address (Optional) Your feedback has been submitted successfully!

Create/Manage Case QUESTIONS? Right Click on the DCOM Object that matches and select 'Properties' and select the 'Security' tabFig 5 7. 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 Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603." It seems like this is the likely problem, mentioned in the below Symantec technote: http://www.symantec.com/business/support/index?page=content&id=TECH128062