Looks like Pooling is a setting on the ConnectionString in the web.config…
More things to try/ check (in order of how easy/likely they are). In case this doesn’t’ help. Take a look at #2 , #3 and #5 they are the most likely to start happening After a long time of things working correctly..
#1 Different Possible web.config workaround: (easy to try)
<
add name="SybaseDB" connectionString="host='******';Pooling=true;Port='5100';UID='*******';Password='******';Database='****';Min Pool Size=5;Load Balance Timeout=30;Max Pool Size=50;Workstation ID='CIS3G';Fetch Buffer Size=4096;Clone Connection If Needed=True" />
#2 Other application consuming to many resources can cause it:
#3 Router issue
Its from the oracle boards but it’s about the same error using the same brand of drivers.
Router/switch reset and /PAE tags in
might be the cause …
#4 New drivers from DDtek
#5 Badly handled Fk error from Sybase
#6 There is a bug in the driver that can cause this error, turn off pooling to fix it
7# IT group set idle connection timeout on the fire wall to 1 hr, from 8, set it back to 8 , and it fixed it(8/13/2020- EWB)
