Microsoft-Windows-DistributedCOM 10016 warning in the event viewer.

Chong 846

Hi Support,

We have many Microsoft-Windows-DistributedCOM 10016 warning in the event viewer. I can found some reference but the CLSID and APPID is different.

https://learn.microsoft.com/en-US/troubleshoot/windows-client/application-management/event-10016-logged-when-accessing-dcom

Any idea to solve this warning

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

{21B896BF-008D-4D01-A27B-26061B960DD7}

and APPID

{03E09F3B-DCE4-44FE-A9CF-82D050827E1C}

to the user DMNSOD\AT13712T SID (S-1-5-21-2675958912-3500480639-3762305494-6141) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Damon Dawson 0 Reputation points

2024-04-24T10:51:41.5266667+00:00

I have the same issue but a different CLSID and APP ID:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID

{21B896BF-008D-4D01-A27B-26061B960DD7}

and APPID

{03E09F3B-DCE4-44FE-A9CF-82D050827E1C}
to the user (my_domain)(my_admin_accont) SID (SID_Number) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Damon Dawson 0 Reputation points

2024-04-24T11:03:25.9766667+00:00

According to: https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/event-10016-logged-when-accessing-dcom?source=recommendations, Microsoft says, "These events can be safely ignored because they don't adversely affect functionality and are by design. It's the recommend action for these events.

If desired, advanced users and IT professionals can suppress these events from view in the Event Viewer."

<steps up on soapbox>
I've seen this same type of response from MS to other issues like when Windows update fails to install a specific update. I do not agree with Microsoft's stance on something like this. At no time should an application throw a warning or error event by design. If so, then it's a really bad design, because it fills up logs with all kinds of useless information, wastes the administrator's time researching bogus issues, and causes other processes (like DCDIAG to report false info) as well as any health check type of application (like SCOM).

Instead, if it's something normal, then Microsoft should either not log it all or list it as an informational message. Exceptions should be coded in and updates provided if exceptions need to be added.

<steps down from soapbox>

@Microsoft - Please correct and stop this practice of expecting your system administrators to remember to ignore or suppress events that shouldn't be there to begin with.