Solved

DCOM was unable to communicate with the computer on SBS 2008

Posted on 2011-02-26
4
1,179 Views
Last Modified: 2013-12-12
On a SBS 2008 at one of my customers I continually get this event log

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 26/02/2011 7:41:55 AM
Event ID: 10009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SBSERVER.kargomax.local
Description:
DCOM was unable to communicate with the computer <IP Address> using any of the
configured protocols.

I see that this started to happen on Feb 15th and now the events are generated
every few seconds with most the IP's addresses in the network

Any ideas what to look for?
0
Comment
Question by:Gerhardpet
  • 2
4 Comments
 
LVL 21

Expert Comment

by:Larry Struckmeyer MVP
ID: 34987508
From the SBS Official Blog: (http://blogs.technet.com/b/sbs/archive/2008/08/26/known-post-installation-event-errors-in-sbs-2008-and-how-to-resolve-them.aspx)

Problem: The DCOM event id 10009 will occur when a client workstation has a miss-configured firewall or other issues affecting its network communications within the domain, for example if the workstation is not managed by an SBS GPO. In this scenario, the DCOM event 10009 will happen repeatedly, potentially hundreds per day.

Were the stations on this SBS added with the //connect wizard, and are they in the correct OU, My Business - Computers - SBS Computers?
0
 
LVL 1

Accepted Solution

by:
Gerhardpet earned 0 total points
ID: 35001028
I found the problem...the event is generated by the monitoring tool I'm using which is normal.
0
 
LVL 1

Author Closing Comment

by:Gerhardpet
ID: 35042669
I found the problem...the event is generated by the monitoring tool I'm using which is normal.
0
 

Expert Comment

by:bluemarbletech
ID: 39713898
I had the same issue with a client's 2011 SBS, the System log showed Event 1009 every 30 minutes for two computers in the domain. It did not seem to affect anything but the log was full of these errors. While dealing with some other issues I found the solution, which was pretty simple. No reg hacks, no port changes.

The two computers showing in the logs had recently been upgraded to Windows 7. They were both wiped clean and then had Win 7 pro reinstalled from scratch, and then rejoined to the domain with new computer names. However, both still showed in AD under the old names as well as the new ones. My guess is they were not dis-joined from the domain before the upgrade. The new computer names showed in AD under SBS Computers, but the old names were still showing under the Computers OU.

In my case the answer was as simple as deleting the old computer names out of AD. The new names stayed put and the errors which were filling up the logs every half hour stopped completely.

Hope this helps in any way.
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

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

Suggested Solutions

If you are a user of the discontinued Microsoft Office Accounting 2008 (MSOA) and have to move to a new computer running Windows 8, you will be unhappy to discover that it won't install.  In particular, Microsoft SQL Server 2005 Express Edition (SSE…
Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

770 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