This is a discussion on [Microsoft][ODBC SQL Server Driver]Communication link failure within the MS SQL ODBC forums, part of the Microsoft SQL Server category; --> I also have started showing strange ODBC link failures on May 4th of 2005. I'm running asp pages on ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I also have started showing strange ODBC link failures on May 4th of 2005. I'm running asp pages on w2k3 standard server. No known changes have been made to the system prior to this error. The initial connection to any of these web pages works great, but if the refresh or f5 key is pressed, the user is presented with the following error message: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver]Communication link failure /index.asp, line 29 The user must wait about 5-7 seconds before the page can refresh again. It is almost like a timer has been enabled on my web server. Maybe a windows patch turned something on recently? I've also included two snippets from my iis log files: nc050504.log:192.168.115.155 - - [04/May/2005:14:53:49 -0500] "GET /about/s_thomp.asp?|11|80004005|[Microsoft][ODBC_SQL_Server_Driver]Communication_link_failure HTTP/1.1" 500 533 nc050506.log:192.168.115.152 - - [06/May/2005:09:33:38 -0500] "GET /reports/reports.asp?|11|80004005|[Microsoft][ODBC_SQL_Server_Driver]Communication_link_failure HTTP/1.1" 500 535 Regards, -- MB |
| ||||
| Update to my situtation, restarting the server does not fix this problem, but manually restarting the mssqlserver service does fix it. This can be replicated. After looking back at the logs, there was one change, personal monitor software for an new APC UPS unit was installed 30 minutes before this issue began to show up in the web logs. I've uninstalled this software and the problem still exists. -- MB "Matt Bartholomew" wrote: > I also have started showing strange ODBC link failures on May 4th of 2005. > I'm running asp pages on w2k3 standard server. No known changes have been > made to the system prior to this error. > > The initial connection to any of these web pages works great, but if the > refresh or f5 key is pressed, the user is presented with the following error > message: > > Microsoft OLE DB Provider for ODBC Drivers error '80004005' > [Microsoft][ODBC SQL Server Driver]Communication link failure > /index.asp, line 29 > > The user must wait about 5-7 seconds before the page can refresh again. It > is almost like a timer has been enabled on my web server. Maybe a windows > patch turned something on recently? > > I've also included two snippets from my iis log files: > > nc050504.log:192.168.115.155 - - [04/May/2005:14:53:49 -0500] "GET > /about/s_thomp.asp?|11|80004005|[Microsoft][ODBC_SQL_Server_Driver]Communication_link_failure HTTP/1.1" 500 533 > > nc050506.log:192.168.115.152 - - [06/May/2005:09:33:38 -0500] "GET > /reports/reports.asp?|11|80004005|[Microsoft][ODBC_SQL_Server_Driver]Communication_link_failure HTTP/1.1" 500 535 > > > Regards, > -- > MB |