Problems with WMI

[Andreas Suether]

Hello,

sometimes i've the problem, that informations collected by WMI Mapper proxy are missing. After performing a System Identification or Start/Stop WMI Mapper Proxy the WMI informations are available again.
Has anyone an idea to resolve this problem so that the WMI works permanent?

Environment:
Windows Server 2003 SP1
SIM 5.0
MS SQL 2000 SP4
HP DL360

[Ben_216]

Hi,
I have the same problem on Win XP sp2

But only when collecting information about non HP kit.

[Andreas Suether]

In my case non HP Systems are not affected.
Only Systems running Windows Server 2003 or 2000 with PSP 7.40.

[Darrin Rawls]

We've been able to reproduce this when a device on the network is not responding 'very well' to WMI requests. Essentially, WMI has to be hung on the device and then not respond to subsequent requests from SIM (mapper problem in SIM that is being worked - no ETA on when a fix is available).

Make sure a support case is logged so that we can get a fix out once available - if that is the case for you. The support team can figure that part out...

-Darrin

[Jim Walsh_2]

Also have you verified that webm is installed and working properly on the target systems? I had one case where the webm folder on the server was empty and I needed to reinstall wmi.

Rebooting a few other servers cleared them up and allowed wmi/webm to work correctly in identifying the servers.

Currently I'm still having issues getting some of my systems consistently identified inside the daily identification.

[Andreas Suether]

Thanks for your replys.
But 10 Systems should have problems to respond to WMI requests at same time?

Some Systems got rebootet at this Weekend but the problem still exists.

What I don't understand, when i perform a Identification and Data Collection manually, all WMI Informations are available. 10 minutes later they are gone and SIM tells me that there is no WBEM/SNMP support on target machine.

I did not had the problems with SIM 4.2 and PSP < 7.40

Any other ideas?

[Jason Cordes_2]

This is about the 3rd or 4th thread on this problem now. I have had a case open on this problem for at least 2 months now, with no hint of a resolution yet.

Darrin, I'm sure my problem is not with any device out there not responding to wmi very well as it happens with all devices I have configured to use wmi in HP SIM. Also, if I restart the Pegasus WMI Mapper service on my HP SIM server the process works for a short time.

-Jason Cordes

[Andreas Suether]

Nice to hear that I'm not alone with this problem. I hope HP will see that there is maybe a problem with SIM or the Mapper Proxy. I hope that they give a resolution for that.

[Andreas Suether]

Okay, i think there will be no resolution.
Thanks for this support, thank you for nothing said better.