Fix for DCOM 10009 Errors in Exchange 2010 SP1

Thursday, July 7, 2011
You may notice DistributedCOM 10009 errors in the Windows Server 2008 R2 System Event Log whenever you run any of the following Exchange 2010 SP1 cmdlets:
  • Get-OWAVirtualDirectory
  • Get-WebServicesVirtualDirectory
  • Get-ActiveSyncVirtualDirectory

The DCOM 10009 error reads as follows:
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          7/1/2011 10:16:11 AM
Event ID:      10009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
DCOM was unable to communicate with the computer using any of the configured protocols.
This happens because of an security context error when invoking an RPC call to the remote CAS server.  The fix is to direct the RPC Runtime to ignore delegation failures.  This can be done by configuring the registry on both the source and target machines, but is more easily done using Group Policy.
To configure Ignore Delegation Failures manually:
  • Run REGEDIT on the source computer
  • Navigate to HKLM\Software\Policies\Microsoft\Windows NT\Rpc
  • Create a new DWORD value called IgnoreDelegationFailure with the value of 1
  • Restart the computer
  • Repeat for each Exchange 2010 SP1 Client Access Server
 To configure this setting using Group Policy:
  • Open the Group Policy Management Console
  • Edit the Group Policy Object (GPO) that applies to the Exchange 2010 SP1 servers.  I usually use the Default Domain Policy.
  • Navigate to Computer Configuration > Policies > Administrative Templates > System > Remote Procedure Call
  • Double-click Ignore Delegation Failure.
  • Enable the policy and set the Ignoring Delegation Failure setting to ON.
  • Restart the Exchange 2010 SP1 Client Access Servers
This DCOM 10009 error does not seem to affect Windows Server 2008 servers, only Windows Server 2008 R2.


  1. I love concise posts like this. thanks much!

  2. Get-WebServicesVirtualDirectory instead of Get-WebServicesDirectory

  3. Thanks for this. I created a new GPO that applied to the "Exchange Servers" group only, and applied that to the OU where my servers live.

  4. Hello, I applied this solution and it works! in fact it also solved another (recurrent) problem on exchange 2010: events 2601, 22604 and 2501


Thank you for your comment! It is my hope that you find the information here useful. Let others know if this post helped you out, or if you have a comment or further information.