In order to fix the issue,there are different ways because it is
generic message and issue can depends on situation to situation .

1.Make sure you have the right entry in your host file for the COM
server name because DCOM is using server name to connect to COM
server.

2.Make sure MSDTC is using same domain ID on both servers(DCOM and COM
server)

3.Under default security tab ,add interactive and domian User(which
you are using for MSDTC).



I hope it will fix your issues.

Thanks
Jatinder Banwait




Message 1 in thread
From: B godlewski (bgodlewski@metlife.com)
Subject: IIS DCOM was unable to communicate with computer


View this article only
Newsgroups: microsoft.public.inetserver.iis
Date: 2001-10-26 08:46:06 PST


We are getting the following message with one of our apps.

we are running nt 4.0 sp6a and iis 4.0


DCOM was unable to communicate with the computer <computer
name> using any of the configured protocols.

this is happening about every 2 weeks and a reboot of the
server is required to get the application running again.

Anyone have a suggestion.
Message 2 in thread
From: Jerry Bryant \(MS\) (jbryantonline@microsoft.com)
Subject: Re: IIS DCOM was unable to communicate with computer


View this article only
Newsgroups: microsoft.public.inetserver.iis
Date: 2001-10-28 05:36:08 PST


What is the Event ID in Event viewer? Do you see one like this as
well?:

Event ID:10006
Source:DCOM
Type: Error
Description: DCOM got error "%2147746132" from the computer  when
attempting
to activate the server:{9B288761-5E2C-11D2-ABDF-08005AD16CA9}



--
For up to date information on IIS:
http://support.microsoft.com/direct...=FH;EN-US;iis50

Regards,

Jerry Bryant
Microsoft IT Communities



This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All
rights
reserved.
"B godlewski" <bgodlewski@metlife.com> wrote in message
 news:00a701c15e34$de448f70$95e62ecf@tkms
ftngxs02...
We are getting the following message with one of our apps.

we are running nt 4.0 sp6a and iis 4.0


DCOM was unable to communicate with the computer <computer
name> using any of the configured protocols.

this is happening about every 2 weeks and a reboot of the
server is required to get the application running again.

Anyone have a suggestion.
Message 3 in thread
From: Bill Godlewswki (bgodlewski@metlife.com)
Subject: Re: IIS DCOM was unable to communicate with computer


View this article only
Newsgroups: microsoft.public.inetserver.iis
Date: 2001-10-29 06:36:00 PST


Yes we get

Event ID:10006
Source:DCOM
Type: Error

that error first then

the 10009
DCOM unable to communicate with computer <computer name> with any of
the configured protocols

*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Message 4 in thread
From: Jerry Bryant [MS] (jbryantonline@microsoft.com)
Subject: Re: IIS DCOM was unable to communicate with computer


View this article only
Newsgroups: microsoft.public.inetserver.iis
Date: 2001-10-29 16:09:46 PST


Bill,

Try this:

1) From the description field in Event ID 10006, look for the GUID of
the
class
responsible for the error and make a note of it or copy it (Ctrl+C) to
the
clipboard.

2) Launch REGEDIT.EXE and search the HKEY_CLASSES_ROOT\CLSID registry
container for the GUID found in step one above.

3) Determine the dll responsible for registering this class object by
double-clicking the GUID, and then clicking once on the InprocServer32
folder
to reveal the dll name. The dll name can be found on the right hand
pane.

4) Using the following command, re-register the class object

REGSVR32.EXE <dll_name.dll>

Hope this helps!
--
For up to date IIS information:
http://support.microsoft.com/direct...=FH;EN-US;iis50

Get Secure!
http://www.microsoft.com/security

Regards,

Jerry Bryant
Microsoft IT Communities



This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All
rights
reserved.
"Bill Godlewswki" <bgodlewski@metlife.com> wrote in message
news:ODT8wbIYBHA.1780@tkmsftngp03...


Yes we get

Event ID:10006
Source:DCOM
Type: Error

that error first then

the 10009
DCOM unable to communicate with computer <computer name> with any of
the
configured protocols

*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Message 5 in thread
From: Bill Godlewswki (bgodlewski@metlife.com)
Subject: Re: IIS DCOM was unable to communicate with computer


View this article only
Newsgroups: microsoft.public.inetserver.iis
Date: 2001-11-01 08:43:51 PST


We Have tried the solution but find that the dll was registered and
the problem did occur again.

We notice that after high usage of the application occurs the 10009
and 10006 messages come up again and a complete reboot of the IIS Web
server is required.



*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

[ Post a follow-up to this message ]