1. Matt Balent
  2. PowerBuilder
  3. Monday, 21 October 2024 20:00 PM UTC

Environment: PB2022 R3, 64bit PB app running on Win 2019 Server connecting to SYBASE ASE 16 database with a native driver.  Users get very periodic  errors (can't reproduce with any regularity) which say Sybase Error 6 (doesn't appear to be the real SYBASE error since theirs start at 2000).

Posting this on the off chance someone else stumbled into the same situation...

Thanks

Matt

John Fauss Accepted Answer Pending Moderation
  1. Monday, 21 October 2024 21:00 PM UTC
  2. PowerBuilder
  3. # 1

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

Comment
There are no comments made yet.
Matt Balent Accepted Answer Pending Moderation
  1. Monday, 21 October 2024 20:15 PM UTC
  2. PowerBuilder
  3. # 2

Now they share this with me:

 atr_corp is the transaction object name.

Comment
  1. Chris Pollach @Appeon
  2. Monday, 21 October 2024 20:42 PM UTC
Hi Matt;

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
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.