So, here's my situation:
In our production environment, I continue to get this error:
[NCR][TDATA DLL] Login timeout expired
I have a VB 6 component (called from ASP) using ADO (MDAC 2.7) to call the Teradata ODBC Driver (V. 2.06.00.00) on a Windows NT 4.0 Server. The connection string looks like this:
Provider=MSDASQL;Driver=(Teradata};
DBCName=<xxxx1>;DBCName2=<xxxx2>;
DBCName3=<xxxx3>;DBCName4=<xxxx4>;
Database=<xxxx>;
UID=<xxxx>;PWD=<xxxx>;
(I removed sensitive info from connection string!)
My thought is that the login timeout expired is due to some kind of concurrency issue - we can't reproduce it anywhere except production, probably due to the volume of requests.
Any thoughts on what I can do to increase the login timeout for this driver? Is there a setting change on the connection string?
Thanks,
-Aaron
In our production environment, I continue to get this error:
[NCR][TDATA DLL] Login timeout expired
I have a VB 6 component (called from ASP) using ADO (MDAC 2.7) to call the Teradata ODBC Driver (V. 2.06.00.00) on a Windows NT 4.0 Server. The connection string looks like this:
Provider=MSDASQL;Driver=(Teradata};
DBCName=<xxxx1>;DBCName2=<xxxx2>;
DBCName3=<xxxx3>;DBCName4=<xxxx4>;
Database=<xxxx>;
UID=<xxxx>;PWD=<xxxx>;
(I removed sensitive info from connection string!)
My thought is that the login timeout expired is due to some kind of concurrency issue - we can't reproduce it anywhere except production, probably due to the volume of requests.
Any thoughts on what I can do to increase the login timeout for this driver? Is there a setting change on the connection string?
Thanks,
-Aaron