HP ProLiant Smart Array Device Manager Extension Problems

[Melanie Sang]

Whenever we install the latest 7.60 agents, it fails on HP ProLiant Smart Array Device Manager Extension for Windows 2000/Server 2003. The installed version is 5.4.0.32. When we try to install the latest version, which is 5.10.0.32, we get an error message saying

Severity Informational
Task ID VCA1162828417
Date / Time 06/11/2006 15:53:52
Message Smart Component, cp005779.exe, returned result code 3, no action taken.
Additional Data
---------------------------------------------------------------------------
Setup Session Beginning 06/11/2006 - 15:53:49
---------------------------------------------------------------------------

Command Line Parameters Given: /force /silent

Name: HP ProLiant Smart Array Device Manager Extension for
Windows 2000/Server 2003
New Version: 5.10.0.32

Beginning Silent Session...

The software is currently installed, but does not need to be installed on
this system.

Current Version: 5.4.0.32



Installation will not continue.

---------------------------------------------------------------------------
End Session
---------------------------------------------------------------------------


Is there a way to uninstall this from our servers, as its flagging most of them up as being out of date

[Daniel Leblanc]

Did you try to install it manualy on the server with cp005779.exe?

[Melanie Sang]

We have tried to install it manually, and straight from within Version Control and still the same error, on all our servers

[Rob Buxton]

Are you installing the entire 7.60 PSP or are you just trying to install the agents?

If the latter then my guess is that this needs the appropriate array device driver that doesn't have this component included.
What kind of Array controller do you have and what is its version.

[Melanie Sang]

We install the entire PSP 7.60 on our servers, which we have configured. We then see that it's failed on this particular one, so we do a manual install on it, but it still fails. Our servers that have the problem have P400 and P600 controllers in them

[PZel]

Melanie,

Is there already someone who found the solution for this problem ?
(my situation is a W2K server (DL380G5 with P400))

[Daniel Leblanc]

Give every there points i'll give you're Answer Melanie.

I meen you have 36 question and you never gave points that not fun,atleast do this one.

[Melanie Sang]

This problem has not been resolved. We are still having problems, but its only on DL380 G5 servers, all others are ok. If you try and install the new v7.70 on the servers, everthing is updated, except for the Smart Array Device Manager Extension. If you then try to install it manually after, it says its not required.

[john mills_3]

Can you extract the contents of 005779 then
from device manager perform a driver update
on the SAS controllers ??

[Rob Buxton]

You can run the .exe directly and just extract it. In the set of extracted files you should find a readme file. That usually gives you ways of running the install manually and with a "force" option to force the installation.

You might also want to open a call with HP to try and determine if the actual product is required. It may be that a previous PSP update installed the product in error.

You could check if the product is listed in Add/Remove programs as you may be able to just remove it.

[Melanie Sang]

I've tried extracting the files, and then running the setup, but same error, just wont install. There is nothing in Add/Remove Programs to remove it either.

[Derek_56]

Melanie,

Was the system deployed via an image? IE: built on another system? The new controllers don't use the extention driver. Only the 5x and 6x controllers did. We had this exact issue when our engineers decided to image on a system with a 6i in it as well as a P400, then deploy to a P400 system only.

My process was:
1. Rename:
C:\windows\system32\cpqcissm.dll
C:\windows\system32\drivers\cpqcissm.sys
to *.old
2. Restart Version Control Agent.

You may need to remove cpqcissm from the Non-Plug 'n' play device list in device manager. It's been a while since we had this issue. Hope this helps.
-Derek

[dospavlos]

My fix was similar to Derek. I deleted
C:\windows\system32\cpqcissm.dll and restarted the version control agent.