Many users across our network experience DCOM 10016 errors many times a day. I bolded part of the text below because I'm getting this same CLSID on all the users experiencing the error.

http://support.microsoft.com/kb/899965 - is the clearest documentation I've found on what to do, but it has me physically visiting each computer, and I'm not sure which solution of the two too try first. If so many people are having problems with the same CLSID application, I was thinking there should be a way to change it in one place, to fix everyone.

The Error:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {0C0A3666-30C9-11D0-8F20-00805F2CD064}
to the user VLCT\user SID (##########################). This security permission can be modified using the Component Services administrative tool.

Unfortunately, I have had to deal with the same issue. The only solution that I found after a lot of researching is the same solution you have. DCOM is specific to each machine and there is no way (that I've found) to remotely administer it.

7 Replies

After some research, I found the CLSID {0C0A3666-30C9-11D0-8F20-00805F2CD064} appID in the registry linked to yet another {hexvalue}. When I looked up this one in the registry the appID was Machine Debugger. I found this DCOM object in component services, so I'm guessing this is the one I have to edit permissions too. Is there a way to do this remotely? Please let me know if I'm going down the wrong path though :)

All the machines of the same model are ghosted with the same image yes, we have several different models. The ghosting is done before they are joined to a domain though, before any users are created besides the local admin.

I'm not getting the same SID for each user, I'm getting the same application CLSID for each user. Not that I know what the difference is )

Unfortunately, I have had to deal with the same issue. The only solution that I found after a lot of researching is the same solution you have. DCOM is specific to each machine and there is no way (that I've found) to remotely administer it.

I used to get DCOM errors about every 5 minutes in every XP machine on my network. After some digging, turns out that changing the Network Access Protection service to "Automatic" resolved the problem.