Backup Exec 11d SP4 installation fails

[Stefan-P]

I have a Symantec Backup Exec 11d installation with Service Pack 1 and Hot Fixes 19,21-28 installed on Windows Server 2003 Standard Edition SP2.

Service Pack 4 installation fails with the following errors.


bkupinst.htm:

11-11-2009,11:48:15 : Setup.ini.0B400D21_0933_47C3_86AE_B09DF0B01D80 was not removed from RemoveFile table.
11-11-2009,11:48:15 : Entering PatchSetup.exe
11-11-2009,11:48:15 : Command Line: /NAME:SP-4 /UI:FULL
11-11-2009,11:48:15 : Executing GetPatchInfo.
11-11-2009,11:49:16 : Das Patchpaket konnte nicht geöffnet werden. Stellen Sie sicher, dass das Patchpaket vorhanden ist und dass Sie darauf zugreifen können, oder wenden Sie sich an den Hersteller, um sicherzustellen, dass es sich um ein gültiges Patchpaket für den Windows-Installationsdienst handelt. C:\WINDOWS\Installer\e05dd61.msi
11-11-2009,11:49:16 : V-225-136: The patch failed to install. Return code: 1635 ***To search for information about this error, click here
11-11-2009,11:49:17 : InstallManager.dll has been updated in cached MSI Binary table.
11-11-2009,11:49:17 : Exiting PatchSetup.exe 

Vxinst.log:
 

<Session>
 <logdata>
   <caller>0</caller>
   <type>0</type>
   <datetime>11-11-2009,11:48:15 </datetime>
   <msg>Setup.ini.0B400D21_0933_47C3_86AE_B09DF0B01D80 was not removed from RemoveFile table.</msg>
 </logdata>
 <LogFileHeader>Symantec Backup Exec (TM) 11 for Windows Servers Patch Log : SP-4</LogFileHeader>
 <logdata>
   <caller>0</caller>
   <type>0</type>
   <datetime>11-11-2009,11:48:15 </datetime>
   <msg>Entering PatchSetup.exe</msg>
 </logdata>
 <logdata>
   <caller>0</caller>
   <type>0</type>
   <datetime>11-11-2009,11:48:15 </datetime>
   <msg>Command Line: /NAME:SP-4 /UI:FULL</msg>
 </logdata>
 <logdata>
   <caller>0</caller>
   <type>0</type>
   <datetime>11-11-2009,11:48:15 </datetime>
   <msg>Executing GetPatchInfo.</msg>
 </logdata>
 <logdata>
   <caller>0</caller>
   <type>0</type>
   <datetime>11-11-2009,11:49:16 </datetime>
   <msg>Das Patchpaket konnte nicht geöffnet werden. Stellen Sie sicher, dass das Patchpaket vorhanden ist und dass Sie darauf zugreifen können, oder wenden Sie sich an den Hersteller, um sicherzustellen, dass es sich um ein gültiges Patchpaket für den Windows-Installationsdienst handelt.
C:\WINDOWS\Installer\e05dd61.msi</msg>
 </logdata>
 <logdata>
   <caller>0</caller>
   <type>2</type>
   <datetime>11-11-2009,11:49:16 </datetime>
   <msg>V-225-136:  The patch failed to install.  Return code: 1635  ***To search for information about this error, click &lt;a href="http://support.veritas.com/umi/V-225-136" target="main"&gt;here &lt;/a&gt; </msg>
 </logdata>
 <logdata>
   <caller>0</caller>
   <type>0</type>
   <datetime>11-11-2009,11:49:17 </datetime>
   <msg>InstallManager.dll has been updated in cached MSI Binary table.</msg>
 </logdata>
 <logdata>
   <caller>0</caller>
   <type>0</type>
   <datetime>11-11-2009,11:49:17 </datetime>
   <msg>Exiting PatchSetup.exe</msg>
 </logdata>

SP3 installation also fails with the same errors.
 

[CraigV]

Hi,

Have you tried to stop the services first, and then make sure there are no BE *.exes running before tying this one more time?

Laters!

[Stefan-P]

Stopping the services made no difference.

[jifru]

Found SP3 does make changes to your system when it fails, even though it said it did not change anything.  Look at the login account on the SQL server (BKUPEXEC) service and the Backup Exec services, especially the DLO administration one.  I normally use domain credentials to start the services but the SP changed the SQL BKUPEXEC instance and the DLO admin service to local administrator login accounts.  Leave them as local and supply the correct password.  The service pack will stop and start the services as part of the install.  SP3 and SP4 then installed fine.  If you have an urlmon.dll issue after the SP install, reboot your server.  After reboot the urlmon issue will go away but you may find the DLO admin service did not start automatically.  I changed it back to the domain admin account and all is well.

[Stefan-P · Accepted solution]

I solved the problem in reinstalling the Backup Exec software. After the reinstallation I was able to install Service Pack 4.