- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: WBEM Access has stopped working
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО12-11-2005 08:50 AM
тАО12-11-2005 08:50 AM
WBEM Access has stopped working
I've found that the WBEM access for the majority of my Servers is no longer working.
My Historical Data tasks are now failing with an error "An error occurred connecting to this system with the WBEM protocol."
Which is odd as there has been no change to the account that is configured in WBEM.
So, I tried to set a System to use the System Properties, not the Global properties. I run the task, go back to check and the Systerm is still using the Global Properties.
Oddly enough I also get different views of what the System Propoerties are depending if I go in via the Options and then Select the Server or go via the Server Name and into the properties that way.
One says that SNMP is using the Global Properties, the other that it's is using Server Specific.
Anyone seen similar?
HPSIM 5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2005 10:40 AM
тАО12-12-2005 10:40 AM
Re: WBEM Access has stopped working
I've verified it's not the account credentials, I've got some Servers to work successfully with the Global Settings.
I've run a test Historical Data Collection job for three Servers and all worked, another for just two and both failed! Reran after just going in and resaving the WBEM and SNMP Settings from the System Settings box and one worked, one failed.
I have consistently seen a difference between the settings displayed by looking at the System Properties by clicking on the Server name and those displayed if I go into the Options->Protocl Settings->System Protocol settings.
Why that should be I've no idea.
I'm still finding a number of Servers have reverted to using a local setting for the SNMP community names, not the Global Settings. Again, the view can change depending on which way you go in to look at the results.
This may be of use to those folk who believe their SNMP settings are correct but are getting errors that indicate they're not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2005 07:39 AM
тАО12-13-2005 07:39 AM
Re: WBEM Access has stopped working
I have also noticed this issue and my Data Collections are now taking 3 times as long to run.
This seems to have happened after applying the SIM 5 hotfix HOTFIX50_001
(http://h18023.www1.hp.com/support/files/server/us/download/23910.html)
I'm still investigating but yet to find a fix.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2005 08:42 AM
тАО12-13-2005 08:42 AM
Re: WBEM Access has stopped working
Not the issue here as I've not applied the Hotfix yet.
I was thinking there might be something in that that fixed the problem!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-14-2005 10:32 AM
тАО12-14-2005 10:32 AM
Re: WBEM Access has stopped working
I managed to stop the WBEM protocol errors by resetting the Global Protocol Settings.
To do this I removed the WBEM settings option and selected ok and then went back into the Global Protocols and set the WBEM options back to the correct configuration.
I have been running data collections all day and have not had any WBEM errors since this change......however the data collection which used to take 15 minutes is now taking 1 hour 20 minutes. I have increased the DataCollectionThreadCount but this has had no effect.
Back to the drawing board.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-14-2005 10:39 AM
тАО12-14-2005 10:39 AM
Re: WBEM Access has stopped working
Spent most of yesterday on a course so didn't do anything in the way of further changes. last night all but 6 of our Servers completed their Historical collection, the day before that over 60 had failed.
It's this kind of inconsistency that's doing my head in!
How did you incread the DataCollectionThreadCount?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2005 02:07 AM
тАО12-15-2005 02:07 AM
Re: WBEM Access has stopped working
i've had the same thing and the only thing that seemed to help was to set the System Properties SSH part up (for All Systems).. Although i dont use SSH on any of my servers, setting a username with rights to the server on that and forcing it out to all servers did the trick. I guess it changed from WBEM over to SSH then.. I'd be interested to see what you can find.. This has been a sore spot of SIM 5 for me, so if you can get this to be fixed..
-Stefan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2005 02:36 AM
тАО12-15-2005 02:36 AM
Re: WBEM Access has stopped working
To increase the DataCollectionThreadCount edit the file globalsettings.props found in the location "C:\Program Files\HP\Systems Insight Manager\config".
After any changes in this file you must restart the HP Systems Insight Manager Service.
Rick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2005 07:21 AM
тАО12-15-2005 07:21 AM
Re: WBEM Access has stopped working
One thing I did see in the mxdomainmgr.nnnnn.out file was a number of entries where there was a change of status of all my VM Servers during the time the Data Collection task ran. So it seems to be that process that is flagging those back as Unknown.
Also, in some of the larger mxdomainmgr.nnn.out files is the following segment:
11:50:19,501 ERROR [BeanSerializer] Exception:
java.lang.IllegalArgumentException: The char '0x4' in '├в ┬╣^ ├в ┬╣N ├в ┬╣V ^?├Г $PCI' is not a valid XML character.
at org.apache.axis.components.encoding.AbstractXMLEncoder.encode(AbstractXMLEncoder.java:206)
No idea if this is related.