Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Tom.Hiscox
Starting Member
12 Posts |
 Posted - 2001-05-17 : 11:30:37
|
| We have a problem with our SQL Server connection. We have applications running on a web Server (NT4, IIS4, SP6a, MDAC 2.6) that are using ODBC to connect to a Named Instance of SQL Server 2000 Enterprise, running on a DB Server (W2K AS, SP1) The only protocol enabled (Server Network Utility) is TCP/IP.When we start up the application it opens and holds a connection to the database, and this works fine, but after a variable period of time (from 2hours up to 2-3 days) the connection is dropped, and when the application is requested to produce a page including some database access we get the following error:Read failure. General SQL error. [Microsoft][ODBC SQL Server Driver]Communication link failureThe application works absolutely fine prior to the error, and upon restarting is also fine again, until the same thing happens again.There is no problem with the Network Connection (the Servers are Compaq DL380's (WEB) and DL580's (DB), the switch is a Cisco 6509, and we have the Web Servers on a different VLAN to the DB Servers, The servers are monitored by Unicenter TNG, and Compaq Server Agents, which report no problem on web or DB.Do you know of anything which could be causing this problem. The SQL Server is a standard installation, with mixed security. The ODBC Connection is using a SQL Server login to the database.Regards,Tom |
|
|
|
|
|
|
|
ODBC Error - Communication Link Failure