This is a discussion on Strange but interesting ODBC error within the MS SQL ODBC forums, part of the Microsoft SQL Server category; --> In setting up System DSN using TCP/IP at port 1433 (SQL authentication) I get this error: SQLState: "HYT00" SQLServerError: ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| In setting up System DSN using TCP/IP at port 1433 (SQL authentication) I get this error: SQLState: "HYT00" SQLServerError: 0 [Microsoft][ODBC SQL Server Driver] Timeout Expired. However, when I click next again, I can connect. Strange thing is what causes this behaviour to happen: not ok on first try but ok on 2nd try. The interesting thing is that it's consistent: always, as in always, not ok on 1st but ok on second. Has anyone encountered this phenomenon? What's causing this? How can this be resolved? Thanks |
| |||
| There may be a intermittant networking problem between your server and client. Check for bandwidth utilitization and error rate. Also, are you current with the latest SQL SP and MDAC on both ends? There may be fixes for initialization and robustness. How long does it take for the timeout to happen? |
| ||||
| Thanks for response. Both client and server have latest SP and MDAC. timeout is around10-15 seconds "Kurt Tiedtke" <anonymous@discussions.microsoft.com> wrote in message news:3E717B92-1BCD-4B8C-90A4-5FFC5C7D1A15@microsoft.com... > There may be a intermittant networking problem between your server and client. Check for bandwidth utilitization and error rate. Also, are you current with the latest SQL SP and MDAC on both ends? There may be fixes for initialization and robustness. > How long does it take for the timeout to happen? > |