Home > Backup Exec > Install Failed With Error Code 1603 Backup Exec Remote Agent

Install Failed With Error Code 1603 Backup Exec Remote Agent

Contents

Veritas does not guarantee the accuracy regarding the completeness of the translation. Veritas does not guarantee the accuracy regarding the completeness of the translation. OS Version = 5.2.3790, Platform 2, Service Pack 2 OS Description = Win2K3 - x86 Enterprise Edition Service Pack 2 CommandLine = c:\76483752cae2eb78c90a02de80664b\Setup.exe /q /norestart /log "C:\Documents and Settings\All Users\Application Data\Symantec\Backup DEBUG: Error 2896: Executing action WiseNextDlg failed. http://mmonoplayer.com/backup-exec/backup-exec-one-or-more-sql-database-consistency-checks-have-failed.html

The instructions for doing so are beyond the scope of this article, but can be found here. Sometimes Error 1053 is related to a permissions problem that keeps the database or one of the Backup Exec Services from starting. 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 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 Failed With Error Code 1603 Backup Exec Remote Agent

It is possible that updates have been made to the original version after this document was translated and published. However, other applications often depend on the .NET Framework and removing the framework can cause those applications to break. Here it is: After 2 days, I finally made Skype and Facebook VideoCall both work on my Windows8 Dell computer. I also removed SEP and deleted everything related to Symantec (with a snapshot and reg backup), still nothing.

You can check to ensure that the target machine does not have short file name creation disabled by navigating to the following registry entry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem Make sure the value "NtfsDisable8dot3NameCreation" is Download this guide and not only discover the latest upgrades to today's top enterprise backup vendors, but also learn where backup software works best in your computing environment. To check if the RAWS was installed, click Start | Programs | Administrative Tools | Services, and see if the Backup Exec Remote Agent for Windows Servers service is started. 0 Error Installation Failed With Error 1603. Getlasterror = 0 Ran the backup again and all is working well.

Backup Exec Error E000FED1: A failure occurred querying the writer status This error message is related to the VSS writer for a particular application. Note: If the target machine should normally have short file name creation disabled, it can be disabled after the install completes by resetting "NtfsDisable8dot3NameCreation" to 1 and rebooting. Backup Exec Error 1603: Fatal error during installation Error 1603 is related to the Backup Exec installation process rather than the backup process. New Hampshire med center turns to Pivot3 vSTAC for VDI Southern New Hampshire Medical Center put its traditional server-storage architecture out to pasture when it added ...

On the remote server, go to the command prompt, (click Start | Run, type cmd, and then click OK), and type the following commands: a. Backup Exec Agent Manual Install In many cases, the error is accompanied by a message indicating the tape drive needs to be cleaned. C:\RAWS32\>setupaa.cmd (to install the RAWS only) c. Additional services may be required depending on how Backup Exec was installed.

Final Error: 0x643 - Fatal Error During Installation.

After modifying this value, the target machine should be rebooted before attempting to launch the setup again. To troubleshoot this error, enter the command VSSADMIN LIST WRITERS in a Command Prompt window. Install Failed With Error Code 1603 Backup Exec Remote Agent Thanks for the tips Craig it helped! 0 Kudos Reply Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Installation Failed With Error Code 1603 Ccmsetup C:\>cd RAWS32 (to change to the RAWS32 directory) b.

Email Address (Optional) Your feedback has been submitted successfully! http://mmonoplayer.com/backup-exec/backup-exec-rpc-service.html Learn More Got an Altiris Question? If a reboot does not clear the error, you will have to troubleshoot the VSS writer itself (and the underlying application) rather than Backup Exec. Once the installation has been successfully un-installed, you can then debug the project to determine what caused the original error. Error: Installation Failed With Error -2146232576. Getlasterror = :0

Thanks! 0 Kudos Reply ...and the account you're CraigV Moderator Partner Trusted Advisor Accredited ‎05-10-2012 04:35 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to No problem! Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? his comment is here Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : install failed with error code 1603 Subscribe to RSS Feed Mark Topic as

Privacy Please create a username to comment. Backup Exec Error 1603 In Windows Server 2008/2008 R2, you can use the Server Manager to remove and reinstall the .NET Framework. if there was a 2012 GUID in there, or a 13.x.x.x.

This causes Windows to launch the Service Control Manager, which can be used to view the properties for the various services.

It looks like 1603 is a generic error for 'something went wrong in the install process and I'm rolling back'. C:\BEW-2b2c6c24bc5d4636841200bca55c1763\VxPushRA\VCRedist\V11.0\vcredist_x64.exe /quiet /install /norestart /log "C:\ProgramData\Symantec\Backup Exec\Logs\V11.0_x64_msruntime_install.log" Return Value of Microsoft Visual C++ 2012 Runtime : 2147944003 ERROR: Failed to execute VC 11.0 runtime installer. Step 3: Review the contents of the log file immediately above the "return value 3" string to determine which custom action or standard action failed. Install Failed With Error Code 1603 Backup Exec 2014 How an effective data archiving system can ease backup woes Load More View All Problem solve PRO+ Content Find more PRO+ content and other member only offers, here.

http://support.microsoft.com/default.aspx?scid=kb;... 0 Login to vote ActionsLogin or register to post comments R-Vijay Understanding Error 1603: Fatal Error During Installation - Comment:19 Oct 2007 : Link Thanks for this very useful KB Plug in the external drive you wish to encrypt: Make sure all previous data on the drive has been … Storage Setting the Media and Overwrite Protection Levels in Backup Exec 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. weblink Sorry, we couldn't post your feedback right now, please try again later.

Try Free For 30 Days Message Author Comment by:bruzmuse ID: 236241142009-02-12 Althought iamthecreator's comment may have worked if I had another server that was running the 12..5 agent already, I MSI (c) (D8:F8) [20:23:41:685]: Cloaking enabled. No Yes How can we make this article more helpful? It is a good idea to initially check for updates to the .NET Framework.

You may also refer to the English Version of this knowledge base article for up-to-date information. 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 To perform a local command line installation of the Symantec Backup Exec (tm) Remote Go to Solution 3 +1 4 Participants bruzmuse(3 comments) Iamthecreator LVL 23 Storage Software20 Storage10 PacMarine norwoodhelpdesk Great care should be taken when making changes to a Windows registry.

However, I did find a solution. It is possible that updates have been made to the original version after this document was translated and published.