Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.
Question
Thursday, May 14, 2009 11:00 AM
The Error is:
2147467259 (80004005)
Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.
We have had IIS and SQL Server 2000 setup on the same server for a few years. I have the ASP setup to send me a notification of any error generated on the site. Occassionally, I would get about 10-15 emails in a row with the error, perhaps every few days. Our web site has steadily grown, and so have the notification of errors. I easily get a few hundred a day now. The database has many millions of records, and there are perhaps millions of transactions per day. CPU averages between 5%-15% utilization, with an occassionaly spike to 60% or so. Memory usage stays around 1.83 GB. It happens on any query, and seems to happen in blocks (like 5-10 at a time, all in the same second).
Any ideas?
Here is the server information.
Windows Server 2003 R2
Standard Edition
Service Pack 2
W2K3 Web Server, Dual Core AMD Operon Processor 270 1.99 GHz, 2.00 GB RAM
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
All replies (3)
Friday, May 15, 2009 7:41 AM âś…Answered
Hi,
first of all be aware that SQL Server 2000 is out of the main stream support. (This might not bother you if you are in the extended support phase) http://support.microsoft.com/lifecycle/?p1=2852
THe mentioned error can be anything concerning the connection either from theclient or from the server. Most likely it is based on the problem that you are using connection pooling and the connection were either not returned to the pool correctly or that you are running out of connections in your pool. For the first case, make sure that you close the connections in your application code. For the second case, increase your connection number in the connection pool. Be ware that you should only increase that by a little number first as the connections in the connection pool might also eat up memory on the client (IIS). You can view the used connections from the server by using the sp_who procedure on the SQL Server 2000 Server.
If you are using an ADO.NET provider, you can change the settings in the connection string: http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring.aspx
-JensJens K. Suessmeyer http://blogs.msdn.com/Jenss
Friday, May 15, 2009 12:34 AM
Do you see any suspecious info on the errorlog?This posting is provided "AS IS" with no warranties, and confers no rights.
Sunday, May 24, 2009 8:02 PM
Was your problem solved or do you have additional questions? if being solved, please mark the post as answered.
-JensJens K. Suessmeyer http://blogs.msdn.com/Jenss