Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, May 28, 2017 7:47 AM | 1 vote
I keep getting this error every time i open Microsoft Outlook 2016 in the event viewer since the last window update Version 1703 (OS Build 15063.332) - I also have a laptop that is doing the same thing and has exactly the same error.
The application-specific 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 JJ-PC\JJ SID (S-1-5-21-262256114-3098324566-3519980562-1001) 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.
I have tried doing the normal things by going into the registry and changing permission of the string 9BA05972-F6A8-11CF-A442-00A0C90A8F39 to the name of ShellWindows and then editing the Tab Security.
In Launch and Activation Permission the Groups are
SYSTEM
Administrators
Users
INTERACTIVE
TrustedInstaller
I have tried adding all sorts of groups but to no avail and noticed the error code says SID (S-1-5-21-262256114-3098324566-3519980562-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable).
What dose the Unavailable mean? Should i be deleting this key?
Thanks
All replies (26)
Thursday, March 1, 2018 9:59 AM ✅Answered
Hi Carl039
I did some digging and I did find the OUTLOOK.EXE.MANIFEST
YOU are a bloody genius, I've been trying to resolve this error for over a year now, your diagnostics was correct, thanks very much, well done you.
Saturday, March 3, 2018 1:46 PM ✅Answered
Thanks for that as you can see from my answer below that thread I managed to do just that and marked this question as answered.
Nice to know that someone else was trying to help, thank you
Saturday, September 29, 2018 8:26 AM ✅Answered | 5 votes
Finally, after 15 months I have resolved this problem.
The application-specific 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 JJ-PC\JJ SID (S-1-5-21-262256114-3098324566-3519980562-1001) 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.
The solution
Bare in mind I’d already given myself permission in the registry so I was already able to edit the necessary properties.
Right click start button, clicked on run and typed dcomcnfg and then press Ok
Expand Component Services, Computers, My Computer and DCOM Config. Scroll down to ShellWindows then right click and click properties.
On the Security tab, click Edit in the Launch and Activation Permissions.
In the Launch and Activation Permission dialog box, click Add.
In the Enter the object names to select box, type ALL APPLICATION PACKAGES and click Check Names , and then click OK.
In the Permissions for ALL APPLICATION PACKAGES list, click to select the Allow check box for the following permissions:
Local Launch Remote Launch Local Activation Remote Activation
click Ok
All done no more errors, this is what worked for me.
Saturday, September 29, 2018 9:23 AM ✅Answered
FIXED
Sill working and no more errors
Monday, May 29, 2017 6:40 AM
Hi,
You need to go to both HKEY_Classes_Root\CLSID\9BA05972-F6A8-11CF-A442-00A0C90A8F39} and HKEY_LocalMachine\Software\Classes\AppID\9BA05972-F6A8-11CF-A442-00A0C90A8F39} and modify the permissions. Change the owner to administrators. After that, go to the DCOM Configuration in Component services and then edit the Tab Security.
After all, please also try restarting the application Service linked to this Application ID or restart the server and monitor.
Regards,
Steve Fan
Please remember to mark the replies as answers if they helped.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, May 31, 2017 3:42 PM
Hi Steve
Not sure I understand you reply?
In my case the keys are exactly the same so when I change permission to HKEY_Classes_Root\CLSID\9BA05972-F6A8-11CF-A442-00A0C90A8F39} to administrators it also changes the permission in HKEY_LocalMachine\Software\Classes\AppID\9BA05972-F6A8-11CF-A442-00A0C90A8F39} so the owner is administrators in both locations.
My problem is not that I can't edit the security tab, as I said before I can edit the ShellWindows Properties and what is already in there is SYSTEM, Administrators, Users, INTERACTIVE and TrustedInstaller.
My question was I don't know what other service to add to try and fix this problem
JJ
Sunday, June 4, 2017 9:28 AM
Can anyone help me with this error above...
Thanks
Sunday, June 25, 2017 1:10 PM
JJ -
Did you ever find a resolution? I am experiencing the same issue.
MTB
Sunday, June 25, 2017 1:51 PM
Hi MTB,
The short answer is no I have not completely resolve this problem. I found I had three issues. Two of them were yellow warnings and one red error. I found that Outlook would not index correctly and the yellow warnings was referring to my Data files.
I am running Microsoft office 365 32-bit version which as you know has Outlook 2016. To try and resolve this problem, what I did was uninstall office keeping all my files in tack and reinstalled the 64-bit version which did resolve my index problem.
Whenever I open outlook now I only get the one red error which is the same one as before
The application-specific 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 JJ-PC\JJ SID (S-1-5-21-262256114-3098324566-3519980562-1001) 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.
I no this is something to do with the last few updates but I'm reluctant to uninstall updates from Microsoft. I know there has been plenty of discussion regarding Outlook emailing but sadly I am I have not found the answer as yet.
Hope this helps,
JJ
Monday, June 26, 2017 6:30 PM
Hi JJ'
I have exactly the same problem.
I found this article about the indexing issue https://www.littledogtech.com/instant-search-failure-in-microsoft-outlook/ and I have uninstalled these KB's :
KB4022715 in Windows 10
KB4022725 in Windows 10
Now I don't have the indexing warning anymore. But I keep getting this error whenever I open Outlook 2016:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{9BA05972-F6A8-11CF-A442-00A0C90A8F50}
and APPID
{9BA05972-F6A8-11CF-A442-00A0C90A8F50}
to the user Domain\User SID (S-xxx) 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.
I found these 2 interesting articles :
https://www.windows10forums.com/articles/event-id-10016-distributedcom.47/
I'm more than sure that I set the right permissions on DCOM Config / ShellWindows (same Application Id than the error AppId) : I added my user Domain\User, Administrators and System in Launch and Activation Permission and set allow to Local Launch, Remote Launch, Local Activation and Remote Activation.
I also set full control to these keys to my user Domain\User, Administrators and System :
HKEY_CLASSES_ROOT\AppID\9BA05972-F6A8-11CF-A442-00A0C90A8F50}
HKEY_CLASSES_ROOT\CLSID\9BA05972-F6A8-11CF-A442-00A0C90A8F50}
So now I'm stuck, if someone has a solution I'm interested.
Windows 10 64bits : 1607/14393.0
Outlook 2016 : 1705/8201.2102
Best.
Tuesday, June 27, 2017 6:04 PM
Thanks for your reply, I will look at your suggestions later over the weekend to see if I can find any more information that will resolve this issue. I'm convinced it's still a Microsoft issue since one of their updates.
Strangely I don't have both of the KB's that you listed only the KB4022725. This is one of the latest updates that has been installed on 16/06/2017 so I'm reluctant to uninstall it at this time.
Hopefully someone else might come up with a interesting solution.
J
Tuesday, June 27, 2017 7:35 PM
Same problem, no solution.
The problem occurs when I move an email from one imap account to another.
The solution is to unsubscribe and subscribe IMAP folder. Moved email disappears.
Tuesday, August 29, 2017 10:13 PM
Hi, I have the same issue and a reinstall of o365's Office works. I tried to start Outlook as Administrator and it changed. Error doesn't log. Wonder if this has something to do with elevated permissions for Outlook to do something.
David Human
Sunday, September 3, 2017 8:09 AM
Hi David,
I found your comments very interesting as you are correct. When starting Outlook as Administrator the error does not occur.
I have tried disconnecting my emails from both folders as (Hadasek) above said, IMAP and Microsoft exchange which made no difference also I have a laptop which has a different email address ending in @outlook.com and that gets the same error so I can confirm it has nothing to do with our email accounts.
I have started to live with this area and hoping that Microsoft through updates would resolve it but to no joy. I am still looking and trying to resolve this problem so if anyone else could help that would be great.
Uninstalled and reinstall it again made no difference running 32-bit or 64 bit so I'm a little stuck stuck.
Microsoft please help with this one!!!
Wednesday, September 6, 2017 10:31 AM
I can also confirm that the error message is logged when starting Outlook normally and does not appear when starting Outlook with Run as Administrator.
I am running Windows 10 version 1703 64bit, Microsoft Office 365 Version 1707 and Outlook 2016 32-bi
Joe Dempsey
Wednesday, September 6, 2017 5:41 PM
It is amazing that we are in 2017 using the latest software and yet we are still having an old error that no one seems to be able to resolve. What is going on Microsoft with Outlook?
The application-specific 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 MY-PC\MY SID (S-1-5-21-262256114-3098324566-3519980562-1001) 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.
Error DistributedCOM 10016
Is there anyone else that could throw some light on this
Thanks
Thursday, November 2, 2017 7:48 PM
Well, we are using microsoft... We should be used to it, right?
working IS and spent most of today trying to deal with this because every time you close outlook and reopen it, go to schedule a new meeting for the first time I get a "Either there is no default mail client or the current mail client cannot fulfill the messaging request" error. subsequent new meetings does not elicit this message, unless I close all instances of outlook and reopen it, then the first one triggers it.
then through multiple attempts at closing reopening and triggering this message, I noticed these COM errors
"
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 ***domainReplaced***\miked SID (S-1-5-21-2589674058-3638939649-1290252312-2444) 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.
"
Assuming the timing of 5 of them w/ the 5 times I triggered the message and no other time that they are related...
idk if this helps but looks like joanne on this post, around pg 23 -26 has this same problem and made some headway with a 3rd reg subkey on the HKEY_LOACL_MACHINE\SOFTWARE\CLASSES\APPID\9BA05972-F6A8-11CF-A442-00A0C90A8F39} which needed to be deleted. I made the mistake of not reading the path carefully and looking in the corresponding APPID path under HKEY_CLASS_ROOT and the employee is using the computer, I'm hoping to come in tomorrow, find an extra entry and viola, however idk. They say a third entry may be added in from the quick boot settings or a 3rd party app. anyway here's the link to see if it helps
Thursday, February 15, 2018 2:15 AM
I am running Windows 10 Pro 64-bit version 1709 (build 16299.248) and Outlook 2016 MSO (16.0.9001.2080) 32-bit.
I can confirm that the DCOM error 10016 is still being logged when opening Outlook 2016.
The windows 10 user account is a Microsoft account with administrator privileges and this user has been added to:
DCOM Config >> Shell Windows >> Properties >> Security Tab >> Launch and Activation Permissions
However, if Outlook 2016 is run as administrator, then DCOM error 10016 is NOT logged.
Wednesday, February 28, 2018 2:09 PM | 3 votes
Try editing the OUTLOOK.EXE.MANIFEST and changing the following line where uiAccess is set to "false" by default:
<requestedExecutionLevel level="asInvoker" uiAccess="true"></requestedExecutionLevel>
On loading Outlook I no longer get the DCOM Event ID 10016 being logged.
Also came across this article which may help explain why setting uiAccess to true fixes the issue.
Wednesday, February 28, 2018 3:11 PM
Your answer sounds promising, but not sure where to edit the Outlook.exe.manifest
I tried copying and pasting the command line above in command prompt (run as administrator) and also in windows PowerShell but with no success.
Could you tell me how to do that please
Thanks
Thursday, March 1, 2018 12:07 PM
Hi Carl039
I did some digging and I did find the OUTLOOK.EXE.MANIFEST
YOU are a bloody genius, I've been trying to resolve this error for over a year now, your diagnostics was correct, thanks very much, well done you.
I modified the OUTLOOK.EXE.MANIFEST and the error has now disappeared but I have a niggle that in the back of my mind that wonders if I haven't short-circuited the protection levels somewhere and left Outlook less protected than I would like?
Joe Dempsey
Saturday, March 3, 2018 12:17 PM | 1 vote
Your answer sounds promising, but not sure where to edit the Outlook.exe.manifest
I tried copying and pasting the command line above in command prompt (run as administrator) and also in windows PowerShell but with no success.
Could you tell me how to do that please
Thanks
There was no command line above. It was a line from a file you need to edit.
The file (at least on my system) is in:
C:\Program Files (x86)\Microsoft Office\root\Office16
You need to run your editor as administrator. For example, type Notepad into the search box at the start button and right-mouse (context-click) on Notepad when it appears and click run as administrator. Then open C:\Program Files (x86)\Microsoft Office\root\Office16\outlook.exe.manifest and change the false to true in the line
<requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
Save the file.
If you get a permission denied, you didn't manage to run notepad as administrator.
It fixed a weird
!!! CreateCTP Error Unable to create specified ActiveX control
I was getting while starting outlook as well as getting rid of the dcom error.
HTH :-)
<style><br _moz_dirty="" /></style>
Saturday, March 17, 2018 2:26 AM
Try editing the OUTLOOK.EXE.MANIFEST and changing the following line where uiAccess is set to "false" by default:
<requestedExecutionLevel level="asInvoker" uiAccess="true"></requestedExecutionLevel>
On loading Outlook I no longer get the DCOM Event ID 10016 being logged.
Also came across this article which may help explain why setting uiAccess to true fixes the issue.
Many thanks for the help.
Your suggested edit of the OUTLOOK.EXE.MANIFEST file does indeed stop the error being logged.
Friday, April 6, 2018 9:59 AM
While resolving the error on my machines the suggested fix has an undesired side effects:
Changing uiAccess="true" causes problems when sending S/MIME signed emails: the confirmation dialog created by Outlook gets displayed in the background and even after bringing it to the foreground sending signed mails does not work or is at least cumbersome.
Thus I changed back to uiAccess="true" because other than the error in the eventlog this seems not to have any bad effects.
Tuesday, September 4, 2018 3:58 AM | 1 vote
What solved it for me;
Part -1
=====
Right Click on Start , click Run , type dcomcnfg , and then click OK .
Expand Component Services , and then expand Computers .
Right-click This PC , and then click Properties .
On the COM Security tab, click Edit Default in the Launch and Activation Permissions area.
In the Launch Permission dialog box, click Add.
In the Enter the object names to select box, type NETWORK SERVICE , click Check Names , and then click OK.
In the Group or user names list, click NETWORK SERVICE .
In the Permissions for NETWORK SERVICE list, click to select the Allow check box for the following permissions:
• Local Launch
• Remote Launch
• Local Activation
• Remote Activation
In addition the ‘Local, In the security policy Service’ need to be configured for the following Policies
- Generate security audits
- Create global objects
- Replace a process level token
- Adjust memory quotas for a process
- Impersonate a client after authentication
- Log on as a service
- Bypass traverse checking
Part -2
=====
Make sure the security settings are set to LOCAL SERVICE and NETWORK SERVICE in the user rights policy.
Local security policy tree is as follows --> Security settings | Local Policies | User rights Assignment |
- Generate security audits
- Create global objects
- Replace a process level token
- Adjust memory quotas for a process
- Impersonate a client after authentication
- Log on as a service
- Bypass traverse checking
yup
Saturday, October 20, 2018 6:47 PM
I agree... Genius is right. This has been driving me crazy as well. I would adjust the guidance and say that only "Local Launch" & "Local Activation" is required. There are other RuntimeBroker issues this one fix seems to also correct.
Thanks for helping to clean up number of related DCOM issues in my eventLog!