1753851 Members
7386 Online
108807 Solutions
New Discussion

WBEM issues

 
Sven_11
Occasional Contributor

WBEM issues

On a couple of our servers, the discovery process does not discover WBEM as a protocol running on the servers. These are G4 -360 & 380 models. I have verified the systems are running the latest WBEM providers. In fact the system management home pages are working with WBEM as the data source. I cannot find any documentation that can help me with this one.
1 REPLY 1
Sven_11
Occasional Contributor

Re: WBEM issues

update:

I found these error messages in the wbemess.log:

Unable to activate event filter with invalid class name 'HP_AlertIndication' (error 80041002). The filter is not active

Could not activate filter select * from HP_AlertIndication in namespace //./root/CIMV2. HR=0x80041010

Aso, in the windows application event log were a couple of these messages with different provider names:

A provider, HPWMIFCA_InstProv, has been registered in the WMI namespace, root\HPQ, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.