Backup Exec Remote Agent Error Code 2
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process backup exec remote agent install failed with error code 1603 ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor
Backup Exec 12 Remote Agent
Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA backup exec 11d remote agent Site: Veritas Veritas PartnerNet Backup Exec (BE), Remote Agent for Windows Systems (RAWS / AWS) or Symantec System Recovery (SSR) installation fails with error code: 2 Article:000021610
Symantec Backup Exec Remote Agent
Publish: Article URL:http://www.veritas.com/docs/000021610 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 to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage backup exec 12.5 remote agent your Subscriptions Problem Backup Exec (BE), Remote Agent for Windows Systems (RAWS / AWS) or Symantec System Recovery (SSR) installation fails with the following error Note: Microsoft SQL Express or .Net installation may also fail with error code: 2, resulting in Backup Exec installation failure. Error Message Following entries are observed in the BKUPINST.HTM ERROR: Installation failed with error 2. GetLastError = :0 OR Install was NOT successful. Skipping post install actions for BE. The return value for Symantec Backup Exec returned error code: 2 The return code is: 2 ORThe return code from the MSI is: 2 OR BELAT failed to installVerify BELAT 1.0 is uninstalled and retry BELAT installation. The MSI Installer log will record the following error:MSI (c) (0C:F8) [
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success
Backup Exec Linux Remote Agent
Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate
Backup Exec Exchange Remote Agent
Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch backup exec remote agent for windows systems not starting Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Push or manual install of Remote Agent fails with error code: 1603 Article:000007922 Publish: Article https://www.veritas.com/support/en_US/article.000021610 URL:http://www.veritas.com/docs/000007922 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 to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe https://www.veritas.com/support/en_US/article.TECH135837 to this Article Manage your Subscriptions Problem Push install or a manual install of Remote Agent fails with the following error: Error Message Installation failed with error 1603 Excerpts from the RAWSINST.htmNOTE: For Windows 2003: RAWSINST.HTM is located in C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\LogsFor Windows 2008: RAWSINST.HTM is located in C:\ProgramData\Symantec\Backup Exec\Logs\rawsinst.htm 06-24-2010,12:57:59 : DIFXAPP: INFO: RETURN: DriverPackageInstallW (0x643) 06-24-2010,12:57:59 : DIFXAPP: ERROR: encountered while installing driver package 'X:\Program Files\Symantec\Backup Exec\RAWS\VirtFile.inf' 06-24-2010,12:57:59 : DIFXAPP: ERROR: InstallDriverPackages failed with error 0x643 06-24-2010,12:57:59 : DIFXAPP: RETURN: InstallDriverPackages() 1603 (0x643) 06-24-2010,12:57:59 : Action ended 12:57:59: InstallExecute. Return value 3. 06-24-2010,12:57:59 : Action 12:57:59: Rollback. 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 Exec Remote Agent for Windows Systems returned error code: 1603 06-24-2010,12:58:10 : Clean up Symantec installer keys.
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support https://www.veritas.com/support/en_US/article.TECH169513 Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us https://www.veritas.com/support/en_US/article.TECH73015 English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec Remote Agent Installation fails with Error backup exec "The return code from the MSI is: 1603" Article:000013673 Publish: Article URL:http://www.veritas.com/docs/000013673 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 to Subscribe Please sign in to set backup exec remote up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Remote Agent Push Install or Local Installation fails with the following Error :The return code from the MSI is:1603. 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 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” to create subkey for component '{24B4B1C2-B6AD-4690-8455-DB29A706DCE1}' Solution Enable Windows Installer Debugging -Please refer Microsoft KB for Instructions on how to enable this - http://support.microsoft.com/kb/223300 Following Errors are noticed in the Logs : Windows Installer Log - DIFXAPP: INFO: creating HKEY_USERS\S-1-5-21-3871640793-1561553363-164305601-4224\Software\Microsoft\Windows\CurrentVersion\DIFxApp\Components\{24B4B1C2-B6AD-4690-8455-DB29A706DCE1}
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet How to troubleshoot backups that fail with Error "e000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent." Article:000039522 Publish: Article URL:http://www.veritas.com/docs/000039522 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 to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem How to troubleshoot backups that fail with Error "e000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent." Error Message e000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent. Make sure that the correct version of the Remote Agent is installed and running on the target computer. UMI :- V-79-57344-3844 Cause This could happen due to one or more of the following reasons: 1. The server name in the selection list may contain an invalid character.2. Remote Agent version mismatch.3. Remote Server is Powered Down.4. Remote machine is no longer connected to the network or available for backup.5. Backup Exec is unable to connect with any remote servers.6. If the Backup Exec Remote Agent Service is stopped or disabled on the Target Machine. Solution Scenario 1: Details : This can be seen in the XML job log. The item in the selectio