Uninstall HP ProLiant Smart Array P700m Clustering Support Software for Windows

[Schinkel]

We have a brand new server (proliant ML350G6) running windows server 2008. Only the integrated P410i controller is present in this system, however the driver mentioned in the subject was installed automatically, version 1.3.0.0. In the version control manager it states we should upgrade to version 2.0.0.0 but that does not work, probably because we dont have the P700m in the system at all.

Since we have a strange problem with this server hanging quite frequently, we suspect this driver to be the problem.

How to get rid of it? We cannot find a way to uninstall it.

Thanks in advance for your help!

This might need the attention of HP since we're not the only one having this software automatically installed on their system without having the P700 on their system.

Please refer to tread 1355026 as well.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1250275891759+28353475&threadId=1355026

[Thorsten Landwehr]

We got the same Problem on all ML350G5 with Windows Server 2003.
Is there a solution yet?

Kind regards
Thorsten

[Schinkel]

Not as I know off, HP: could you please respond to this?

[Schinkel]

Anyone?

[Jens Teglhus Møller]

Hi

There seems to be some kind of mixup in the naming of packages. If you uninstall (using 'Add or Remove Programs') the "HP ProLiant PCI-express Power Management Update for Windows' the 'HP ProLiant Smart Array P700m Clustering Support Software for Windows' goes away.

If you click the 1.3.0.0 link in VCA you also get the description of the PCI-express stuff, that is what gave me the clue to try and uninstall that one.

Very strange.

Best regards Jens

[Rob C.]

I can confirm this as well. I uninstalled the HP ProLiant PCI-express Power Management Update for Windows on a DL380 G3 and then refreshed my inventory in VC - the update to HP ProLiant Smart Array P700m Clustering Support Software for Windows Version 2.0.0.0 was gone. I then installed the PCI-express update version 1.3.0.0 D (cp010920.exe), rebooted and checked VC - the clustering update was back.

HP please correct this issue.

[PZel]

We have the same kind of problems when installing PSP 6.40 (6.30?) on our ML/DL series.
The express setup of HPSUM is standard installing PCI-Express Update and P700m clustering software, but on the www.hp.com support and drivers/chipset these drivers
are only for BL460c and not for ML/DL.
It looks like HPSUM thinks that the ML/DL is a BL460c, maybe because of a faulty Power Management Controller driver ??
You can uninstall it with AddRemoveProg but in our case in the VCA the firmware level of the P400 disappears strange enough ??
(but it is still working)

[ChrisM_22]

I've found the same issue on a BL460c G1 with Win 2008R2, but in my case the server's been running fine.

I used SmartStart 8.4 to do the OS install and it installed version 1.3.0.0 of the "HP ProLiant Smart Array P700m Clustering Support Software for Windows", which I don't have. I ave an E200i embedded controller. Uninstalling the "HP ProLiant PCI-express Power Management Update for Windows" removed the P700m from the Version Control Agent.

Hopefully HP will fix this soon, as it seems to have been around for a while.

[HalV]

I hate to do a "me too" posting but this affects most of our HP servers also. The issue seemed to pop up after upgrading the version control agent from the 2.xxx version to the 6.xxx version. Uninstalling the pci-express power management item from add/remove programs does make the erroneous p700 clustering update go away in the VCA, but now the VCA no longer shows the power management controller firmware update.

[Curtis Ballard]

The revision control clash between the power management and P700m cluster control is being worked and is understood now. An update should be available soon with a fix.

The original poster mentioned the system locking up. We can't find anything to indicate that the driver would be related to that problem but don't have much information about the configuration. Do you have an open service call that could be referenced?

[Mark Harwood - UK]

HP is there any news on this update. Its been 3 months since the last update.

[Schinkel]

we have occasional spontaneous reboots on this machine. also several items (drives, sas expander) in the vcagent are not listed. several open support cases you could look it up with our serial: CZJ91902XA

[Révy]

Hi Schinkel

I'm having the same problem like you do, also on a ML350 G6 with Windows Server 2008 W32 installed.

I also have the problem with the frequently server hang. I also had a long list of open cases with this server. Had several Hardware replacements and in the end HP even replaced the whole Server. Yet still the serverhang continious.

I'm trying my luck now with the Microsoft support. I'll let you know if I can get some help there. Ofcourse it'd be nice if someone has a solution for this problem, to let me know it.

Kind regards.

[Révy]

Hello Schinkel,

