Event ID 10016 -- DCOM permissions error

Here only SID from SYSTEM account and no one more.I'll try to think tomorrow,tired

The SID S-1-5-18 doesn't translate to a user with sid2user.exe.

sluice said:

The SID S-1-5-18 doesn't translate to a user with sid2user.exe.

The SID S-1-5-18 belongs to SYSTEM account

Maybe this one help:

Start>>Search>>dcomcnfg

Go to Console root>>Computers>>My computer,right click on it>>Properties>>COM Security in the "Launch and Activation permissions" click on "edit limits" and add SYSTEM account and give this account full access (select all)

This method is equivalent to this one described here Event 10016 may be logged in the System log on a computer that is running Windows XP Professional x64 Edition but you have to note in your message log is SYSTEM account not LocalService or Network service

You can also check these articles.


You may have this problem too due to any soft

i.e Kaspersky can cause this issue too
Cannot access Microsoft NAP Agent: Event ID 10016 | Kaspersky Lab United States

or Windows SharePoint Service
Event ID error messages 10016 and 10017 are logged in the System log after you install Windows SharePoint Services 3.0

I managed to fix the problem by taking ownership of every key and AppID in the registry with those IDs and ensuring that System and administrators had full permission.

Great thread. It fixed the issue on Windows 7 SP1 Ultimate x64 as well.

How would I restore ownership of the registry key back to the TrustedInstaller account?

JohnsonProgram said:

How would I restore ownership of the registry key back to the TrustedInstaller account?

TrustedInstaller - Restore as Owner - Vista Forums

Great topic!!
However, I still had problems setting the right permissions to the registry (I'm not an it expert.)
I found this site that described every step:
error 10016 {344ED43D-D086-4961-86A6-1106F4ACAD9B}

thanks again!

Hi
I have the exact same error.

The strange thing is that CLSID C97FCC79-E628-407D-AE68-A06AD6D8B4D1 does not exist in Registry,
Actually that number does not exist at all in registry,
Could some program installation have gone wrong?

BR
FlemmingK