Quantcast
Channel: Teradata Forums - All forums
Viewing all articles
Browse latest Browse all 27759

Why would teradata return both "Login timeout expired" and "Not enough information" - response (1) by Kenny54

$
0
0
I am still trying to track down this issue. This is causing issues because I cannot tell what the problem is. All connection strings are built in a common class and  I've setup some trace output showing all the "information to log on" is in the connection string, so I'm thinking it is not a problem with "Not enough information to log on". I suspect that there is a session limit on the number of connections that are active and even though the code is 'opening late and closing early', it is still reaching some limit. But the error is not stating that, so I can't tell. Any thoughts would be helpful.  

Viewing all articles
Browse latest Browse all 27759

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>