Question Locked

DCOM fails after 1 hour of inactivity: The remote procedure call failed

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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.

3 replies

by wayne m.

It's been several years since I did DCOM work, but the client and server are supposed to exchange pings to keep connections alive. I do not think you should be seeing this timeout.

Try searching MSDN http://search.msdn.microsoft.com/search/
for "DCOM Timeout". If you have the exact error message, search MSDN for that or do a internet search with your favorite search engine.

Sorry that I can't be more help, it's just been too long! Good luck!

by hmalachi

This issue has been resolved as follows:

Originally thought to be a software problem has been identified as sourced from hardware/firmware.

The hardware/firmware is a firewall (one Cisco Pix 506E) separating the Windows XP/sp2 DCOM clients and the Windows 2003 Server/sp2 DCOM servers.

This firewall comes configured out-of-the-box with a one (1) hour TCP socket time-out feature.

Consultation with Microsoft suggested this time-out be increased to two (2) hours and ten (10) minutes because the Windows XP OS contains a TCP KeepAlive feature which sends polling packets on each open socket once every two (2) hours. Note!!! - This should not be confused with the other keepalive mechanism which occurs once every two (2) minutes between the DCOM client and DCOM server machines.

The firewall's time-out was adjusted as recommended and the problem no longer occurs. ***Thank God!***

Many thanks to the community for any responses or suggestions that lead to this solution.

Howard Malachi
Software Engineer V
Integic/A Northrop Grumman Company.
Email: hmalachi@hotmail.com

This discussion is closed to new replies.