Articles > Misc.
At my company we decided to do some work on our SQL server to make it utilize all of its memory. We turned on the /3GB switch and the /PAE switch in the boot.ini (You don't need the /PAE switch if you have Windows Server 2003 R2). Then we turned on AWE for SQL Server 2005. We also installed Service Pack 2 for Windows Server 2003. After making all of these changes we started getting these errors randomly, but applications were still funtional:
Error message 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General Network error. Check your network documentation
Error message 2
ERROR [08S01] [Microsoft][SQL Native Client]Communication link failure
Error message 3
System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
At first we thought the errors had something to do wtih the AWE settings with SQL Sever, but after a couple weeks of investigating we discovered that the problem was caused by the, "Scalable Networking Pack" features the SP2 automatically turns on when you install it. The Microsoft article below outlines the problem and the solution:
Some problems occur after installing Windows Server 2003 SP2
http://support.microsoft.com/kb/945977
Random SQL Errors Win 2003
Last Updated: 2/14/10At my company we decided to do some work on our SQL server to make it utilize all of its memory. We turned on the /3GB switch and the /PAE switch in the boot.ini (You don't need the /PAE switch if you have Windows Server 2003 R2). Then we turned on AWE for SQL Server 2005. We also installed Service Pack 2 for Windows Server 2003. After making all of these changes we started getting these errors randomly, but applications were still funtional:
Error message 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General Network error. Check your network documentation
Error message 2
ERROR [08S01] [Microsoft][SQL Native Client]Communication link failure
Error message 3
System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
At first we thought the errors had something to do wtih the AWE settings with SQL Sever, but after a couple weeks of investigating we discovered that the problem was caused by the, "Scalable Networking Pack" features the SP2 automatically turns on when you install it. The Microsoft article below outlines the problem and the solution:
Some problems occur after installing Windows Server 2003 SP2
http://support.microsoft.com/kb/945977
I hope this article helps if anyone else runs into these problems. Also if you need to turn AWE on for your SQL Server here is that link as well:
Enabling Memory over 4GB for SQL Server 2005
http://technet.microsoft.com/en-us/library/ms190673.aspx
Keywords: sql server error win2k3sqlerror