From: Moshe Haim (moshehaimHOTMAIL.COM)
Date: Thu Jan 15 2004 - 03:39:53 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

I am running a system that launches Remote COM object on a different
machine.
In one of the methods the Remote object gets an interface pointer to a Local
COM object created on the local machine and calls AddRef. Only when it does
not need it anymore it calls Release, and only after that the local machine
can destroy the object.
(I have stated that since I have seen discussions about the error I'm
getting and Sink interfaces).

We are running the system for long periods of time (more than 10 hrs) and
sometimes we get RPC_E_DISCONNECTED error code.

I have read microsoft documentation and checked that all machines are with
Win2K SP4 installed and the "topmost" DCOM protocol is TCP/IP.

The Remote object creates a few COM objects all local and Free threaded.
One of them uses WaitForSingleObject to synchronize with a secondary thread
- and I did notice that my EXE calls CoInitialize and not CoInitializeEx
(STA instead of MTA).

1. I have no belief that my EXE crashes because many times it seems to be
alive after the error (as far as I recall) - but what can cause the error? I
seem to have all the patches needed (SP4).
2. Does changing the EXE to MTA can solve the problem?

Thanks,
Moshe.

_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.html
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]