0
Fixed

DCOM errors thrown when ILM/FIM service unavailable

Matthew Clark 7 years ago • updated by anonymous 3 years ago 6

In the event that Event Broker cannot contact the ILM service for whatever reason (service is off/unresponsive), masses of DCOM errors are thrown to the System log in the Windows Event Viewer:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{61738644-F196-11D0-9953-00C04FD919C1}

to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.

This is likely an artifact of WMI communication failing. If possible, it would be good to remove this issue, and if not, then it should be noted with the documentation. Consequentially, this is worth looking at for v3.0

As a note, I first witnessed this at QDETA in abundance, and the error is thrown even if Local Activiation permission is granted correctly

This error should not be so hidden

The main issue for this in Event Broker 2.x was that connection issues with FIM were not logged anywhere, however, now they are. I think this is the residue of a failed WMI call, but I haven't had much time to research this more properly. The root issue of this concern has been addressed - the rest would be a research project to see if we can prevent the Event Viewer from containing this error on a failed call

As the root issue of not being fed back to the Event Broker UI has been addressed, this issue is being closed