I am running an NFR (Not For Resale) version of BackupExec 10.5485 on a Windows 2003 SP1 server. I use a Sony Lib-162 Library with twin drives and I use the Veritas Device Drivers. Windows RSM is disabled. When I try to install BackupExec 10 SP1 for 10.5484 it bombs out of the installer with the following message: "The wizard was interupted before Veritas BackupExec for Windows servers could be completely installed" and logs the following error to the application log "Product: VERITAS Backup Exec for Windows Servers - Update '{90BBDB2C-A880-425A-B54F-DA7DF734F3D9}' could not be installed. Error code 1603"I have tried the following:1) Checked user permissions on the source folder (root of the C: drive of the Backup Server itself).2) Checked the "System" user has correct permissions3) Ran a repair installation of BackupExec4) Removed and reinstalled BackupExec5) Tried extracting the "bepatch.msp" manually and running it6) Tried running the install as a silent installNone of this have worked. Any suggestions would be appreciated.

Sorry I've written that I run NFR 10.5485. This is a typo - I run 10.5484.

I'm having the same error as well. I am using BE10 on W2k3 SP1 also. I think it may have to do with SP1 for W2k3,..

I have the same issue on a W2k domain controller. I have an identical DC that installed BE just fine. I have rebooted, tried again, same result, so it's not just a W2k3 issue.

The user that the services were using was the same one I was logged in with. I changed the user that the services uses, and it installed just fine. I'm not sure if it has anything to do with it or not, but I am also running the upgrade via remote desktop.

Installing remotely is not recommended, try running the install from the actual server itself.

Unable to install SP1 for BackupExec 10.5484

26 Replies

Richard_Watki1
Level 3
20 years ago
Sorry I've written that I run NFR 10.5485. This is a typo - I run 10.5484.
Devious
Level 2
20 years ago
I'm having the same error as well. I am using BE10 on W2k3 SP1 also. I think it may have to do with SP1 for W2k3,..
Alice_Stewart
Level 5
20 years ago
I have the same issue on a W2k domain controller. I have an identical DC that installed BE just fine. I have rebooted, tried again, same result, so it's not just a W2k3 issue.
Devious
Level 2
20 years ago
The user that the services were using was the same one I was logged in with. I changed the user that the services uses, and it installed just fine. I'm not sure if it has anything to do with it or not, but I am also running the upgrade via remote desktop.
A_A_4
Level 2
20 years ago
Installing remotely is not recommended, try running the install from the actual server itself.
Imran_Raoof_3
Level 2
20 years ago
Hi
Here is the trick which worked for me. When I faced the problem of installing BE SP1 i logged off and login again. make sure you are using the administrator account.

Regards
Imran
Angel_something
Level 3
20 years ago
I Had the smae problem. i could not install SP1. What i did was, configure Backup Exec First and then run the SP1.
and it worked fine!
steve_burkett
Level 4
20 years ago
Am currently having the same issue, for me its because Backup Exec can't update the schema of the Backup Exec database which is housed on a remote SQL server as opposed to MSDE on the local server.

Check the Backup Exec installation log file 'bkupinst.log' in your Windows directory for the reason it failed.
Richard_Watki1
Level 3
20 years ago
I tried again today after rebooting but still no luck. It is not even logging anything to the backupexec install log. I wouldn't bother but for the issue of being able to restore a SP1 Windows 2003 server to a working state without these BackupExec updates!
David_Marten
Level 2
20 years ago
This behavior has been documented when the BEDB resides on a different machine than where the Backup Exec application is installed.

http://support.veritas.com/docs/276637