HPE EVA Storage
1826493 Members
3933 Online
109692 Solutions
New Discussion

Re: Uninstall HP ProLiant Smart Array P700m Clustering Support Software for Windows

 
Andre Dill
New Member

Re: Uninstall HP ProLiant Smart Array P700m Clustering Support Software for Windows

I had a similar problem. I had to remove both CP012775.exe and CP010488.exe from the repository and replace with 0 byte files of the same names (to prevent them from being re-downloaded). I then ran a catalogue rescan and now all is good.
Schinkel
Advisor

Re: Uninstall HP ProLiant Smart Array P700m Clustering Support Software for Windows

Looks like over one and a half year into this problem, HP still has found a solution: the P700m magically disappeared from our system. Nice :)

However, things are still pretty much in the dark in VCA: all our drives disappeared from the version control agent recently. They're simply not listed anymore. Reinstalling the app and rebuilding the repository does not work. HP: please help!
Curtis Ballard
Honored Contributor

Re: Uninstall HP ProLiant Smart Array P700m Clustering Support Software for Windows

This hasn't been forgotten. Features are being worked on to help address some of these errors.
UMG-ICT
Occasional Contributor

Re: Uninstall HP ProLiant Smart Array P700m Clustering Support Software for Windows

@Curtis Ballard: do you have any news concerning this issue? Recently we did the upgrade of HP SIM to version 6.3. But we are still getting the HP ProLiant Smart Array P700m Clustering Support Software for Windows in VCA.

Lukasland
New Member

Re: Uninstall HP ProLiant Smart Array P700m Clustering Support Software for Windows

Hi all,

 

I think this is finally fixed - what works for me:

 

1) Install the newly released VCA version 7.0.0.900.

 

2) In the VCA, try to install the v2.0.0.0 update for v1.3.0.0 of the "HP ProLiant PCI-express Power Management Update for Windows".

 

3) The install fails with code 3, no action taken, as it has previously.

 

4) When you go back to the list of items on the VCA home page, the latest version now correctly appears as v1.3.0.0.

 

As an aside: after upgrading to this version of the VCA, we had to re-configure which reference support pack the VCA should use. Trying to do this with authenticate by certificate fails. Using authenticate by user/pass works. This may be specific to our setup.

 

Lukas