waspsoft.com


Home > Backup Exec > Backup Exec Remote Agent Error Installation Failed With Error 1603

Backup Exec Remote Agent Error Installation Failed With Error 1603

Contents

Labels: 11.x and Earlier Backup and Recovery Backup Exec 1 Kudo Reply 4 Replies Re: Remote Agent installation failed with error 1603 Greg_Meister Level 6 ‎03-30-2007 05:32 AM Options Mark as 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 To perform a local command line installation of the Symantec Backup Exec (tm) Remote Go to Solution 6 Comments LVL 23 Overall: Level 23 Storage Software 20 Storage 10 Message 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 have a peek here

You should also try a new tape, in case the current tape is defective. MSP documentation: Why it's essential to scaling your business In the past, IT service managers might have gotten away with storing important info in their brains; today, having solid MSP ... Backup Exec Error E00084EC: Error reading/writing data from/to the media This is one of the Backup Exec errors that can be somewhat difficult to troubleshoot, as it corresponds to a read You can usually clear a VSS writer error by rebooting the machine.

Install Failed With Error Code 1603 Backup Exec Remote Agent

Uninstall the Remote Agent before continuing with the installation. 04-09-2010,09:45:27 : Error initializing shared data 04-09-2010,09:45:27 : ERROR: Installation failed with error 1603. The Installation should complete successfully. You should therefore make a full system backup before attempting a registry modification.

I have tried the pull install and it also does not work. Create/Manage Case QUESTIONS? I've also seen reports of this error occurring on Windows 2000 servers that have not been updated to SP4, so if that condition applies to you, address that and run the Error: Installation Failed With Error -2146232576. Getlasterror = :0 No Yes Did this article save you the trouble of contacting technical support?

This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Backup Exec 2010 R3 Remote Agent Install Error 1603 Privacy Load More Comments Forgot Password? Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Remote Agent installation failed with error 1603 VOX : Backup and Recovery : 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

However, other applications often depend on the .NET Framework and removing the framework can cause those applications to break. Backup Exec Remote Agent Manual Install GetLastError = :0  Figure1        Cause WMI Service is not started and the properties of WMI Control shows Invalid class or Access Denied.     Solution Solution 1 :- Start WMI Service  Veritas does not guarantee the accuracy regarding the completeness of the translation. To perform a local command line installation of the Symantec Backup Exec (tm) Remote Agent for Windows Servers 32-bit (RAWS) or the Advanced Open File Option (AOFO) on a remote server,

  • It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes. 1) Open registry 2) Go to HKEY_USERS\S-1-5-21-3871640793-1561553363-164305601-4224\Software\Microsoft\Windows\CurrentVersion” 3) Right click the
  • Join Now For immediate help use Live now!
  • Right click on the server to view logs for more information.
  • The command line interface.
  • Open a Registry editor, and search the registry for: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products for this GUID and delete it. Delete all instances of this key and try reinstalling the Backup Exec Remote Agent.  
  • There may be more than one.Click on the End Process button for each & respond Yes to the Task Manager Warning message popup.Rerun the installation.Method 2 (In case the windows remote
  • C:\RAWS32\>setupaofo Note: If setupaofo.cmd is run to install the AOFO, the server must be rebooted to initialize the AOFO driver. 4.

Backup Exec 2010 R3 Remote Agent Install Error 1603

Four data copy management misconceptions that affect your business What are some flat backup misconceptions? Solution Download and install .Net Framework 2.0 SP2 from the following location http://www.microsoft.com/en-us/download/details.aspx?id=1639 Once the .Net is installed successfully, try the push installation. Install Failed With Error Code 1603 Backup Exec Remote Agent Or you are searching for a contact that you erased from your MS Outlook ‘Contacts’ folder and now realized that it was important. Install Failed With Error Code 1603 Backup Exec 2014 You may also refer to the English Version of this knowledge base article for up-to-date information.

I recommend downloading and installing the latest device drivers for your tape drive. http://waspsoft.com/backup-exec/backup-exec-remote-agent-install-failed-with-error-code-1603.html The return value for Symantec Backup Exec Remote Agent for Windows Systems returned error code: 1603 Cause The User used to run remote agent Installation does not have rights  on “HKEY_USERS\S-1-5-21-3871640793-1561553363-164305601-4224\Software\Microsoft\Windows\CurrentVersion” The return value for Symantec Backup Exec Remote Agent for Windows Systems returned error code: 1603 Error Message The return code from the MSI is: 1603. The following services need to be running: SQL (Bkupexec) BE Remote Agent BE Device and Media BE Server Service BE Job Engine Service BE Agent Browser Oftentimes, you can force a 0x643 Backup Exec

Connect with top rated Experts 9 Experts available now in Live! Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Get 1:1 Help Now Advertise Here Enjoyed your answer? Check This Out If the server is not a domain controller, log in as a local admin instead of domain admin, to help eliminate any GPO issues.

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 Final Error: 0x643 - Fatal Error During Installation. About Us Contact Us Privacy Policy Advertisers Business Partners Media Kit Corporate Site Experts Reprints Archive Site Map Answers E-Products Events Features Guides Opinions Photo Stories Quizzes Tips Tutorials Videos All Next Steps Will Symantec Backup Exec restore the brand's reputation?

GetLastError = :0Backup Exec installation logs gives the following error: (Figure 1).

I re-extracted the ZIP file and am now able to install the remote agents.Thank you for help, Greg!Dave 0 Kudos Reply Contact Privacy Policy Terms & Conditions Home Windows Clients Servers Upgrades for VMware virtual servers added by Axcient, Veritas, Zerto Axcient, Veritas and Zerto upgrade their software for VMware configurations. Create/Manage Case QUESTIONS? Error Installation Failed With Error 1603. Getlasterror = 0 Email Address (Optional) Your feedback has been submitted successfully!

If that doesn't work, check the Application and System logs in the Event Viewer. Applying an update often has the same effect as reinstalling the .NET Framework, but without the potential for breaking other applications. Error Message The RAWSINST.htm file on the Remote server located in (C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs) will show the following 06-25-2012,18:53:16 : The .NET Installer returned 1603. this contact form Registry modifications should only be carried-out by persons experienced in the use of the registry editor application.

You have exceeded the maximum character limit. No Yes How can we make this article more helpful? 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 Take this quiz to catch up on IT partnership news This month's channel news quiz takes a look at a range of topics, including cybersecurity, cloud computing, distribution, partner...

Thank You! The upgrades center on data recovery, workflow ... Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. How to complete a disaster recovery plan process without funding There are paths you can take if your organization does not allow for DR plan spending.

However, cleaning the tape drive rarely corrects the problem. It is possible that updates have been made to the original version after this document was translated and published. In some cases, it can be related to a problem with the Microsoft .NET Framework. Great care should be taken when making changes to a Windows registry.