We have seen such intermittent problems previously (but generally due to
excessive load). We sleep for a little while and try again before reporting
an error!

I have no idea why you're seeing the problem you are though... but if you
offered a free CE device to reproduce the bug on, I'm sure you'll get many
people who'll try to help ;-)

> -----Original Message-----
> From: Pierre Martin-Dumont [mailto:pmdumontCYBECTEC.COM]
> Sent: 14 March 2002 19:31
> To: DCOMDISCUSS.MICROSOFT.COM
> Subject: Intermittent problem: First function call returns 0x800706BA
>
>
> Hi everyone,
>
> I need help from a DCOM/RPC guru. I can provide a
> demo project,
> network sniffs, or anything else that can help. Here is the problem:
>
> I have an ATL COM server running under Windows CE 3.0, in an embedded
> device. The client application is running under Windows NT4 SP6.
>
> When the embedded device starts up, it registers the server
> application as a
> COM server (/regserver), then launches the server application.
> The server register the two DLLs files (component and proxy)
> of another ATL
> COM object (ILog interface), and falls in an endless message loop.
>
> The client application initially connects to the server,
> geting an interface
> pointer (ISrv) to it. The server interface provide a function
> to obtains an
> interface pointer to another object (ILog).
> The client use the ISrv pointer to gets the ILog pointer, and
> then call the
> unique member function of the ILog interface. This mechanism
> is working
> fine.
>
> Here is the implementation of the server interface function
> that create the
> object and returns his interface pointer:
>
> STDMETHODIMP CSmf::CreateInstance(REFCLSID rclsid, REFIID riid, void
> **ppIface)
> {
> HRESULT hr = E_ACCESSDENIED;
>
> // Try local or remote out-of-proc server before trying inproc.
> hr = CoCreateInstance(rclsid, NULL, CLSCTX_LOCAL_SERVER |
> CLSCTX_REMOTE_SERVER, riid, ppIface);
> if (FAILED(hr))
> {
> hr = CoCreateInstance(rclsid, NULL,
> CLSCTX_INPROC_SERVER, riid,
> ppIface);
> }
>
> return hr;
> }
>
> The problem appears when the embedded device is shutted down (power
> breakdown) and then powered up. The client application
> reconnects to the
> server and gets the ILog interface pointer the same way. The
> first call to
> ILog returns 0x800706BA "The RPC server is unavailable". This
> behavior can
> be reproduced easily, typically after restarting the device
> no more than 3
> times.
>
> The problem disappear if the client application is shutted down and
> restarted about 2 minutes later, or if the device is
> restarted again. The
> problem disappear also if the client application instantiate
> directly the
> ILog interface, but this solution is useless in the context
> of the project,
> for many reasons. From my point of view, it's sounds like the
> RPC binding of
> the ILog interface isn't released, or not flushed from the
> binding cache.
> But it works fine about 75% of the time.
>
> The problems seems not to be related to the device startup time, since
> restarting the device 10 minutes after power failure gives the same
> behavior. DCOM configuration is setup to use TCP/IP.
>
> What can go wrong? Anyone already faced this problem? Please help!
>
> Pierre Martin-Dumont
>
> ----------------------------------------------------------------
> 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-requestDISCUSS.MICROSOFT.COM
>
> ______________________________________________________________
> __________
> This e-mail has been scanned for all viruses by Star Internet. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> ______________________________________________________________
> __________
>

********************************************************
Attachments in this message have been swept
by NAIs TVD (version 4.0.4191) for the presence
of known computer viruses.
********************************************************

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

----------------------------------------------------------------
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-requestDISCUSS.MICROSOFT.COM

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