Server System Error Reporting Event 10016, DistributedCOM, 121, DeviceSetupManager, 513, CAPI2

w w 1 Reputation point
2022-07-01T05:50:07.593+00:00

What can I do if an error message is displayed?Environment Is the company domain account login to view system events.
Server 2019 STD System Event 10016, DistributedCOM.

Application-specific permission settings cannot contain CLSID

{571FCE7E-C4EB-41CF-B9D1-1CBCBFC6D2BD}

with APPID

{82F02F0C-0E3A-472E-BAA5-0BC0AE548818}

The native-enabled permissions for the COM server application are granted to the consumer from the address LocalHost (using LRPC) (executed in the application container cannot be used SID (unusable)) (S-1-5-80-344959196-2060754871-2302487193-2804545603-1466107430). You can use the Component Services System Administration tool to modify this security right.

Server2016 std

  1. Event 121, DeviceSetupManager

Driver installation failed, devnode 'STORAGE\VOLUMESNAPSHOT\HARDDISKVOLUMESNAPSHOT685' result=0x80072EE2

  1. Event 513, CAPI2

Cryptographic Services failed to process an OnIdentity() call in a system writer object.

Details:

AddLegacyDriverFiles: Unable to back up image of binary Microsoft nexus layer explores communication protocols.

System Error:

Access denied.

Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 39,921 Reputation points
    2022-07-03T13:02:00.967+00:00

    Hello

    Thank you for your question and reaching out. I can understand you are having query\issues related to

    DCOM error 10016 is usually harmless and present on most of Window devices. You can safely ignore them.

    These 10016 events are recorded when Microsoft components try to access DCOM components without the required permissions. In this case, this behavior 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.

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

    ------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept as answer--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.