Hi Kir,
Did you get any client messages below?
"[ASE Error SQL30012:08001]Client unable to establish a
connection[ASE Error SQL30012:08001]Client unable to establish a connection"
OR
"... (30012) [08001] [Sybase][ODBC Driver]Client unable to establish a connection"
Did you resolve the SQL error 30012 issue? If so, can you share the resolution?
Hi Tilman,
CR#711008 isn't Windows platform specific. One of the three known Cases affected had ASE running on Solaris - I was working at this customer site at the time. SQL error 30012 is generic for any situation when a client fails to connect to the ASE server. The root-causes could vary from scenario to scenario. My customer's root-cause was not configuring a socket pool for the ASE listener with sufficient sockets and the 3rd party client was firing up new connection requests at very high rate thus exhausting the socket pool. The ASE server wasn't exhibiting high CPU & Engine utilisation symptoms (for least one of the ASE RTC threads), which would be expected if CR#711008 was the culprit.
Kind regards,
Raymond