BE 9.1 to 10d upgrade fails

[James_Ingram]

Upgrade fails, action rollsback and last lines of the log are as follows, any ideas?...

10-27-2005,12:09:53 : Property(S): MOVETABLE_SOURCE33 = C:\temp\VERITAS\WINNT\INSTALL\BE\Bin\

10-27-2005,12:09:53 : Property(S): MOVETABLE_SOURCE32 = C:\temp\VERITAS\WINNT\INSTALL\RAWSX64\

10-27-2005,12:09:53 : Property(S): MOVETABLE_SOURCE34 = C:\temp\VERITAS\WINNT\INSTALL\BE\Bin\

10-27-2005,12:09:53 : Property(S): RENAMED_PATH.380C600C_E17D_459C_91FA_D5C4585F8825 = \oemtap0.inf

10-27-2005,12:09:53 : Property(S): SQLServiceName = MSSQL$BKUPEXECDLO

10-27-2005,12:09:53 : Property(S): OutOfDiskSpace = 0

10-27-2005,12:09:53 : Property(S): OutOfNoRbDiskSpace = 0

10-27-2005,12:09:53 : Property(S): PrimaryVolumeSpaceAvailable = 0

10-27-2005,12:09:53 : Property(S): PrimaryVolumeSpaceRequired = 0

10-27-2005,12:09:53 : Property(S): PrimaryVolumeSpaceRemaining = 0

10-27-2005,12:09:53 : Property(S): ProductToBeRegistered = 1

10-27-2005,12:09:53 : 1: INSTALL 2: 3

10-27-2005,12:09:53 : Upgrade state set to 7

[Amruta_Purandar]

Hello,

Please search for the value "return value 3" and send the related part of the log to further troubleshoot this issue.


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[James_Ingram]

Cheers, that just answered half my question. I searched for "return value 3' and found the folder in the path just prior to the return value had been renamed to 'backupexec9.1' i renamed it back to 'backupexec' and tried again. Now I get an error message dialog box saying:

Error 1309. Error reading from file D:\apps\bkupexec\DATA\BEWINNT7.SCH. Verify that the file exists and that you can access it.

The file exists, if I click Ignore it asks me the same question for another file in that same folder. They all exist, should I just continue to ignore all files or will this effect installation? All BackupExec services are stopped. I have run a chkdsk on the D: drive and it indicates there are some logical disk problems that will be resolved after a reboot - I will reboot the server tonight and report back on Monday. Cheers.

[James_Ingram]

Managed to squeeze a reboot in at lunchtime today, the disks checked out ok. I tried the install again but it failed on exactly the same issue. This server has not had a decent backup for a while so I uninstalled BackupExec 9.1 then rebooted. Next I tried installing BackupExec 10d again, this time ANOTHER failure on installing. A message box popped up tellining me installation could not continue because the database versions were different from what was being installed and what was already installed. Thing is I had uninstalled BackupExec and renamed the existing BackupExec folder to BackupExec.OLD. This should have been a clean install rather than upgrade. There is no other instance of backup exec on the server. here is the installation log:

10-28-2005,13:53:54 : Unable to start changers at this time.

10-28-2005,13:53:54 : Executing BEMain_ConfigMMS. Configuring MMS components.

10-28-2005,13:53:54 : Executing VerifyBEDBVersion.
10-28-2005,13:53:54 : DRIVER={SQL Server};SERVER=NEWPLYMTH\BKUPEXEC;Trusted_Connection=Yes
10-28-2005,13:53:56 : Connected to SQL Server.
10-28-2005,13:53:57 : ADAMM Version Number = 9.000001
10-28-2005,13:53:57 : The Backup Exec database version you are trying to use does not match the version of this install. Schema changes have been performed on this database which do not match the executables currently being installed. Install will not be able to continue at this time. Please visit the Symantec support web site for more information.

10-28-2005,13:54:24 : Action ended 13:54:24: InstallFinalize. Return value 2.

10-28-2005,13:54:24 : Action 13:54:24: Rollback. Rolling back action:

10-28-2005,13:54:24 : Configuring VERITAS Backup Exec. Please wait...

10-28-2005,13:54:24 : RB_ConfigInstall

10-28-2005,13:54:26 : Rolling back install of BE services.

10-28-2005,13:54:26 : Rolling back install of BE database.

I will try uninstalling the MSSQL\BKUPEXEC$ database and rebooting next then trying to install again, I would imagine this should do it?