DCOM was unable to communicate with the computer

Posted on 2008-10-23
Last Modified: 2013-11-25
I am getting an error in Windows Server 2003 "DCOM was unable to communicate with the computer "xyz" using any of the configured protocols. I would like to correct the error but I am not sure how. The computer in question was an old domain controller that crashed and is no longer part of the domain. How can I remove any reference to this old DC?

Thank you,
Question by:conquerdev
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 59

Expert Comment

by:Darius Ghassem
ID: 22786120
Will need to do a metadata cleanup on Active Directory to remove this old DC. Can you post the exact error you are recieving.
LVL 59

Expert Comment

by:Darius Ghassem
ID: 22786135
Also, Make sure to remove all DNS records for this DC.

Expert Comment

ID: 22786148
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.


Author Comment

ID: 22786165
Here is the exact error -

Event Type:      Error
Event Source:      DCOM
Event Category:      None
Event ID:      10009
Date:            10/22/2008
Time:            7:29:19 PM
User:            N/A
Computer:      MMFDC02
DCOM was unable to communicate with the computer using any of the configured protocols.

For more information, see Help and Support Center at

Author Comment

ID: 22786281
I just followed the procedures for the metadata cleanup and the server listed in the error message is not showing up for me to remove during the cleanup process. I have also look at DNS and cannot find any reference to the server. Any other suggestions?

Thank you,
LVL 59

Accepted Solution

Darius Ghassem earned 500 total points
ID: 22786290
Look over this but if the computer name is the old DC then you need to do a metadata cleanup and clean DNS of the records for this DC.

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Active Directory security has been a hot topic of late, and for good reason. With 90% of the world’s organization using this system to manage access to all parts of their IT infrastructure, knowing how to protect against threats and keep vulnerabil…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
The goal of the video will be to teach the user the concept of local variables and scope. An example of a locally defined variable will be given as well as an explanation of what scope is in C++. The local variable and concept of scope will be relat…
In a recent question ( here at Experts Exchange, a member asked how to run an AutoHotkey script (.AHK) directly from Notepad++ (aka NPP). This video…

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question