waspsoft.com


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

Backup Exec Installation Failed With Error 1603

Contents

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 ERROR: Installation failed with error 1603. How to complete a disaster recovery plan process without funding There are paths you can take if your organization does not allow for DR plan spending. GetLastError = :0 Option 1 - Install locally Copy C:\Program Files\Symantec\Backup Exec\Agents\RAWSX64 folder from Symantec Backup Exec server to a temporary location on a client PC. (If your client is 32bit, copy have a peek here

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Great care should be taken when making changes to a Windows registry. Please provide a Corporate E-mail Address. 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

Backup Exec 12 Error Installation Failed With Error 1603

Check out templates, websites and a ... No Yes How can we make this article more helpful? HKEY_LOCAL_MACHINE | SYSTEM | CurrentControlSet | Services | VirtFile HKEY_LOCAL_MACHINE | SOFTWARE | Microsoft | Windows | CurrentVersion | DIFx HKEY_LOCAL_MACHINE | SOFTWARE | Microsoft | Windows | CurrentVersion | DIFxApp Register or Login E-Mail Username / Password Password Forgot your password?

  1. 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
  2. We'll send you an email containing your password.
  3. Backup Exec Error 1603: Fatal error during installation Error 1603 is related to the Backup Exec installation process rather than the backup process.
  4. You should also try a new tape, in case the current tape is defective.
  5. 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
  6. SearchITChannel New SUSE partner program offers product training, rebates SUSE's new channel program offers rebates of up to 30% to partners who train and certify their sales and engineering personnel on...
  7. Connect with top rated Experts 9 Experts available now in Live!
  8. GetLastError = :0   Other errors observed:  The install failed with an unexpected error: Object reference not set to an instance of an object.   ERROR: Installation failed with error -1073741819.
  9. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i… Storage Software Windows Server 2008 Disaster Recovery Advertise
  10. GetLastError = :  During push installation of Backup Exec Remote Agent for Windows System, following error is observed : "WMI is not accessible or disabled or may be blocked by the firewall"

Copy the entire RAWS32 folder from the Backup Exec media server's installation folder to the root of the C: drive on the remote server. In order to perform a successful upgrade: Wait for the Backup Exec Remote Agent service to stop and attempt the Add Server / Push Install again. Thank You! Installation Failed With Error 1603 Backup Exec Remote Agent 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.

Keep in mind that editing the Registry is dangerous; a mistake can cripple Windows and/or your applications. Backup Exec 11d Error Installation Failed With Error 1603 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 Email Address (Optional) Your feedback has been submitted successfully! If not, you may have to manually associate the DLL file with Backup Exec.

Give the Administrators group and SYSTEM Full Control. Backup Exec Installation Failed With Error 1603 Server 2008 Backup Exec Error 1068: The dependency group failed to start This is probably the most common of all the Backup Exec error codes. Sorry, we couldn't post your feedback right now, please try again later. Dell PE 2900. 0 Message Accepted Solution by:bruzmuse2009-02-12 I had to install the remote agent locally on the new server from a command prompt.

Backup Exec 11d Error Installation Failed With Error 1603

You may also refer to the English Version of this knowledge base article for up-to-date information. Join our community for more solutions or to ask questions. Backup Exec 12 Error Installation Failed With Error 1603 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 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.

Create/Manage Case QUESTIONS? navigate here GetLastError = :0Backup Exec installation logs gives the following error: (Figure 1). To troubleshoot this error, enter the command VSSADMIN LIST WRITERS in a Command Prompt window. Once the cleanup ulity removed the previous symantec backup agent, i tried installing the BE2012 agent manually and it worked. Installation Failed With Error 1603 Backup Exec 2010

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 Email Address (Optional) Your feedback has been submitted successfully! Thank You! Check This Out C:\RAWS32\>setupaofo Note: If setupaofo.cmd is run to install the AOFO, the server must be rebooted to initialize the AOFO driver. 4.

This Article Covers Backup software RELATED TOPICS Archiving Virtual server backup Cloud backup Looking for something else? Install Failed With Error Code 1603 Backup Exec Remote Agent 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 Right click on the computer to view logs for more information.

It is possible that updates have been made to the original version after this document was translated and published.

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Violin flash upgrade: Is it a high note or swan song? 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 Install Failed With Error Code 1603 Backup Exec 2014 Please login.

Backup Exec Error E000FED1: A failure occurred querying the writer status This error message is related to the VSS writer for a particular application. The following services need to be running: SQL (Bkupexec) BE Remote Agent BE Device and Media BE Server Service BE Job Engine Service BE Agent Browser Oftentimes, you can force a Four data copy management misconceptions that affect your business What are some flat backup misconceptions? http://waspsoft.com/backup-exec/backup-exec-remote-agent-error-installation-failed-with-error-1603.html GetLastError = :18     Cause The error message from MSI includes the suggestion that it's a permission issue.

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 You should therefore make a full system backup before attempting a registry modification. With on-premises storage, storage administrators must adapt or perish Storage admins show increased interest in and adoption of on-premises storage technologies such as software-defined storage and ... It is possible that updates have been made to the original version after this document was translated and published.

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. If that doesn't work, check the Application and System logs in the Event Viewer. Right click on the server to view logs for more information. No Yes How can we make this article more helpful?

If that doesn't work, check the Application and System logs in the Event Viewer. Same exact error. 1603. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?