SIM 5 and WBEM problems

[Kevin Kelling]

In the Global Protocol settings, the very first set of WBEM credentials is an account which is a Domain Administrator for our primary domain.

Yet if I try to click on "system properties" or run a Data Collection task, I get a message that it could not connect via WBEM.

The WMI service is running on all targets.

Have tried re-entering the WBEM accounts and rebooting the SIM server which no success.

Any ideas? Where can I look for more debugging info?

Thanks!

[NJK-Work]

Kevin,

Are you using the format of:

domainname\username

or just:

username

Nelson

[Kevin Kelling]

domain/username

You can log into (interactively) any of the servers using this account specified in WWBEM settings and get full admin access

[Kevin Kelling]

Correction...

domain\username

Just verified that slash direction is correct and it is

[David Claypool]

Is the WMI mapper installed and functioning on the SIM server? Does SIM have the correct pointer to it? Do any of the targets have hostnames with underscore characters?

[Kevin Kelling]

Both of the Pegasus WMI services are running and appear healthy.

Not sure how to verify if SIM "has the correct pointer to it".

This server was built new with SIM 4.2 SP2 and upgraded to 5 last week.

None of the targets have underscore chars.

[Kevin Kelling]

OK....I went to "WMI Mapper Proxy" and it has a single entry for the SIM server itself on port 5989. Assuming that this is correct (as we don't have a need for WMI across firewalls yet).

[David Claypool]

Can you verify that the HP SIM server can successfully make WMI calls to the targets? A good way to check this is to use a script such as those that are output by Scriptomatic.

[Kevin Kelling]

Yes....I downloaded WMI CIM Studio from Microsoft onto the SIM server and I can query the WMI on any server all day long.

Also we have HP OpenView here which uses WMI heavily and it works fine..

[sandu_1]

To get the systems identified using wbem, make sure that you have enabled wbem, entered the correct credentials in the globalprotocolsettings page and WMI is running on all the clients.

Run an identification task to get all the systems identified using wbem.

[Kevin Kelling]

Thanks.

The system protocol page of any given system shows only one of the WBEM credentials and is greyed out. The set of credentials is one that I would expect to work.

There is an identify task which runs on every system daily. Plus I usually kick one off manually when doing any troubleshooting.

[Jason Cordes_2]

Does anybody else have this issue? What I am seeing is that sometimes an Identify task will work and pick up some of these systems, and if I run Identify on the same systems it will go back to unknown or unmanaged. Or I will run and Identify task and it'll pick up some of my systems but when I go to it's system page and select properties under more information, it's supposed to come up with a page that queries wmi but instead I get an 'error cannot connect to target system using wbem' and it says to check my global protocol settings.

This does not make any sense as it had already queried the system via wmi and discovered it's system type and os.

-jason

[sandu_1]

Make sure that the WBEM service is running in ur managed node, and run identification task.

[Eric V. Wilson]

Kevin,

Has there been any resolution of this issue?
I have hit exactly the same problem. I have checked the WBEM credentials, checked that the right services are running, re-identified systems, re-discovered systems, etc, etc, - all to no avail!
If you are aware of any solution, please let me know.

Many thanks.

Eric Wilson

[Eric V. Wilson]

Problem solved!
I have installed SP4, re-entered the WBEM credentials, and re-identified the managed systems, and now I can see the managed system properties via WBEM.

[Marco Buehler]

Hi there,

I'm an IT-Apprentice and my english might be a little bit funny, so sorry for any grammatical mistakes. :)

But I have the same problem as all the guys before me. I treid nearly everything and now i'm asking myself: What did "Eric V. Wilson" meant with:

" Problem solved!
I have installed SP4, re-entered the WBEM credentials, and re-identified the managed systems, and now I can see the managed system properties via WBEM."


Is SP4 an SP for Win2003 Server or for the SIM?

Thanks alot for reading(and hopefully understanding) my question.

[Aravindh Rajaram]

It is HPSIM SP4.