'Re: RPCSS & (80010108)'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-dcom
Subject:    Re: RPCSS & (80010108)
From:       Clay Mayers <clay.mayers () PREVIO ! COM>
Date:       2001-09-29 0:02:56
[Download RAW message or body]


The first example is what we're doing.  In some cases we do pass the
interface proxy to another process (I assume that goes through a stream) but
I'm nearly certain that in the case we're failing, the proxy is straight
from CoCreateInstanceEx(). If it matters, we set proxy blankets on the
interfaces to set up a CoAuthIdentity (we're running as the system account).

Clay.

-----Original Message-----
From: Riyaz Pishori [mailto:riyazp@MICROSOFT.COM]
Sent: Friday, September 28, 2001 4:52 PM
To: DCOM@DISCUSS.MICROSOFT.COM
Subject: Re: RPCSS & (80010108)


Hi Clay,
Here is what I mean,
get pInterfaceProxy
wait 6 or so minutes
use pInterfaceProxy,
Release pInterfaceProxy

OR

get pInterfaceProxy
Marshal it into a stream,
Release pInterfaceProxy
wait 6 or so minutes
Unmarshal from the stream
use pNewInterfaceProxy,
Release pNewInterfaceProxy

Hope this clarifies the question.
Riyaz
-----Original Message-----
From: Clay Mayers [mailto:clay.mayers@PREVIO.COM]
Sent: Friday, September 28, 2001 4:47 PM
To: DCOM@DISCUSS.MICROSOFT.COM
Subject: Re: RPCSS & (80010108)

To get the Hot fix I have to call support.  I used the web "free"
incident
to request the hot fix.

I'm not sure what your question is.  What's failing is a method call on
a
proxy to a remote object.  I'm using that proxy for the full 6 minutes,
then
right at 6 minutes the method call fails.
[RP] Here is what I mean,
get pInterfaceProxy
wait 6 or so minutes
use pInterfaceProxy,
Release pInterfaceProxy

OR
get pInterfaceProxy
Marshal it into a stream,
Release pInterfaceProxy
wait 6 or so minutes
Unmarshal from the stream
use pNewInterfaceProxy,
Release pNewInterfaceProxy


Clay.

-----Original Message-----
From: Riyaz Pishori [mailto:riyazp@MICROSOFT.COM]
Sent: Friday, September 28, 2001 4:41 PM
To: DCOM@DISCUSS.MICROSOFT.COM
Subject: Re: RPCSS & (80010108)


Try the hotfix first, if that does not work, may be MS PSS folks would
need to dig into in your repro.
Other question, is what is the state of the proxy, i.e. an interface
pointer or just a marshaled stream?

Hope this help,
Riyaz

-----Original Message-----
From: Clay Mayers [mailto:clay.mayers@PREVIO.COM]
Sent: Friday, September 28, 2001 4:02 PM
To: DCOM@DISCUSS.MICROSOFT.COM
Subject: Re: RPCSS & (80010108)

Well nearly exactly 6 minutes after the object was created 80010108 is
returned.  I can't find any dead windows on the system.  I wrote a quick
utility to send a broadcast message, it worked fine.  Maybe my
assumption
that I can detect a foul STA by broadcasting is incorrect.

I suppose the next thing to try is to get the hot fix from MS.

Clay.

-----Original Message-----
From: Clay Mayers
Sent: Friday, September 28, 2001 2:00 PM
To: DCOM@DISCUSS.MICROSOFT.COM
Subject: Re: RPCSS & (80010108)


Thanks! This looks promising as it's win2k only but I would think there
would be other symptoms on the machine if a message queue weren't being
serviced since broadcasted messages would block as well.  Perhaps this
mixed
with:

http://support.microsoft.com/support/kb/articles/Q189/4/27.ASP

would make MTA's need to pump messages too.

Clay.

-----Original Message-----
From: Riyaz Pishori [mailto:riyazp@MICROSOFT.COM]
Sent: Friday, September 28, 2001 1:04 PM
To: DCOM@DISCUSS.MICROSOFT.COM
Subject: Re: RPCSS & (80010108)


This KB should help,
http://support.microsoft.com/support/kb/articles/q293/6/31.asp

Hope this helps,
Riyaz

-----Original Message-----
From: Clay Mayers [mailto:clay.mayers@PREVIO.COM]
Sent: Friday, September 28, 2001 10:48 AM
To: DCOM@DISCUSS.MICROSOFT.COM
Subject: Re: RPCSS & (80010108)

Oops got that backwards - 2k clients nt 4.0 server.

Clay.

-----Original Message-----
From: Clay Mayers
Sent: Friday, September 28, 2001 9:39 AM
To: DCOM@DISCUSS.MICROSOFT.COM
Subject: Re: RPCSS & (80010108)


I'm disappointed, as I'm sure you are, that there is no reply to this
one.
We're plagued by this problem as well with NT 4.0 talking to a Win2k
server.

Clay.

-----Original Message-----
From: Alan Kilpatrick [mailto:alan.kilpatrick@ATLANTAGA.NCR.COM]
Sent: Thursday, September 27, 2001 1:37 PM
To: DCOM@DISCUSS.MICROSOFT.COM
Subject: RPCSS & (80010108)


Could someone tell me if/when this was patched in NT 4.0? I'm getting
alot
of the 80010108, RPC_E_DISCONNECTED exceptions from customers that are
running our DCOM application on their NT 4 sp4 machines and I'm trying
to
narrow down the causes.

Thanks,
Alan K.

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

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

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

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

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

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

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

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

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

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

[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic