Hi David;

  I suspect that this issue could be caused caused by either A) Network Timeout; B) VPN timeout and/or C) a DBMS Server timeout setting. Once one of these environment timeouts occurs, IM would then loose the DB connection (even though "KeepAlive=1" is set). All the "KeepAlive=1" setting does is make sure that your ASE "Idle" timeout is not encountered. This feature is for ASE only and does not circumvent the other various environment timeouts that could be in play.

   Once an environment timeout is encountered, your DB Thread is "dead" and the KeepAlive (aka DB Ping) would no longer work when the ASE Connection is dead. I would talk to your Operations, Citrix, Network and/or DBA teams to find out what other environment timeouts have been set in these various areas that might be affecting any App that tries to maintain a consistent DB connection.  HTH

Regards .. Chris