topic Re: DCOM Windows System Events in Server Management - Systems Insight Manager

DCOM Windows System Events

Clive Churchyard — Wed, 31 Dec 2003 05:54:10 GMT

Every time SIM does a discovery i get a DCOM Event for every IP it tries to discover.
"DCOM was unable to communicate with the computer using any of the configured protocols."
I have setup the discovery exactly the same way as i did in IM7 and don't get any of these errors.
SIM is on Windows 2003.

Any help or ideas would be muchly grateful!

Re: DCOM Windows System Events

David Claypool — Wed, 31 Dec 2003 10:47:15 GMT

These DCOM events are most likely related to WMI. From the docs:

"HP Systems Insight Manager uses HTTPS to access WBEM data, providing a secure path for system management data. For access to Windows management data instrumented in WMI , a WMI Mapper running on a Windows system converts the HTTPS WBEM requests into WMI requests, which use DCOM and NT security."

Make sure the WMI mapper is set up and supply appropriate passwords for WBEM to use to communicate with the systems on the Global Protocols page.

Re: DCOM Windows System Events

John Kramer — Wed, 31 Dec 2003 12:10:21 GMT

David can you explain in more detail the WMI Wapper setup and what type of account needs to be setup in the global settings, is this a Domain administrator account?

Re: DCOM Windows System Events

John Kramer — Wed, 31 Dec 2003 12:24:53 GMT

Okay I tried a Domain admin account in the global WBEM settings and this elimenated the errors for servers but when it discovers RIB or ILO it tries still generates this error in the eventlog is there a way to emliminate this problem?

Re: DCOM Windows System Events

John Kramer — Wed, 31 Dec 2003 12:27:41 GMT

Actually looking through the eventlogs I only get this error on Rib's and ILO's not servers. I am running HPSIM on Windows 2000.

Re: DCOM Windows System Events

David Claypool — Fri, 02 Jan 2004 13:30:50 GMT

This is in fact a Windows problem (Windows indiscriminately attempts to talk to everything it can with DCOM whether it talks DCOM or not...this can show up with iLO/RILOE and Linux systems plus others) although it is being caused by the presence of the WMI Mapper Proxy. This is being looked into.

Re: DCOM Windows System Events

Rob Buxton — Tue, 06 Jan 2004 14:00:39 GMT

Definately a pain.
We have quite a few Solaris, OpenVMS and Linux Systems. And these errors get generated for all of these.

Re: DCOM Windows System Events

David Claypool — Tue, 24 Feb 2004 15:20:11 GMT

[This has also been posted in the thread "DCOM 10009 Errors in HPSIM" at http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=348570 ]

We now have a workaround for this issue. Please note that this is a workaround and does not change the fact that during identification every device will be queried via DCOM to see if it speaks WMI. The request will fail, but it won't be logged. This also means that any valid issue won't be logged either, so proceed at your own risk:

On the machine where the WMIMapper is installed, and serves as the WMIMapper proxy for the HP SIM server, it is very possible that the error message 'DCOM was unable to communicate with computer using any of the configured protocols.' will appear in your NT Event Log during Initial Device Identification and Daily Device Identification. These error messages are not generated by WMIMapper. Rather, they are generated by the Microsoft Windows Management Instrumentation (WMI) service when it is unable to communicate with the target machine to get the WMI information. Most of the time, the target machine is a non-Windows machine.

You can disable logging the WMI errors to the NT Event Log by the following steps:

On the machine where WMIMapper is installed:
1). Stop the 'Pegasus WMI Mapper' service

2). Right mouse click on the 'My Computer' icon from desktop

3). Select 'Manage' from the pop-up menu, the 'Computer Management' page will be displayed

4). Expand the 'Services and Applications' node

5). Select 'WMI Control', and right mouse click on it, the 'WMI Control Properties' page will be displayed

6). Click on the 'Logging' tab on the top

7). Select 'Disabled' from the 'Logging level' section, click on the 'OK' button to close this page

8). From the 'Computer Management' window, double click on 'Services', then select 'Windows Management Instrumentation' service, stop it and then start it again

9). Start the 'Pegasus WMI Mapper' service from the 'Services' page