[Microsoft] [odbc SQL Server Driver] solutions for timeout and expiration

Environment : OS: window2000 Server Database: SQL Server 2000 Chinese Enterprise Edition + SP4 Both the customer and service are running on one machine. The customer's management system encountered the "[odbc SQL Server dirvier] timeout expired" error nearly a month after normal operation, and even failed to log on to the database again. Because the system has been running normally for a period of time Code The probability of this error being caused is small, and the ms SQL Server-related system error is more likely. So I tried to cancel, SQL Server Configure properties-> connection timeout limit.

The results have no effect.[Odbd SQL Server dirver]The timeout has expired. However, I found that as long as I re-register ODBC, I can log on again normally, but this problem will still occur frequently afterwards, and the symptoms will not be solved. To solve this problem as soon as possible, there is no way to reinstall the SQL Server Enterprise Edition + SP4, but the problem still persists. :(There is no way to proceedGoogleAndBaiduLooking for previous experiences may be the cause of this problem, but it is complicated. Based on the experience of others, no problem can be solved in our system. At this time, my heart almost collapsed. If the problem persists, only the entire system is reinstalled. This is what I do not want to see. However, the previous article on the Microsoft website, "no way, no way, no way.ArticleAttract my attention. Article ID: 300420 "connnection to SQL Server database using IP address is unusually slow ". The article said that there is a bug in mdac2.6, and it will be slow to connect to the database with an IP address. This reminds me of the IP address I used to avoid DNS resolution when registering ODBC driver. Will this be the problem. So I performed the following operations:

1. ODBC registration by host name
2. Add the IP ing between the IP address and the host name in the hosts file of the system. (This may be an additional step)
3. Upgrade MDAC to version 2.7. Because you do not know how to view the current MDAC version, you can directly download 2.7 from the Microsoft website.

The time has passed. 3 The customer did not report this error. I thought, I probably found a solution for it. So remember to remember. :)