w_marquardt
asked on
Several repetitive dcom errors in the event log
I have a computer that is throwing dozens of dcom errors. The event iD is 10016. Here's the text from the event viewer (this is winodws 10 pro, 1809
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-5 0F6B8EA6B5 4}
and APPID
{15C20B67-12E7-4BB6-92BB-7 AFF0799740 2}
to the user KBICUSTOMCASE\timothy2 SID (S-1-5-21-4137594547-12426 24928-2318 743208-112 5) 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.
It's the same message time and time again repeated sequentially every minute or so.
I have no idea what the event log info is trying to tell me. Any assistance on this would be greatly appeciated.
Regards,
Bill
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-5
and APPID
{15C20B67-12E7-4BB6-92BB-7
to the user KBICUSTOMCASE\timothy2 SID (S-1-5-21-4137594547-12426
It's the same message time and time again repeated sequentially every minute or so.
I have no idea what the event log info is trying to tell me. Any assistance on this would be greatly appeciated.
Regards,
Bill
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
https://www.tenforums.com/general-support/119105-eventid-10016-a.html
https://www.tenforums.com/performance-maintenance/110023-why-certain-dcom-10016-events-dont-matter.html
"These 10016 events are recorded when Microsoft components tries to access DCOM components without the required permissions. In this case, this is expected and by design. A coding pattern has been implemented where the code first tries to access the DCOM components with one set of parameters. If the first attempt is unsuccessful, it tries again with another set of parameters. The reason why it does not skip the first attempt is because there are scenarios where it can succeed. In those scenarios, that is preferable."
(Cluttering up event logs with preventable errors simply because it's convenient is, IMO, poor coding practice.)
Over the past two weeks we've seen more of this question, so it's not an uncommon thing.