Hi!

From time to time I see the following error in my System event log:

DCOM was unable to communicate with the computer SERVERNAME using any of the
configured protocols.

What scares me is that SERVERNAME is an old Exchange 2003 server we
uninstalled a long time ago (we are now running Exchange 2007).

How can I see where DCOM gets SERVERNAME from? Why does it try to connect to
a server uninstalled over six months ago?

Regards
Erik

Quote:

From time to time I see the following error in my System event log: DCOM was unable to communicate with the computer SERVERNAME using any of the configured protocols. What scares me is that SERVERNAME is an old Exchange 2003 server we uninstalled a long time ago (we are now running Exchange 2007). How can I see where DCOM gets SERVERNAME from? Why does it try to connect to a server uninstalled over six months ago?

See if some of the info here helps:
http://www.eventid.net/display.asp?eventid=10009&eventno=579&source=DCOM&phase=1

- Thee Chicago Wolf

Thanks alot for your replies!

I am afraid I didn't find a solution at the eventid.net site.

Could it be I have some old attribute still in my AD that points to my old
Exchange Server? Or do you know from where DCOM gets it's list with hosts it
tries to connect to?

// Erik

"Meinolf Weber" wrote:

Quote:

Hello Erik, Start here: http://www.itnewsgroups.net/group/microsoft.public.windows.server.general/topic20871.aspx http://www.eventid.net/display.asp?eventid=10009&eventno=579&source=dcom&phase=1 Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm Hi! From time to time I see the following error in my System event log: DCOM was unable to communicate with the computer SERVERNAME using any of the configured protocols. What scares me is that SERVERNAME is an old Exchange 2003 server we uninstalled a long time ago (we are now running Exchange 2007). How can I see where DCOM gets SERVERNAME from? Why does it try to connect to a server uninstalled over six months ago? Regards Erik

Hello Erik,

Start here:
http://www.itnewsgroups.net/group/microsoft.public.windows.server.general/topic20871.aspx

http://www.eventid.net/display.asp?eventid=10009&eventno=579&source=dcom&phase=1

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Quote:

Hi! From time to time I see the following error in my System event log: DCOM was unable to communicate with the computer SERVERNAME using any of the configured protocols. What scares me is that SERVERNAME is an old Exchange 2003 server we uninstalled a long time ago (we are now running Exchange 2007). How can I see where DCOM gets SERVERNAME from? Why does it try to connect to a server uninstalled over six months ago? Regards Erik

Hello Erik,

Was the old one also domain controller? Did you check all DNS zones for entries
of it, also the reverse lookup zones? Please post also the complete event
viewer entry. On which machine do you have th entries?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Quote:

Thanks alot for your replies! I am afraid I didn't find a solution at the eventid.net site. Could it be I have some old attribute still in my AD that points to my old Exchange Server? Or do you know from where DCOM gets it's list with hosts it tries to connect to? // Erik "Meinolf Weber" wrote: Hello Erik, Start here: http://www.itnewsgroups.net/group/microsoft.public.windows.server.gen eral/topic20871.aspx http://www.eventid.net/display.asp?eventid=10009&eventno=579&source=d com&phase=1 Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm Hi! From time to time I see the following error in my System event log: DCOM was unable to communicate with the computer SERVERNAME using any of the configured protocols. What scares me is that SERVERNAME is an old Exchange 2003 server we uninstalled a long time ago (we are now running Exchange 2007). How can I see where DCOM gets SERVERNAME from? Why does it try to connect to a server uninstalled over six months ago? Regards Erik

Quote:

Thanks alot for your replies! I am afraid I didn't find a solution at the eventid.net site. Could it be I have some old attribute still in my AD that points to my old Exchange Server? Or do you know from where DCOM gets it's list with hosts it tries to connect to?

Are you already using SP2?

- Thee Chicago Wolf

I have checked both our Forward Lookup Zones and Reverse Lookup Zones and I
can't find the host DCOM is trying to connect to.

I get this error on one of my Windows Server 2003 SP2 DCs

The server DCOM is trying to connect to was not a DC but a Member Server
running Exchange 2003.

Below is the entire Event:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10009
Date: 2008-10-15
Time: 23:10:07
User: N/A
Computer: MYSERVER
Description:
DCOM was unable to communicate with the computer OLDSERVER.DOMAIN.TLD using
any of the configured protocols.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

"Thee Chicago Wolf" wrote:

Quote:

Thanks alot for your replies! I am afraid I didn't find a solution at the eventid.net site. Could it be I have some old attribute still in my AD that points to my old Exchange Server? Or do you know from where DCOM gets it's list with hosts it tries to connect to? Are you already using SP2? - Thee Chicago Wolf

The server I am seeing this error is running the following:

Microsoft Windows Server 2003 R2 Standard Edidtion Service Pack2

I do know that DCOM won't be able to connect to the server it give me in the
event log. That server was deleted about 6 months ago.

What confuses me is that DCOM finds the name of that old server at all.

// Erik

"Meinolf Weber" wrote:

Quote:

