TimesTen 7.0.5.0.0 as well as 11.2.1.4.0 on some PC's return a TCP Reset when an ODBC Client DSN attempts to connect. The trace in the tterrors.log file for the 11.2 release is:

10:54:59.64 Err : SRV: 13732: EventID=3| Socket send() failed. Error (10038). File: C:/ADE/pechan_install-pop/timesten/VisiChannel/oc/src/vostcpip.cpp; Line: 742
10:54:59.70 Err : SRV: 13732: EventID=5| Socket recv() failed. Error (10038). File: C:/ADE/pechan_install-pop/timesten/VisiChannel/oc/src/vostcpip.cpp; Line: 639
10:54:59.75 Err : SRV: 13732: EventID=68| Failed to read request from client. Closing connection without reply.

The Client displays a 10054 error code.

The errors with 7.0.5 are identical except for the line numbers:

10:56:35.87 Err : SRV: 10520: EventID=3| Socket send() failed. Error (10038). File: d:/TTBuild/main_0313/VisiChannel/oc/src/vostcpip.cpp; Line: 734
10:56:35.91 Err : SRV: 10520: EventID=5| Socket recv() failed. Error (10038). File: d:/TTBuild/main_0313/VisiChannel/oc/src/vostcpip.cpp; Line: 629
10:56:35.96 Err : SRV: 10520: EventID=68| Failed to read request from client. Closing connection without reply.

This happens when setting up the ODBC Client on Windows: when clicking the "refresh" button on the client screen. Tracing shows the TCP message going to the server and a TCP RST being returned. If anything other than the TT_INTERNAL_DSN message is sent, the server returns a TCP FIN, so it seems comms is ok.

We cannot find anything common on the PC's that do or do not work. Running Windows XP.

Any help would be appreciated.

Thanks

Lou