A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Windows Service Pack 2
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

XPSP2 Issue: Dcom was not able to communicate



 
 
Thread Tools Display Modes
  #1  
Old January 16th 05, 08:01 PM
Dale Alex
external usenet poster
 
Posts: n/a
Default XPSP2 Issue: Dcom was not able to communicate

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.

Ads
  #2  
Old January 16th 05, 08:11 PM
Torgeir Bakken \(MVP\)
external usenet poster
 
Posts: n/a
Default XPSP2 Issue: Dcom was not able to communicate

Dale Alex wrote:

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/d...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/pro...on126121120120


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


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx
  #3  
Old January 17th 05, 06:28 AM
Roger Abell
external usenet poster
 
Posts: n/a
Default XPSP2 Issue: Dcom was not able to communicate

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.

--
Roger Abell
Microsoft MVP (Windows Security)
MCSE (W2k3,W2k,Nt4) MCDBA
"Dale Alex" wrote in message
...
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.



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
XPSP2 Issue: Dcom was not able to communicate Dale Alex Windows Service Pack 2 2 January 17th 05 06:28 AM
XPSP2 Issue: DCOM was unable to communicate with the computer Dale Alex General XP issues or comments 0 January 16th 05 06:43 PM
XPsp2 Firewall wrongly detecting domain/standard - DNS Suffix / DHCP RJ Windows Service Pack 2 1 January 12th 05 03:06 PM
Is there any problems upgrading from xpsp1 home or xpsp2 home to xpsp2 pro? Greg R Windows Service Pack 2 12 October 22nd 04 02:15 PM
XPSP2 Near Miss!!! Rick Windows Service Pack 2 2 August 26th 04 04:48 AM






All times are GMT +1. The time now is 02:41 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.