Hello Erik, As mentioned from Thee Chicago Wolf upgrade to SP2 and all patches at least check this one: http://support.microsoft.com/kb/910695 Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm I have checked both our Forward Lookup Zones and Reverse Lookup Zones and I can't find the host DCOM is trying to connect to. I get this error on one of my Windows Server 2003 SP2 DCs The server DCOM is trying to connect to was not a DC but a Member Server running Exchange 2003. Below is the entire Event: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10009 Date: 2008-10-15 Time: 23:10:07 User: N/A Computer: MYSERVER Description: DCOM was unable to communicate with the computer OLDSERVER.DOMAIN.TLD using any of the configured protocols. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. "Thee Chicago Wolf" wrote: Thanks alot for your replies! I am afraid I didn't find a solution at the eventid.net site. Could it be I have some old attribute still in my AD that points to my old Exchange Server? Or do you know from where DCOM gets it's list with hosts it tries to connect to? Are you already using SP2? - Thee Chicago Wolf

Hello Erik,

As mentioned from Thee Chicago Wolf upgrade to SP2 and all patches at least
check this one:
http://support.microsoft.com/kb/910695

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Quote:

I have checked both our Forward Lookup Zones and Reverse Lookup Zones and I can't find the host DCOM is trying to connect to. I get this error on one of my Windows Server 2003 SP2 DCs The server DCOM is trying to connect to was not a DC but a Member Server running Exchange 2003. Below is the entire Event: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10009 Date: 2008-10-15 Time: 23:10:07 User: N/A Computer: MYSERVER Description: DCOM was unable to communicate with the computer OLDSERVER.DOMAIN.TLD using any of the configured protocols. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. "Thee Chicago Wolf" wrote: Thanks alot for your replies! I am afraid I didn't find a solution at the eventid.net site. Could it be I have some old attribute still in my AD that points to my old Exchange Server? Or do you know from where DCOM gets it's list with hosts it tries to connect to? Are you already using SP2? - Thee Chicago Wolf

Erik

Sorry to jump in here at this time but I have seen this error before in another newsgroup. If my recollection holds then it was an issue with the Exchange server where the OP installed Exchange 2007 from the 2003 version on a W2K8.There was a line in the registry that was not changed\removed with the install. His method of fixing the issue was to remove the 2007 version and then re-install Exchange 2003 then uninstall the latter again and then repeat the install of Exchange 2007. I cannot remember the line in the registry and I tried to find that old thread that was posted about 2 months ago but I cannot find it.
Maybe it applies here also and maybe not. Like I said my two cents for what it is worth


--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Erik Droszcz" <ErikDroszcz@discussions.microsoft.com> wrote in message news:2B5A05EE-83A9-40C4-8B18-50A39A7E4277@microsoft.com...

Quote:

The server I am seeing this error is running the following: Microsoft Windows Server 2003 R2 Standard Edidtion Service Pack2 I do know that DCOM won't be able to connect to the server it give me in the event log. That server was deleted about 6 months ago. What confuses me is that DCOM finds the name of that old server at all. // Erik "Meinolf Weber" wrote: Hello Erik, As mentioned from Thee Chicago Wolf upgrade to SP2 and all patches at least check this one: http://support.microsoft.com/kb/910695 Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm I have checked both our Forward Lookup Zones and Reverse Lookup Zones and I can't find the host DCOM is trying to connect to. I get this error on one of my Windows Server 2003 SP2 DCs The server DCOM is trying to connect to was not a DC but a Member Server running Exchange 2003. Below is the entire Event: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10009 Date: 2008-10-15 Time: 23:10:07 User: N/A Computer: MYSERVER Description: DCOM was unable to communicate with the computer OLDSERVER.DOMAIN.TLD using any of the configured protocols. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. "Thee Chicago Wolf" wrote: Thanks alot for your replies! I am afraid I didn't find a solution at the eventid.net site. Could it be I have some old attribute still in my AD that points to my old Exchange Server? Or do you know from where DCOM gets it's list with hosts it tries to connect to? Are you already using SP2? - Thee Chicago Wolf

I searched for the name in the registry of both the DC where I see this event
and on my Exchange 2007 server. But it wont show up anywhere.

This one is driving me crazy :)

// Erik

"Meinolf Weber" wrote:

Quote:

Hello Erik, Maybe some where in the registry of the server, search fo rthe name and if there is a key with the name post it here first. Mayeb someone knows about if the key is safe to delete. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm The server I am seeing this error is running the following: Microsoft Windows Server 2003 R2 Standard Edidtion Service Pack2 I do know that DCOM won't be able to connect to the server it give me in the event log. That server was deleted about 6 months ago. What confuses me is that DCOM finds the name of that old server at all. // Erik "Meinolf Weber" wrote: Hello Erik, As mentioned from Thee Chicago Wolf upgrade to SP2 and all patches at least check this one: http://support.microsoft.com/kb/910695 Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm I have checked both our Forward Lookup Zones and Reverse Lookup Zones and I can't find the host DCOM is trying to connect to. I get this error on one of my Windows Server 2003 SP2 DCs The server DCOM is trying to connect to was not a DC but a Member Server running Exchange 2003. Below is the entire Event: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10009 Date: 2008-10-15 Time: 23:10:07 User: N/A Computer: MYSERVER Description: DCOM was unable to communicate with the computer OLDSERVER.DOMAIN.TLD using any of the configured protocols. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. "Thee Chicago Wolf" wrote: Thanks alot for your replies! I am afraid I didn't find a solution at the eventid.net site. Could it be I have some old attribute still in my AD that points to my old Exchange Server? Or do you know from where DCOM gets it's list with hosts it tries to connect to? Are you already using SP2? - Thee Chicago Wolf

