Hello… we’re getting an anomalous timeout with Teradata and TDP. We have updated/tested timeouts in the .NET Data Provider config xml and TDP with greater values and zero. There still seems to be a 30 second timeout somewhere we cannot account for that gets triggered when the server gets a little busy. I have spoken with one of the DBAs and they are not aware of a 30 second timeout on their side. Below is an example of the error received.
Run_SQL - [.NET Data Provider for Teradata]  Command did not complete within the time specified (timeout).
[Teradata Database]  The transaction was aborted by the user.
[Socket Transport]  The receive operation timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
TDP 220.127.116.118 64 bit
Any ideas as to where there might be another timeout setting that we are missing? Is there more information I might be able to provide to narrow this down? DBA and I ran a stack trace and while he was able to identify the timeouts there was no pattern. I can’t guarantee I’ll capture them either as they seem to be minutely random.