Server Management - Systems Insight Manager
1753851
Members
7386
Online
108807
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2009 04:10 AM
09-30-2009 04:10 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2009 04:38 AM
09-30-2009 04:38 AM
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP