A VB 6.0 DCOM test client, installed on XP/SP2 with latest updates, faults with “The remote procedure call failed” only after 1 hour of inactivity to it’s companion VB 6.0 DCOM server, installed on Windows Server 2003/SP2 with latest updates. All DCOM related functions work fine as long as there is some intermittent operator activity within the 1 hour period – but as soon as the client is left idle for at least one hour and the operator returns to initiate some action requiring the server, the problem results. It is noted this problem does not occur on one of our workstations which does not have a firewall between itself and the DCOM server.
Questions: 1. What is causing the remote procedure call failure. 2. What is possible connection between the failure and the 1 hour time frame? 3. The presence of the firewall is a mystifying because DCOM appears to be working normally for all the application’s functions.. We just have this idle disconnect problem… Also seen as: The object invoked has disconnected from its clients.