Hi, Matt -
I can offer no pearls of wisdom, I'm afraid... but here are my thoughts:
1. What PB Transaction object property values and DBParm options are being used?
2. Does this issue occur during the initial app startup/login or at various points within a session?
3. Does this issue occur at approximately the same time of day when it happens? I once worked at a company where there was some kind of network port checking occurring at the same time when their connections to the ASE server would sometimes be disrupted.
4. Is the ASE server configured for failover, load balancing, or does it terminate connections that are considered to be "inactive"?
5. Since the error message you posted shows a failure in the CT-Lib function ct_connect, this makes me think that a connection between the app and the ASE server has failed/broken and the driver is attempting to automatically re-connect. Does this happen only or primarily for remote users?
6. Are you working with Network Infrastructure team to check if there is anything unusual going on that they can see?
7. Are the users reporting this issue connecting local, remotely, or a mixture?
Good luck and best regards, John
I've seen this type of error a few times in my PB / ASE career. One of these customers traced it down to an MS Windows packet errors caused by the latest MS O/S update. After backing out the O/S update, the packet errors stopped. Food for thought. HTH
Regards ... Chris