DCOM errors on Server 2012 RDS server

I am getting several DCOM errors per day on a Server 2012 R2 RDS server. I believe these errors are being generated each time Office 2016 (Office365) is loaded.

This error, I believe, is leading to the server becoming unresponisive. This is the last error before we had to do a hard shutdown on the VM.

The server {0823B6F8-F499-4D5E-B885-EA9CB4F43B24} did not register with DCOM within the required timeout.

These occur regularly:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user DOMAIN\user SID (S-1-5-21-2276840340-2600592784-1026484717-10752) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

AND

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
 and APPID
{8BC3F05E-D86B-11D0-A075-00C04FB68820}
 to the user DOMAIN\user SID (S-1-5-21-2276840340-2600592784-1026484717-10757) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3720635031-3871207760-4221551337-244094189-2265803721-711340575-1868385908). This security permission can be modified using the Component Services administrative tool.

{9BA05972-F6A8-11CF-A442-00A0C90A8F39} points to ShellWindows and {8BC3F05E-D86B-11D0-A075-00C04FB68820} points to WMI.

This article (http://www.itexperience.net/2017/01/13/event-id-10016-fix-the-application-specific-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-with-clsid/)  says to grant permission to the user that is generating the error. I am reluctant to do this because it seems to be every user that logs on to the terminal server.

Should I add the RDS user group? Leave it alone? Please advise.
SBSWIZARDAsked:
Who is Participating?
 
Davis McCarnOwnerCommented:
Your DCOM errors have been rampant and normal for every flavor of Windows since seven.  I too am very leery of granting the permissions to the registry keys necessary to eliminate them and think it is well past high time that Microsoft wrote a few powershell scripts that actually fixed them as I see them on 95+% of the PCs I work on.
0
 
Radhakrishnan RSenior Technical LeadCommented:
Hi,

What's the user SID (S-1-5-21-2276840340-2600592784-1026484717-10752)  belongs to?. I have checked the CLSID {9BA05972-F6A8-11CF-A442-00A0C90A8F39} in registry and this pointing to ShellWindows as you mentioned. But this does have Domain\Users has 'Read' permission.

It's fine to add the permission for the appropriate user into that CLSID as this won't cause any issues.
0
 
Davis McCarnOwnerCommented:
They are both correct answers.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.