XPSP2 Issue: Dcom was not able to communicate

G

Guest

I have a client/server database application (MINISIS) that works perfect fine
in the following configuration:

Server: Windows 2000 Server SP4
Clients: Windows 2000 Professional SP4 and Windows XP Professional SP1

However, when I try to run the client from a Windows XP Professional SP2
workstation, I get the following two Message Boxes and a DCOM error in Event
Viewer on the Client:

Message Box 1: Server is not available (Function CoCreateInstanceEx)

Message Box 2: Failed to create MINISIS instance on server <computer name>
(mcl_connect_to_server)

Event Message: DCOM was unable to communicate with the computer <computer
name> using any of the configured protocols. (Event ID: 10009)

Help.

Thank you.
 
T

Torgeir Bakken \(MVP\)

Dale said:
I have a client/server database application (MINISIS) that works perfect fine
in the following configuration:

Server: Windows 2000 Server SP4
Clients: Windows 2000 Professional SP4 and Windows XP Professional SP1

However, when I try to run the client from a Windows XP Professional SP2
workstation, I get the following two Message Boxes and a DCOM error in Event
Viewer on the Client:

Message Box 1: Server is not available (Function CoCreateInstanceEx)

Message Box 2: Failed to create MINISIS instance on server <computer name>
(mcl_connect_to_server)

Event Message: DCOM was unable to communicate with the computer <computer
name> using any of the configured protocols. (Event ID: 10009)
Hi

I suggest you read the DCOM chapter in the document
02_CIF_Network_Protection.DOC downloadable from
http://www.microsoft.com/downloads/...d7-b791-40b6-8364-685b84158c78&DisplayLang=en

Note: WinXPSP2_Documentation.zip contains all the .doc downloads...

This one might be the same as in the document
02_CIF_Network_Protection.DOC:
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx#XSLTsection126121120120


The "Anonymous DCOM and SP2" blog entry at
http://blogs.tonygoodhew.com/xpsp2 might apply as well...
 
R

Roger Abell

Additionally, if this is the commercial Minisis software the contact
the vendor for update information, as a number of companies needed
to adjust during the long timeframe while MS was warning of the
changed behaviors for DCOM that would occur with SP2, and most
that did not have since had to more urgently.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top