waspsoft.com


Home > Backup Exec > Backup Exec Remote Install Error 1603

Backup Exec Remote Install Error 1603

Contents

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 Article:000013971 Publish: Article URL:http://www.veritas.com/docs/000013971 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in No Yes Did this article save you the trouble of contacting technical support? Windows will display a list of each VSS writer and note if it is in an error state. http://waspsoft.com/backup-exec/backup-exec-remote-agent-install-error-1603.html

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 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” 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 Veritas does not guarantee the accuracy regarding the completeness of the translation.

Backup Exec Error 1603 When Installing A Remote Agent

Veritas does not guarantee the accuracy regarding the completeness of the translation. This causes Windows to launch the Service Control Manager, which can be used to view the properties for the various services. 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 Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

  1. E-Chapter Double down: When backups and archives beat as one E-Handbook Direct backup changes rules, cost of backup E-Zine Copy management system saves storage space, cash Brien Poseyasks: What Backup Exec
  2. No Yes How can we make this article more helpful?
  3. Register or Login E-Mail Username / Password Password Forgot your password?
  4. However, cleaning the tape drive rarely corrects the problem.

Create/Manage Case QUESTIONS? It is possible that updates have been made to the original version after this document was translated and published. Exiting install. 06-25-2012,18:53:16 : ERROR: Installation failed with error 1603. Error: Installation Failed With Error -2146232576. Getlasterror = :0 GetLastError = :0Backup Exec installation logs gives the following error: (Figure 1).

Sorry, we couldn't post your feedback right now, please try again later. Backup Exec Remote Agent Install Failed With Error Code 1603 Great care should be taken when making changes to a Windows registry. Four data copy management misconceptions that affect your business Data protection methods: Mounting backups vs. You may also refer to the English Version of this knowledge base article for up-to-date information.

This Article Covers Backup software RELATED TOPICS Archiving Virtual server backup Cloud backup Looking for something else? Install Failed With Error Code 1603 Backup Exec Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. Great care should be taken when making changes to a Windows registry. 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 Remote Agent Install Failed With Error Code 1603

Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Push install or a manual install of Remote Agent fails with the Any Backup Exec Services should be configured to start under the Local System Account. Backup Exec Error 1603 When Installing A Remote Agent No Yes Home Windows Clients Servers Active Directory Home and Media Simple How Tos Linux Clients Servers Mac OS X Other Reviews and Tutorials Mobile Devices Programming Android apps Web and Backup Exec 2014 Agent Install Error 1603 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

You have exceeded the maximum character limit. http://waspsoft.com/backup-exec/backup-exec-remote-agent-install-failed-with-error-code-1603.html 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 Backup Exec database is offline, turn it on and then restart the Backup Exec Services." Correcting this error can sometimes be as simple as entering Services.msc at the server's Run prompt Or you are searching for a contact that you erased from your MS Outlook ‘Contacts’ folder and now realized that it was important. 0x643 Backup Exec

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  Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. Join & Ask a Question Need Help in Real-Time? http://waspsoft.com/backup-exec/backup-exec-2010-remote-agent-install-error-1603.html Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

Backup Exec Error 1603: Fatal error during installation Error 1603 is related to the Backup Exec installation process rather than the backup process. Final Error: 0x643 - Fatal Error During Installation. Specifically, one of the VSS writers used to back up an application running on the server reported a status of failed, which caused Backup Exec to produce error E000FED1. Check the related technical articles for more information.

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

By submitting my Email address I confirm that I have read and accepted the Terms of Use and Declaration of Consent. No Yes How can we make this article more helpful? Thank You! Backup Exec Remote Agent Manual Install I recommend downloading and installing the latest device drivers for your tape drive.

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 GetLastError = :0" Article:000016850 Publish: Article URL:http://www.veritas.com/docs/000016850 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile After making any changes, it is a good idea to reboot the server. this contact form Symantec Backup Exec has been around in one form or another since the early 1990s and has a reputation as one of the more reliable backup products on the market.

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 The VSSADMIN command can be used to determine which VSS writer is causing your problem.