Fix DCOM Event ID 10016 Error On Windows 10
Violetta Wagganer
You install Microsoft Windows SharePoint Services 3.0. When you view the System log after Windows SharePoint Services 3.0 is successfully installed, you see event ID error 10016 or 10017 logged one or more times.
This issue occurs if the domain user account that you specified as the Windows SharePoint Services 3.0 service account does not have the Local Activation permission to the IIS Wamreg Admin Service. The event ID error messages 10016 or 10017 that are mentioned in the "Symptoms" section do not affect the functionality of Windows SharePoint Services 3.0.
You can safely ignore the event ID error messages 10017 or 10016 that are logged in the System log. If you want to prevent the event ID error messages from being logged in the System log, use the Component Services snap-in to enable the Local Activation permission to the IIS Wamreg Admin Service for the domain user account that you specified as the Windows SharePoint Services 3.0 service account. To do this, follow these steps:
This has been a persistent problem for me. Four simultaneous event 10016 will cause my system to lock up, while doing intensive Cad work. I've tracked one of them to Malwarbytes. I've disabled it in hopes there's a fix in the works.
It is a multi-purpose troubleshooting and repair utility, designed to assist with issues related to Malwarebytes for Windows. Our goal with the Malwarebytes Support Tool is to provide a simple and stress-free approach to troubleshooting issues with Malwarebytes products
As I understand things it's a Windows 10 issue. One that that's existed since windows 7. Only now after the last big update, it's causing real issues. MS is just proposing regedit fixes that don't work. This isn't a unique problem. Since uninstalling malwarebytes, I'm only seeing three DCOM errors. I'll let you know if I have another crash.
Finally, searching your system for the CLSID and the AppID may help to reveal the program associated with the freezes (and a test would be to uninstall them temporarily to see if that stops the freezes)
I think things are sorted now. I've reinstalled Malwarebytes and haven't had any issues. I believe something went wrong with my Bios update. I tried unsuccessfully to clear it (cmos button then jumper and battery removal). But it appears that fixed it. I noticed a 6 degree drop in temps afterwards. I still can't explain what went wrong initially.
The DistributedCOM also known as DCOM (Distributed Component Object Model) is a vital aspect for facilitating a set of protocols that allows internetworking between programs on computers with the Windows operating system. Widely accepted as a patent technology developed by Microsoft, it kick-starts when an application is hooked up to the World Wide Web. The Distributed Object Model is capable of accessing the information on RAS (remote access servers) unlike the traditional COM, only capable of accessing information stored in the same machine.
While windows distributedcom event 10016 may not disrupt the functionality of your computer, applying certain fix methods without properly backing up your files may result in loss of valuable data or even crash your PC. If you find yourself battling with recovering lost files as a result of distributedCOM error 10016 windows 10 crash, there is a simple remedy that involves the use of third-party software. The recommended software for such scenarios is the Tenorshare 4DDiG data recovery software. The Tenorshare 4DDiG data recovery software works for all scenarios and below are its amazing features:
Editing the Windows registry should be the first option when it comes to fixing the distributedcom event 10016. By simply removing some windows registry keys these error events could be avoided. However, before tampering with the registry backing up your windows is highly recommended. To do so:
This fix is time-consuming and as such should be an alternative when deleting the above-mentioned registry keys does not suffice. In situations where there are distributedCOM errors from several individual applications, it will require repeating this process for each error, and of course, this will be time-consuming. Below are the steps to take in executing this fix.
Step 3: Locate the Class and Application IDs. To do so you have to highlight and copy the Class ID, launch the regedit, and then search for this directory using the regedit address bar - HKEY_CLASSES_ROOT\CLSID\your Class ID goes here. Once the search is completed, cross-check the Application ID displayed to see if it matches that of the error message.
If the above-listed fixes are way beyond your capacity you can always opt-in for third-party software. There is software out there specifically designed for such problems the likes as error distributedCOM 10016. However, ensure you use the software you trust. Check for reviews and ratings before installing as it will increase your chances of getting a good one.
The DCOM error can be fixed using one of the following fixes; deleting the registry keys, turning on DCOM permissions for certain errors, and utilizing software specifically designed for fixing DCOM errors.
The distributedCOM error 10005 can be resolved through three easy methods which are; setting the server integrations services (SQL) to normal on both nodes, uninstall Microsoft SQL servers with the aid of third-party software, or ignoring the error as it is benign and has no effect on the operating system.
The distributedcom error 10016 fix on windows 11 is quite easy and does not require a user to be tech-savvy to do so. However, some fixes take longer than expected and as such, some users turn to third-party software which is also effective. Unforeseen circumstances such as data loss from implementing some fixes cannot be ruled out. In such scenarios, we recommend the use of the Tenorshare 4DDiG data recovery software to recover lost files.
The recommended way to fix the DistributedCOM error 10016 is to make a few changes to your Registry. The default permissions will be written for the system if you delete the above-mentioned four keys from your registry.
Finally, you will find some other ClSID and AppID values. Repeat the following steps for all of those values that have been listed in the event logs. The changes will take effect after you restart your system at the end.
The scenario is this:Windows 10......hosting an application (or cluster of applications) that takes near-real-time data from real sensors parses the numbers, writes them to a database, and presents them onto a browser .aspx page via IIS and DCOM(this is an archaic mysterious application/set of applications for which there is limited or no source code or documentation).
Occasionally, after working through all the installation and configuration steps, you are presented with a localhost/something.aspx page and whilst you can see the variables by hovering over the fields, the values are not populated.Looking in Windows event viewer, you may see errors like this:
The installed one, is usually the one that reports having no permissions, typically for the "NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20)" user (formed into a group of admin and user accounts)[ -exchange.com/questions/24205909/NT-AUTHORITY-NETWORK-SERVICE-SID-S-1-5-20-on-Windows-Server-2003.html... can't access this page at the moment]; then when you go into the security and add specific permissions for it, you're left with it reporting the above Interactive User keys, the 8d8... one and a 726... one, which you can't edit permissions for.
What bugs me about this is that it's apparently a complete magical mystery, which is unacceptable in a computer system! :DThe current solution is to just no bother fiddling, and just format the machine, redo windows, work through all the application installation, IIS, and DCOM steps, and .aspx config again from scratch, and hope for the best - i.e.: that the magical special order that you do things in just makes it work, "because it does". I think this is a bit ridiculous, and time-consuming, more to the point, it bugs me intensely that there's not really a clear notion of what the actual problem is and what the solution might be.
There must be something specific happening or not happening that is causing the DCOM to not talk to the .aspx webpage; surely something that can be tweaked after the event without zapping the whole systems and spending ages redoing it all. It's as if something is "unplugged" or has a different identity/name/number from what is being looked at or filtered by what the .aspx page ingests, maybe something in the code? something in the IIS selections? something that needs resetting? Not sure...
I'm not asking for a silver bullet, but if anyone is willing to help work through this, that would be appreciated, it's just annoying and frustrating, and I'd like to get to the bottom of it, and hopefully create a definitive thread that others might benefit from.
Before going into these lengthy procedures and editing registry. I would you look at TCP/IPv6 in the Local Area Connection Settings. If it is enabled then disable it and flush the dns or restart your server. Hope it helps the future seekers.
Look for the corresponding service that appears on the error viewer.Note: For this step, look for the one that appeared at the right panel of the RegEdit. For example, the AppID Registry (316CDED5-E4AE-4B15-9113-7055D84DCC97) contains the "Immersive Shell" Data with a (Default) as a name. Now look for "Immersive Shell".
Given that there were 105 instances of this DCOM 10016 error in an eleven second period, I decided to see what was happening at the same time (00:52:09-00:52:19) in the Application event logs. It turned out that there were 210 Information and Warning events during the same time-frame. An example pair of these event is included here:
1035 Information
Windows Installer reconfigured the product. Product Name: Microsoft Excel Mobile Viewer Components. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.