We finally solved the Problem with the Server freezing (well at least he didn't freeze for nearly a week).

Are you running an Pervasive PSQL Database on that Server? If so could you please disable the XIO Cache?

Start -> Run... -> cmd -> xiomgr -stop

and

Start -> Run... -> cmd -> xiomgr -disable

After a reboot the Serverhangs should've stopped.

Also the Problem with the P700m appearing in the VCA was solved by uninstalling the "HP ProLiant PCI-express Power Management Update for Windows", like ChrisM_22 already said before.

Hope that helps you out. It would be nice if you could let me know if that also resolved you're problem.

Kind Regards,

Révy

[Dario Palermo]

Same here on many servers (no hangs, just the VCA error).

No one asked, IMHO, the right question:

should we remove or not the package "HP ProLiant PCI-express Power Management Update for Windows Version 1.3.0.0D" just to make the problem go away?

I think not...

Sadly... still no news from HP.

Best regards,

Dario Palermo

[Schinkel]

Unbelievable such a simple thing remains unsolved for such a long time...

I wish this was the only (minor) problem we have with HP. After due consideration (and tens of unsolved but automatically closed cases) we are changing to Dell hardware.

Good luck everyone here...

[Curtis Ballard]

I see that people still seem to be having problems with this. I double checked with the developers and they reported that the release on the web 7/21/10 for the P700m is the release that has the new key file name that was intended to fix this issue.

There shouldn't be a clash with the signatures anymore.

It may be necessary to uninstall both packages then reinstall using the newest versions.

If you are still having problems with the latest versions installed some details on whic packages are actually installed and what was used to install them would be useful. The PCI-express SW isn't supposed to be in SmartStart.

[Dario Palermo]

I had cp010920 installed on 6 out of 7 servers (2 bl680 and 4 bl460). Can't recall where it came from.

The server without it, didn't complain about missing it. Also, it didn't ask me to install CP012775.

Then I installed cp010920 manually: the server gladly took it and, after installation, also this last server started asking me to install CP012775.

Now... it could have been my mistake to install manually the package on the last server but, for the other 6, it wasn't so. I used (100% sure) some Support Pack (the latest available at the time, I suppose).

Now what? Do I simply unistall cp010920 manually from all the servers? After that, do I need to install an updated version of that package or can I live happy without it?

Thanks

Best regards,

PS
IMHO the ho management software is not so bad after all. Some kind of problems are likely to happen in every system of this kind: Micosoft WSUS also as similar problems every now and then...

Dario Palermo

[Marcin.Trzyna]

I have uninstalled HP ProLiant PCI-express Power Management. I confirmed that the "HP ProLiant Smart Array P700m Clustering Support Software for Windows" entry disappeared from VCA inventory. Than I've installed cp010920.exe, which is the current version of HP ProLiant PCI-express Power Management - and the "HP ProLiant Smart Array P700m Clustering Support Software for Windows" entry appeared again on the list in VCA. Hence - the problem lies not in the "HP ProLiant Smart Array P700m Clustering Support Software for Windows" component (which we had never installed at all), but in the "HP ProLiant PCI-express Power Management Update for Windows" component, which incorrectly presents itself to VCA as "HP ProLiant Smart Array P700m Clustering Support Software for Windows".

Curtis, if you helped to resolve this issue till the happy end, you would turn off thousands of yellow exclamation marks in VCAs all around the world, so please help us... You are our only hope...

[Curtis Ballard]

Thanks for posting further information. I've been talking with the P700m clustering software team but it looks like the problem may lie elsewhere since the last poster is clear that they don't have that software and still have the problem. I'll get somebody from the power management team to take a look.

[Dario Palermo]

Some more info: I zeroed the repository and made a new one from scratch.

1) In the rep. folder now I've got:

a) CP010920 - HP ProLiant PCI-expres Power Management Update for Windows v1.3.0.0D

b) CP012775 - HP ProLiant Smart Array P700m Clustering Support Software for Windows v2.0.2

c) CP012962 - HP ProLiant Smart Array P700m Clustering Support Software for Windows v2.0.2B

2) In the VCRM, listing the components, I've got:

Driver - Chipset
HP ProLiant Smart Array P700m Clustering Support Software for Windows Version 2.0.2.0 (English (US))
HP ProLiant Smart Array P700m Clustering Support Software for Windows Version 2.0.0.0 (English (US)) (* this is CP010488)
HP ProLiant PCI-express Power Management Update for Windows Version 1.3.0.0D (English (US))
HP ProLiant PCI-express Power Management Update for Windows Version 1.3.0.0C (English (US))
HP ProLiant PCI-express Power Management Update for Windows Version 1.3.0.0B (English (US))
HP ProLiant Smart Array P700m Clustering Support Software for Windows Version 1.0.0.0 (English (US))
HP ProLiant Smart Array P700m Clustering Support Software for Windows Version 2.0.2.0B (English (US))

*****STRANGE THING******
the 2.0.2B version is listed at the bottom... maybe because all other updates in the category are seen as the same (signature error?), therefore ordered by version (newer on top).
This explanation is consistent with the issue we all are having.
************************

3) none of the server is asking me to install CP010920 - HP ProLiant PCI-expres Power Management Update for Windows v1.3.0.0D

I'm going to install manually CP010920 and then, one at a time, delete from the repository CP012775 and CP010488.

Users needing the P700m Clustering Support will be safe, as CP012962 is the newer version available and will stay in the rep.

I'll update in a few minutes...

Best Regards

Dario Palermo

[Dario Palermo]

Update:

1) installed CP010920: the system now asks for CP012775
2) deleted CP012775 and made a rep. rescan to reflect it (waited for catalog rebuilding, as confirmed in the the VCRM log)

NO MORE PROBLEMS

CP010488 doesn't need to be removed.

Someone shold just test this solution on a system with P700m to check if the Clustering Software update works correctly (it should pick version 2.0.2B)

Best Regards

Dario Palermo

[Curtis Ballard]

Great work Dario - It sounds like the original signature conflict doesn't clean up with a simple uninstall/reinstall but requires manually deleting CP012775 and rebuilding the repository.

I'll relay that back to the team. I don't know if there is something that can be done to help clean that up automatically or if they will need to publish an advisory for how to clean up.

[Eric Datwyler]

I did what Dario posted and it worked for 1 day. VCA correctly showed the Power Management update instead of the P700m clustering software. This was until I came in this morning and noticed it was back. The nightly VCRM sync re-downloaded the CP12775 update and thus my servers are back to needing the P700m clustering software update.

This seems to be an issue HP needs to fix.

[JonInfrastructure]

Sorry for the 'me too' post but I figured if more people said the same issue was effecting them there was a possibility it may make HP up the priority. This has been going on for way too long HP, I'm sick of my version control agents not showing up as green, as I'm a patch Nazi...