Install Failed With Error Code 1603 Backup Exec 2010
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 ABOUT error: installation failed with error -2146232576. getlasterror = :0 About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers error: installation failed with error 1603. getlasterror = :0 Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas final error: 0x643 - fatal error during installation. PartnerNet Push or manual install of Remote Agent fails with error code: 1603 Article:000007922 Publish: Article URL:http://www.veritas.com/docs/000007922 Support / Article Sign In Remember me Forgot Password? Don't have backup exec remote agent manual install 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 Push install or a manual install of Remote Agent fails
Error: Installation Failed With Error 1603. Getlasterror = :18
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. 06-24-2010,12:58:10 : AgentSeqDlgs::Misc_BE_CommonOps 06-24-2010,12:58:10 : The Installation Failed! Cause This issue may occur if: Certain driver packages are not being able install from the following location: 'X:\Program Files\Symantec\Backup Exec\RAWS\VirtFile.inf'The remote agent has recently been
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In
Backup Exec 2012 Manual Agent Install
CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results symantec endpoint protection error 1603 by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and error installation failed with error 1603 backup exec Recovery : Backup Exec : Backup Exec Agent install error 1603 VOX : Backup and Recovery : Backup Exec : Backup Exec Agent install error 1603 Subscribe to RSS Feed Mark Topic as New https://www.veritas.com/support/en_US/article.TECH135837 Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Backup Exec Agent install error 1603 jhowel Level 2 12-20-2014 09:11 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Ok, I have an Exchange 2010 server that was running low on disk space as the logs weren't commiting due to backup failures https://vox.veritas.com/t5/Backup-Exec/Backup-Exec-Agent-install-error-1603/td-p/707810 because the backup exec 2010 agent wasn't working. I took the opportunity to remove the BE agent using Programs and Features, rebooted the server etc and tried to re-push the agent getting the vague error 1603. It looks like 1603 is a generic error for 'something went wrong in the install process and I'm rolling back'. Before I really delved into the log files I followed the following article to remove the BE Agent manually: http://www.symantec.com/business/support/index?page=content&id=TECH130940 Nothing,still 1603. I also removed SEP and deleted everything related to Symantec (with a snapshot and reg backup), still nothing. I looked at the log and noticed: 12-20-2014,13:27:48 : Application: {2E214FDB-1B99-4BF3-BEE4-43B82EB1D6AE}, Command line: UPGRADINGPRODUCTCODE={856D9205-4AA3-48FB-ADD2-CE6E
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 https://www.veritas.com/support/en_US/article.000006600 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: http://www.lewan.com/blog/2010/09/28/backup-exec-2010-r2-remote-agent-install-error-code-1603 Veritas Veritas PartnerNet Backup Exec Remote Agent installation fails with ERROR: Installation failed with error 1603 Article:000006600 Publish: Article URL:http://www.veritas.com/docs/000006600 Support / Article Sign In Remember me failed with 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 your Subscriptions Problem Installation of the Backup Exec Remote Agent failed with error for Windows Systems (RAWS) fails with error: Another version of the Backup Exec Remote Agent for Windows Systems is installed on this computer. Uninstall the Remote Agent before continuing with the installation. Error Message Another version of the Backup Exec Remote Agent for Windows Systems is installed on this computer. Uninstall the Remote Agent before continuing with the installation. The RAWSINST-2010.log will contain dialog like: 04-09-2010,09:43:03 : Set RAWS Media path: C:\temp\RAWS32\install\media\ 04-09-2010,09:43:03 : RawsDlgSequence::CheckInstMode 04-09-2010,09:43:03 : BEOperations::BE_GetInstalledProdCodeVersion 04-09-2010,09:43:03 : Found 12.5.2213 RAWS32 Product. 04-09-2010,09:43:03 : Early version detected, not support RAWS Upgrade. 04-09-2010,09:43:03 : BEOperations::BE_GetInstalledProdCodeVersion 04-09-2010,09:43:03 : Found 12.5.2213 RAWS32 Product. 04-09-2010,09:45:27 : Another version of the Backup Exec Remote Agent for Windows Systems is installed on this computer. 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. GetLastError = :0 Solution In order for the install to proceed, any information related to the previously insta
Managed IT Services Managed Infrastructure Managed Cloud Hosting Managed Print Managed Data Protection Managed Network Security Managed Technology Spend Blog Contact Us Customer Support Lewan Technology Blog The latest insights, industry news, tips and topics from our team of experts. Backup Exec 2010 R2 - Remote Agent Install Error Code 1603 [fa icon="long-arrow-left"] Back to all posts [fa icon="pencil'] Posted by Lewan Solutions [fa icon="calendar"] September 28, 2010 Tweet While onsite trying to remotely push a Backup Exec 2010 R2 remote agent, we were getting a lot of the "error code 1603" messages, which stated: "Error connecting to the remote server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603." It seems like this is the likely problem, mentioned in the below Symantec technote: http://www.symantec.com/business/support/index?page=content&id=TECH128062 Our workaround was to just install the client manually on each server that wouldn't connect, instead of going through all the steps mentioned in the above technote. Written by Lewan Solutions View & Submit Comments [fa icon="envelope"] Subscribe to Email Updates Search Blog Posts in Google [fa icon="comments-o"] Follow us Get even more great content, photos, event info and industry news. [fa icon="tags"] Posts by Topic VMware (175) Citrix (131) Microsoft (116) Microsoft Windows (79) Citrix XenDesktop (70) Citrix XenApp (66) How To Guide (58) Virtualization (56) VMware vSphere (48) Managed Services (36) Cisco (33) Data Storage (31) Apple (25) Lewan Awards & Certifications (22) Lewan News & PR (18) Microsoft Exchange (18) Data Backup & Recovery (17) Microsoft Hyper-V (15) Cloud Computing (14) NetApp (13) Paper (12) Paperless Solutions (12) Data Security (10) Dell (10) Disk Performance (10) IT Solutions (10) Managed Infrastructure & Helpdesk (10) Citrix XenServer (9) Lewan Events (9) Printers & Copiers (9) Xerox (9) AppSense (8) HP (8) Networking (8) Sales Technique (8) Linux (7) Microsoft Office (7) PowerShell (7) Citrix Storefront (5) Unified Communication & Collaboration (5) VMware vCenter (5) Citrix XenMobile (4) Email Security (4) infographic (4) CommVault (3) CRN (3) Fortrust (3) Google (3) Microsoft Azure (3) Microsoft Outlook (3) Nimble Storage (3) Unidesk (3) Barracuda (2)