RPC_S_CALL_FAILED after 30 minutes of inactivity RRS feed

  • Question

  • We have a client/server application that uses DCOM. At one customer installation we have problems that the user experiences as a handful-minute delay when starting to use the client after letting it be idle for half an hour or more. The server is 2003 and the clients run XP. Looking at the logs from our application we see that DCOM calls on these occasions give error RPC_S_CALL_FAILED (0x800706be, The remote procedure call failed).


    After sniffing on Ethernet it is obvious that the server stops responding on the socket that is used for the DCOM communication. The client makes 8-9 retries on TCP and then fails and opens a new DCOM interface. The application requires a number of interfaces and the sum of the time spent retransmitting and reopening for all interfaces (that is sequential) adds up to minutes.


    The first theory was that there was some kind of idle sleep in the client, but we introduced a regular ping once every ten seconds on one of the interfaces and this only helps that interface. Other interfaces still have the same problem after half an hour of inactivity.


    The Ethernet sniffing also shows the following error: “Provider rejection, reason: Proposed transfer syntaxes not supported“ on some occasions. This is given in Bind_ack. Can this be related to the problem?


    Any help you can provide to solve this issue is highly appreciated.

    Wednesday, October 13, 2010 8:27 AM