System Management Homepage - Cannot Connect

[Mike Stead]

.....and it's already not responding.

So, it's not a SIM issue, it's an issue with some PSP 8.00 components. Which I think we all knew. So let's see if HP can figure it out.

[Steve Evernham]

Did HP provide you with a method of downgrading all of the componets from 8.00 to 7.80? I've performed a forced downgrade from 8.00 and it did not revert some of the components.

[Mike Stead]

No, they didn't.

I had to manually uninstall the Version Control Agent and the Insight Management Agents then reboot.

Force installed 7.80 then rebooted.

Force installed VCA and IMA again then rebooted again.

Everything seemed to be at 7.80 then.

[Mike Stead]

They are now going to try and simulate the problem in their lab and get back to me on Monday or Tuesday.

[Steve Evernham]

I opened a case with HP and haven't gotten anywhere other than an email with instructions on how to install the SMHP. I explained to them that the problem (for me anyway) seems to occur after the server has been added to a SIM console. Now they are going to send the case to the SIM team.

I'll keep this thread updated with the ongoings of the case.

[FrankW]

Have found this problem as well. No changes with SIM, just installed the Support Pack 8.00.

As an added bonus, now getting lots of application error report popups on the console from wmiprvse.exe, faulting module HPWinHostedEthernetTeam.dll, version 2.1.0.0. To the tune of dozens per day.

I will be trying to revert back to 7.91. Everyone should be advised that 'upgrading' to version 8.00 software is not a good idea!

[Mike Stead]

So far they have had me uninstall the agents twice and reinstall back to 7.91 and let it sit to be sure it works. Today we will manually install 8.00 again to see if it works.

In this last round of uninstalling they had me uninstall both SNMP and WMI SNMP Provider services from Windows completely before reinstalling the PSP.

No real progress yet.

[Terry_92]

Seems like an awfull lot of work for a lot of people for something that should not have been broken in the first place!

[Mike Stead]

Reinstalled 8.00 PSP today per HP. Within two hours the SMH was not responding.

I let them know and I was just informed that they will be escalating the call to a 3rd support level today and to expect a call from a 3rd level engineer in the next 2 business days.

The saga continues.....

[Steve Evernham]

My case is being forwarded to the SIM team ... so I was told. I still haven't gotten anything from them other than the install instructions. I'm going to wait until 1 PM and then call again.

[Mike Stead]

So far I have been with both the ProLiant and the SIM teams. I am not sure where I am going now.

[JD13]

I am having this issue as well on several different servers after upgrading to System Management Homepage v2.1.11.197 (Support Pack 8.00). I have also noticed that the SMH and VCA only stop responding after a system logoff. They respond fine until I log off the system. The SMH service is still running, but does not respond either through SIM or locally via the desktop shortcut unless SMH is restarted. Rebooting is not necessary, only restarting the service. For the systems on which I have tried reverting to the previous version of the SMH, I have had to manually uninstall SMH and VCA and install the versions from Support Pack 7.91.

[Ervinck Kevin]

Indeed manually removing VCA and SMH and installing these from psp7.91 does the trick.

[JD13]

Additional bit of information that I have found for those who may be interested or communicating directly with HP:

If I log onto one of the affected servers with Remote Desktop using the /console switch or log on using the local KVM interface, then log off, SMH becomes unresponsive after logoff and requires a service restart. If I log on to one of the affected systems with Remote Desktop and do NOT use the /console switch, logoff does not render SMH unresponsive. I have tested this repeatedly on all my systems that have been upgraded to SMH v2.1.11.197 and it is consistent on ALL of them.

This may be a work-around for some making it unnecessary to go through the hassle of manually uninstalling SMH with file deletes and registry edits, until HP provides a fixed version.

[NJK-Work]

I agree with JD13's assement. I get the same results. Nice job finding this out!

Someone give this man some points!

Nelson

[Steve Evernham]

I am still working with HP on this issue to find its root cause and a solution, but we did find a workaround that seemed to work at first. But after a little bit of time had past, the same problem came back. The only good thing was that the server now has a link to the hompage in SIM. The change that we tested was setting the security for the SMHP to SNMP instead of WEBM and then having SIM perform an Identify System task on it.

[Kathy Santerre_1]

Has anyone deployed PSP 8.0 to Windows 2008?

[Mike Stead]

Okay. Official word from HP is that it's broken. They have replicated the issue and have moved it up internally and hope to have a fix out soon.

The guy said if you need guaranteed SIM connectivity you should downgrade back to 7.91.

The only workaround is what JD13 came up with, or to connect remotly to the server after you have logged off and restart the SMH service. (ie Computer Management and Manage another computer)

My case is still open, but the guy said he had no idea when there would possibly be a fix.

[AaronK]

Yep, I can reproduce it exactly the same way!
AK

[Steve Evernham]

HP has also informed me that there is a problem within PSP 8.00A (didn't we tell them that?). My case is being escalalted and I will continue to work with them until we have a GOOD resolution or updated PSP.

Hang in there! Just keep deploying 7.91A in the mean time.

[PYMO]

It's been a while.... Any news?

Thanks to all those who have helped troubleshooting this isssue. I had to live with it as I have to time to backtrack all of the servers.
Thanks!

[Steve Evernham]

We are waiting for HP to release an update or a new PSP image. They are recommending to use 7.91A until then. There is no ETA on the new release that I am aware of. If I hear of any updates being tested, I'll post about it.

[mark q]

this is nice, so after I've updated 500+ servers to support paq 8.0 now I have to re-update all of them????

what the heck.. right I don't have anything better to do..

have you had problems with vcrm reporting stuff that wasn't there? every bl25 g1 that I have is reporting the chipset identifiers wrong, and missing rompaq's even though they're instaled.

I've opened cases with hp about all of this stuff and haven't gotten anywhere.

[Steve Evernham]

This whole situation is beyond frustrating. Its very apparent to me that HP did not do any where near sufficient testing on this release and has not lifted a finger to inform anyone that there are problems. Their site still shows the 8.00A PSP as the recommended install, even though its broken. Calling in for support on this was not a walk in the park either. I got passed from one area to another and eventually actually got back to the second person I spoke with. (That took over a week) I'm loosing faith in HP quickly anymore. There support is getting worse and worse, and now their "approved" software gives me the impression that they are relying on the user community to do their testing for them. This type of service and product will cost them. If they aren't careful and correct their internal issues quickly, they'll watch their share of the market go elsewhere.

BTW - I haven't heard ANYTHING from HP for quite a while regarding this case - so still no ETA on a fix.

[Bernard Burette]

What surprises me most here is that the service itself is not stopped, why is it only the Apache web server spawned from "smhstart.exe" and called "hpsmhd.exe" who receives a "stop" order when someone logs off the console? The file named "C:\hp\hpsmh\logs\error_log" clearly states "Parent: Received shutdown signal -- Shutting down the server."

I've had a similar problem with a Java service a little while ago, fortunately sun provides a java.exe command line switch "-Xrs" that help addressing the situation.

Still, I can't see any good reason for Windows to send a shutdown signal to a service as a user logs off the console!