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

Backup Exec Installation Failed With Error 1603

Contents

Backup Exec Error E000FED1: A failure occurred querying the writer status This error message is related to the VSS writer for a particular application. 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 Veritas does not guarantee the accuracy regarding the completeness of the translation. However, other applications often depend on the .NET Framework and removing the framework can cause those applications to break. Source

GetLastError = :0" Error Message ERROR: Installation failed with error 1603. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Same exact error. 1603. Keep in mind that editing the Registry is dangerous; a mistake can cripple Windows and/or your applications.

Backup Exec 12 Error Installation Failed With Error 1603

Once the cleanup ulity removed the previous symantec backup agent, i tried installing the BE2012 agent manually and it worked. Any Backup Exec Services should be configured to start under the Local System Account. Sorry, we couldn't post your feedback right now, please try again later. 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

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 Email Address (Optional) Your feedback has been submitted successfully! Hedvig storage update offers multicloud capabilities Hedvig outlined its vision for a Universal Data Plane spanning public and private clouds, as it announced an updated version of ... Installation Failed With Error 1603 Backup Exec Remote Agent Labels: 2012 Agents Backing Up Backup and Recovery Backup Exec Basics Best Practice Configuring Downloads Error messages Features Installing Integration Managing Backup Devices Monitoring Patch Recovering Reporting Restore Rules Tip-How to

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. Backup Exec 11d Error Installation Failed With Error 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 Figure 1. Installation log file "bkupinst.htm" path: Windows Server 2003: :\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\LogsWindows Server 2008: :\ProgramData\Symantec\Backup Exec\Logs Solution Method 1: Open Task ManagerClick on the Processes No Yes How can we make this article more helpful?

If this doesn't work, try a manual install of the RAWS agent: http://www.symantec.com/business/support/index?page=content&id=TECH30491 Thanks! Backup Exec Installation Failed With Error 1603 Server 2008 If replacing the tape doesn't work, the problem is most likely related to device drivers or the tape drive itself. Hi zak, Make sure that any CraigV Moderator Partner Trusted Advisor Accredited ‎05-10-2012 01:14 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Veritas does not guarantee the accuracy regarding the completeness of the translation.

Backup Exec 11d Error Installation Failed With Error 1603

All rights reserved. Get 1:1 Help Now Advertise Here Enjoyed your answer? Backup Exec 12 Error Installation Failed With Error 1603 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 Backup Exec Installation Failed With Error 1603 Windows 2008 Error Message Another version of the Backup Exec Remote Agent for Windows Systems is installed on this computer.

Join & Ask a Question Need Help in Real-Time? http://sovidi.com/backup-exec/backup-exec-agent-error-installation-failed-with-error-1603.php 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. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Final error: 0x643 - Fatal error during installation.   Error generated in the Remote Agent install log: FATAL ERROR: Error 1921. Installation Failed With Error 1603 Backup Exec 2010

Five challenges when buying backup and restore software Veritas, Veeam top choices of data backup app users Copy management systems demystified Load More View All Evaluate Develop copy management systems for In many cases, the error is accompanied by a message indicating the tape drive needs to be cleaned. In most of the cases I have seen, the problem is connected to a permissions issue related to the account being used to run the service. have a peek here 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

Right click on the server to view logs for more information. Install Failed With Error Code 1603 Backup Exec Remote Agent Option 2 - Install via Group Policy Symantec Backup Exec Remote Agent can be installed via Group Policy as described here. I recommend downloading and installing the latest device drivers for your tape drive.

This email address is already registered.

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 No Yes Did this article save you the trouble of contacting technical support? You should also launch the Backup Exec Console and click on Tools | Backup Exec Services | Service Credentials | Change Service Account Information to ensure Backup Exec is configured to Install Failed With Error Code 1603 Backup Exec 2014 You should also try a new tape, in case the current tape is defective.

Not all occurrences of Symantec Backup Exec error 1053 are related to the .NET framework. 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 Thank You! Check This Out SearchStorage Virtual Instruments teaches VirtualWisdom NAS expertise Virtual Instruments taps into expertise gained through the Load DynamiX merger to teach its VirtualWisdom analytics products to ...

If that doesn't work, check the Application and System logs in the Event Viewer. No Yes How can we make this article more helpful? Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is possible that updates have been made to the original version after this document was translated and published.

By submitting you agree to receive email from TechTarget and its partners. Sorry, we couldn't post your feedback right now, please try again later. Return value 3.:ERROR: Installation failed with error 1603. 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 

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 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 waits 3 minutes before it reports a service stop failure. This email address doesn’t appear to be valid.

No Yes How can we make this article more helpful? If you still have trouble after the device driver update, run a backup from Windows Server Backup. Thank You! On the remote server, go to the command prompt, (click Start | Run, type cmd, and then click OK), and type the following commands: a.

Covered by US Patent.