Hi Deanna,
On 3/9/2012 2:34 PM, Deanna Earley wrote:
><snip>
> I was commenting in reply to your question about the
> "Rpc_s_server_too_busy fix application". It is most likely trojaned or a
> scam as the page is based on what you search for, and nothing at all to
> do with the error itself.
>
> Does this not give you a more useful clue for debugging:
>
http://support.microsoft.com/kb/176734
>
Wow, this is interesting, I did not know such a problem as described in
this KB article exists with ncacn_np. Ed, do you use named pipes as a
transport? If so, the article suggests what I suggested to you earlier,
IIRC, namely, retry after some time.
I have never received any such complaint for my rpc servers that use
named pipes. However, I do not use the RpcTryExcept schematics as Ed
does, but instead I always use comm_status and fault_status attributes.
I wonder if this has any influence on whether this problem can occur.
Maybe I have always been lucky so far, but now I know that I need to
handle this problem. Thanks for bringing this to my attention.
--
S