DistributedCOM DC Server Occasion ID 10016 DCDIAG Error [Fixed]

Learn this information to learn to repair the dcdiag error message, “The machine-default permission settings don’t grant Native Activation permission for the COM Server software with CLSID” Occasion ID 10016 error.

Step 0: Evaluate the Drawback Background and Overview

I just lately promoted a Home windows Server 2019 Server as an extra DC in a site. After selling the server, I accomplished the next duties:

1. Confirmed that the server was added to its AD website
2. Ran “repadmin /kcc” and verified {that a} replication connection was robotically generated.
3. Verified that the server’s subnet is related to its native AD website.

Lastly, to make sure that there have been no replication errors, I ran dcdiag (hyperlink opens in a brand new browser tab) and piped the consequence to a textual content file. Once I reviewed the file, I discovered that the server failed the SystemLog take a look at.

Additional evaluation of the dcsdiag file signifies that an occasion log was logged with the next particulars: “The machine-default permission settings don’t grant Native Activation permission for the COM Server software with CLSID.”

The supply of this occasion within the System occasion log is DistributedCOM, with an Occasion ID of 10016. The error particulars are within the screenshot under.

I’ve defined the steps I took to repair the error message within the remaining sections of this text.

The primary two steps under contain enhancing the Home windows registry. As this may increasingly break your server, it’s strongly really useful to take a snapshot of your server if it’s a VM or again the server up if it’s a bodily server.

Step 1: Change the Possession of the CLSID Registry Keys

1. Get the offending software’s CLSID from the occasion error log. That is the sting of values subsequent to the CLSID within the occasion error log. I’ve highlighted the applying’s CLSID ID within the screenshot under:

2. Seek for and open Regedit. Then, navigate to HKEY_Classes_RootCLSID<the CLSID string from 1 above>.

Since there are such a lot of registry keys within the “HKEY_Classes_RootCLSID” registry path, the easiest way to find the important thing you want is to repeat the important thing from the occasion log, paste it after “” on the and press the enter key.

3. Proper-click the registry key and select permissions.

4. After that, click on the Superior button within the registry key’s permission properties web page, then click on the Change button subsequent to the Proprietor.

5. Then, enter Directors within the Enter the article names to pick field and click on Examine Names > OK.

6. Lastly, examine the Exchange house owners on sub containers and objects checkbox and click on OK.

7. Lastly, grant the Directors group Full Management and click on OK to shut the registry key’s permissions properties window. Don’t shut the registry editor but, as you’ll need to in Step 3 under.

Step 3: Change the Possession of the APPID Registry Keys

1. Get the offending software’s APPID from the occasion error log. See mine within the screenshot under.

2. Again within the registry editor, navigate to KEY_LocalMachineSoftwareClassesAppID registry key, enter the title of the APPID out of your occasion log on the finish of the above path, and press enter.

3. Proper-click the APPID’s registry key and select Permissions. Then, repeat steps 4, 5, 6, and seven of the final part to make the Area Directors group the registry key proprietor—bear in mind to grant the Directors group Full Management.

8. Shut the registry editor.

1. Seek for and open administrative Instruments. Then, find and open the element companies – you possibly can seek for it.

2. Then, increase Part companies > Pc > My Pc and click on DCOM Config.

2. After that, increase DCOM Config, search for the corresponding service within the error viewer, right-click on it, after which select Properties.

In case you obtain the warning message within the screenshot under, choose Sure. The app IDs that start with “{” might be towards the top, so you will need to scroll down the DCOM Config checklist to see the one you’re searching for.

3. On the Properties window, choose the Safety tab, then within the Entry Permission part, choose Customise, then click on the Edit button.

4. After that, click on the Add button.

5. Then, click on the Areas button subsequent to From this location, choose the title of the native server and click on OK.

6. After that, within the Enter the article title to pick discipline, enter the title of the account displayed within the occasion log error (NT SERVICEOCAUM) see the primary screenshot under) – then, click on Examine Names, and OK.

7. Lastly, grant the account Native and Distant entry, then click on OK and OK.

Step 5: Rerun DCDIAG to Affirm that the SystemLog Check Handed

1. Clear the System occasion log by right-clicking it and selecting Clear log. Save a replica of the log within the course of if you happen to require it for additional troubleshooting.

2. After that, rerun dcdiag to substantiate that the SystemLog take a look at handed.

Conclusion

Fixing the “The machine-default permission settings don’t grant Native Activation permission for the COM Server software with CLSID” Occasion ID 10016 error is so simple as granting the account within the occasion log error permission to the COM Server software.

On this “repair it” information, I walked you thru the steps to finish this job utilizing a real-life error I encountered after selling a Home windows Server 2019 server to a DC.

I hope this text met your expectations. Let me know by responding to our “Was this web page useful?” request under.