Re: Unregistering RPC endpoints
From: Thore Karlsen [MVP DX] (sid_at_6581.com)
Date: 06/08/04
- Next message: Janiv Ratson: "Re: Identifying a router"
- Previous message: Rhett Gong [MSFT]: "Re: Unregistering RPC endpoints"
- In reply to: Rhett Gong [MSFT]: "Re: Unregistering RPC endpoints"
- Next in thread: Rhett Gong [MSFT]: "Re: Unregistering RPC endpoints"
- Reply: Rhett Gong [MSFT]: "Re: Unregistering RPC endpoints"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 07 Jun 2004 22:02:07 -0500
On Tue, 08 Jun 2004 02:29:13 GMT, v-raygon@online.microsoft.com (Rhett
Gong [MSFT]) wrote:
>Yes, this is a known problem -- RpcServerUseProtseqEp() will fail with error
>RPC_S_DUPLICATE_ENDPOINT if we call it rapidly or call it in second process though we
>unregistered it before.
>
>Could you add a sleep for 5 seconds before you call RpcServerUseProtseqEp()? Please let
>me know if it could work in your side. Thanks.
That would be a little inconvenient for our users, so I think I just
prefer it the way it is. It's not a big problem, I just needed to verify
that there was nothing I could do about it. Thanks. :)
-- Be seeing you.
- Next message: Janiv Ratson: "Re: Identifying a router"
- Previous message: Rhett Gong [MSFT]: "Re: Unregistering RPC endpoints"
- In reply to: Rhett Gong [MSFT]: "Re: Unregistering RPC endpoints"
- Next in thread: Rhett Gong [MSFT]: "Re: Unregistering RPC endpoints"
- Reply: Rhett Gong [MSFT]: "Re: Unregistering RPC endpoints"
- Messages sorted by: [ date ] [ thread ]