Application Perf Mgmt (BAC / BSM) Support and News Forum
Showing results for 
Search instead for 
Do you mean 

HP BSM 9.23 patch fails on 9.22.131 DPS.

SOLVED
Go to Solution
Highlighted
Respected Contributor Respected Contributor

HP BSM 9.23 patch fails on 9.22.131 DPS.

Our installation of the 9.23 patch has failed on a 9.22.131 DPS. The gateway installation was fine.

 

The installation wizard cites the following:-

 

DPSInstallFailure.png

 

Has anyone seen this before?

 

1 ACCEPTED SOLUTIONS
Respected Contributor Respected Contributor

Re: HP BSM 9.23 patch fails on 9.22.131 DPS.

Ok, it appears the disk space on the C:\ volume was the root cause. The d:\hpbsm volume had enough space but other shared components appear to be installed in c:\

 

Silly me thinking the pre installation disk space check would suffice!

 

 

3 REPLIES
Respected Contributor Respected Contributor

Re: HP BSM 9.23 patch fails on 9.22.131 DPS.

Looking in the log

 

(C:\Users\TEMP\AppData\Local\Temp\HPOvInstaller\HPBsm923_9.23\HPBsm923_9.23_2014.01.07_11_46_HPOvInstallerLog.html)

 

we can find the following exception:-

 

Exception while reading registryFatal Error , problem executing invokeN Exit Code : -1 ><ERROR : !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! **** ERROR: problem executing script : C:\Users\TEMP\AppData\Local\Temp\2\OVII_rad1E8E5.tmp.vbs !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Respected Contributor Respected Contributor

Re: HP BSM 9.23 patch fails on 9.22.131 DPS.

Oh, and we also detected this in the Windows Application Event Log:-

 

Product: HP BSM SDR 09.23.211 -- Disk full: Out of disk space -- Volume: 'C:'; required space: 111,616 KB; available space: 76,712 KB.  Free some disk space and retry.

 

 

Respected Contributor Respected Contributor

Re: HP BSM 9.23 patch fails on 9.22.131 DPS.

Ok, it appears the disk space on the C:\ volume was the root cause. The d:\hpbsm volume had enough space but other shared components appear to be installed in c:\

 

Silly me thinking the pre installation disk space check would suffice!