Did the creator of the other thread uninstall Exchange 2007, reinstalled
Exchange 2003, uninstalled Exchange 2003 and then finally installed Exchange
2007 again?

I am afraid I don't have the option to uninstall out current Exchange 2007
server since we only have one mailserver in total.

// Erik

"Peter Foldes" wrote:

Quote:

Erik Sorry to jump in here at this time but I have seen this error before in another newsgroup. If my recollection holds then it was an issue with the Exchange server where the OP installed Exchange 2007 from the 2003 version on a W2K8.There was a line in the registry that was not changed\removed with the install. His method of fixing the issue was to remove the 2007 version and then re-install Exchange 2003 then uninstall the latter again and then repeat the install of Exchange 2007. I cannot remember the line in the registry and I tried to find that old thread that was posted about 2 months ago but I cannot find it. Maybe it applies here also and maybe not. Like I said my two cents for what it is worth -- Peter Please Reply to Newsgroup for the benefit of others Requests for assistance by email can not and will not be acknowledged. "Erik Droszcz" <ErikDroszcz@discussions.microsoft.com> wrote in message news:2B5A05EE-83A9-40C4-8B18-50A39A7E4277@microsoft.com... The server I am seeing this error is running the following: Microsoft Windows Server 2003 R2 Standard Edidtion Service Pack2 I do know that DCOM won't be able to connect to the server it give me in the event log. That server was deleted about 6 months ago. What confuses me is that DCOM finds the name of that old server at all. // Erik "Meinolf Weber" wrote: Hello Erik, As mentioned from Thee Chicago Wolf upgrade to SP2 and all patches at least check this one: http://support.microsoft.com/kb/910695 Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm I have checked both our Forward Lookup Zones and Reverse Lookup Zones and I can't find the host DCOM is trying to connect to. I get this error on one of my Windows Server 2003 SP2 DCs The server DCOM is trying to connect to was not a DC but a Member Server running Exchange 2003. Below is the entire Event: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10009 Date: 2008-10-15 Time: 23:10:07 User: N/A Computer: MYSERVER Description: DCOM was unable to communicate with the computer OLDSERVER.DOMAIN.TLD using any of the configured protocols. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. "Thee Chicago Wolf" wrote: Thanks alot for your replies! I am afraid I didn't find a solution at the eventid.net site. Could it be I have some old attribute still in my AD that points to my old Exchange Server? Or do you know from where DCOM gets it's list with hosts it tries to connect to? Are you already using SP2? - Thee Chicago Wolf

Hello Erik,

Maybe some where in the registry of the server, search fo rthe name and if
there is a key with the name post it here first. Mayeb someone knows about
if the key is safe to delete.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Quote:

The server I am seeing this error is running the following: Microsoft Windows Server 2003 R2 Standard Edidtion Service Pack2 I do know that DCOM won't be able to connect to the server it give me in the event log. That server was deleted about 6 months ago. What confuses me is that DCOM finds the name of that old server at all. // Erik "Meinolf Weber" wrote: Hello Erik, As mentioned from Thee Chicago Wolf upgrade to SP2 and all patches at least check this one: http://support.microsoft.com/kb/910695 Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm I have checked both our Forward Lookup Zones and Reverse Lookup Zones and I can't find the host DCOM is trying to connect to. I get this error on one of my Windows Server 2003 SP2 DCs The server DCOM is trying to connect to was not a DC but a Member Server running Exchange 2003. Below is the entire Event: Event Type: Error Event Source: DCOM Event Category: None Event ID: 10009 Date: 2008-10-15 Time: 23:10:07 User: N/A Computer: MYSERVER Description: DCOM was unable to communicate with the computer OLDSERVER.DOMAIN.TLD using any of the configured protocols. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. "Thee Chicago Wolf" wrote: Thanks alot for your replies! I am afraid I didn't find a solution at the eventid.net site. Could it be I have some old attribute still in my AD that points to my old Exchange Server? Or do you know from where DCOM gets it's list with hosts it tries to connect to? Are you already using SP2? - Thee Chicago Wolf

Quote:

Did the creator of the other thread uninstall Exchange 2007, reinstalled Exchange 2003, uninstalled Exchange 2003 and then finally installed Exchange 2007 again? I am afraid I don't have the option to uninstall out current Exchange 2007 server since we only have one mailserver in total.

Have you installed some of those post SP rollups that were released
recently. I remember seeing some Roll-up Version 4 or some such thing
recently. Is Exchange 2007 fully patched up as well?

- Thee Chicago Wolf