Backup Exec 2010 Error Code 1603
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center
Installation Failed With Error 1603 Getlasterror 0
Support Community MyVeritas Customer Success Licensing Programs Licensing Process the return value for symantec backup exec returned error code 1603 ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal
Backup Exec Agent Error 1603
Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec 2010 or Remote Agent error 1603 backup exec remote agent install or upgrade fails with error "ERROR: Installation failed with error 1603. GetLastError = :0" Article:000006629 Publish: Article URL:http://www.veritas.com/docs/000006629 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 backup exec install error 1603 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 Backup Exec 2010 or Remote Agent install or upgrade fails with error "ERROR: Installation failed with error 1603. GetLastError = :0" Error Message ERROR: Installation failed with error 1603. GetLastError = :0Backup Exec installation logs gives the following error: (Figure 1). Figure 1. Installation log file "bkupinst.htm" path: Windows Server 2003:
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
Symantec Agent Install Error 1603
Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research install failed with error code 1603 backup exec 2014 Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português
0x643 Backup Exec
Español USA Site: Veritas Veritas PartnerNet Installation of Backup Exec Remote Agent fails with "The .NET Installer returned 1603. Exiting install. ERROR: Installation failed with error https://www.veritas.com/support/en_US/article.TECH128630 1603. 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 Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products https://www.veritas.com/support/en_US/article.TECH191721 Article Languages Subscribe to this Article Manage your Subscriptions Problem While performing push installation or Local installation of Backup Exec 2010 Remote Agent on a Remote server, the installation fails with Error 1603. 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. Exiting install. 06-25-2012,18:53:16 : ERROR: Installation failed with error 1603. GetLastError = :0 Cause This issue occurs if correct version of .Net Framework is not present on the remote server or it is corrupt. Solution Download and install .Net Framework 2.0 SP2 from the following location http://www.microsoft.com/en-us/download/details.aspx?id=1639 Once the .Net is installed successfully, try the push installation. 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 have been machine-translated. It is possible that updates have been mManaged 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 http://www.lewan.com/blog/2010/09/28/backup-exec-2010-r2-remote-agent-install-error-code-1603 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 http://www.symantec.com/connect/articles/understanding-error-1603-fatal-error-during-installation 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 backup exec 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 error code 1603 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 (130) Microsoft (115) Microsoft Windows (79) Citrix XenDesktop (69) Citrix XenApp (65) How To Guide (57) Virtualization (55) 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 (6) 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 Outlook (3) Nimble Storage (3) Unidesk (3) Barracuda (2) Microsoft Azure (2) Product Announcements (2) Fax Solutions (1) Microsoft System Center Configuration Manager (1) NetScaler (1) RES Software (1) see all [fa icon="calendar"] Recent Posts Citrix Provisioning Service
Français Deutsch 日本語 Español Help Video Screencast Help As we strive to continually improve your experience on our site, please help us by taking this survey and tell us about your satisfaction level using Symantec Connect. One lucky winner will receive 500 Connect points! * Take the survey. Understanding Error 1603: Fatal Error During Installation Created: 15 Oct 2007 | 11 comments Language TranslationsMachine TranslationsDeutsch Français Español 简体中文 日本語 R-Vijay +2 2 Votes Login to vote Tweet This error message is displayed by the Microsoft Windows Installer engine and is a general error code that indicates a problem occurred during the installation. Read on to learn how to sidestep this speed bump. The following is a non-exhaustive list of known causes for this error: Short file name creation is disabled on the target machine. An Install Script custom action is prototyped incorrectly. A file is locked and cannot be overwritten. The Microsoft Windows Installer Service is not installed correctly. The Windows Temp folders are full. The setup was corrupted after installation and, therefore, fails with this error during un-installation. An older version of Install Shield Developer is being used. A general error occurred during the installation. Print and File sharing is not installed or enabled when installing MSDE 2000. How to Avoid this Error The following solutions have resolved this error in the majority of cases: Make sure short file name creation is enabled on the target machine. 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 equal to 0. This indicates that short file name creation is enabled. A value of 1 indicates that this functionality is disabled. You should change the value to 0. After modifying this value, the target machine should be rebooted before attempting to launch the setup again. 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