Post reply

Network Packet Size

  • September 27, 2007 at 10:00 am

    #70218

    Hi Guru,

    After we moved from old server (windows 2000, SQL 2000 and SP3a) to a new server (windows 2003, SQL 2000 and SP4) that cutting down maximum network packet size to a half, we run into a new issue below:

    Message : General network error. Check your network documentation.

    Source : .Net SqlClient Data Provider

    Help link :

    Errors : System.Data.SqlClient.SqlErrorCollection

    Class : 20

    LineNumber : 0

    Number : 11

    Procedure : ConnectionWrite (send()).

    The default timeout of our application is 60 seconds and SQL still runs on default netowrk packet size value which is 4096. Switch and NIC settings are exactly the same compared to old machine. I'm not ready to bump up the network packet size value from default configuration. Also, our developer indicated that the time out is not from app server.

    What is the solution of fixing this issue?

    Thanks,

    Silaphet,

  • September 27, 2007 at 11:27 am

    #736873

    1) Check the sql server logs/windows log on a more detailed info.

    2) Is the windows 2003 patched (service pack 2 seems to be current)

    3) Are there any issues on the switches where both servers are connected on (perhaps crc errors...). We went through a serie of routers because they tended to drop large packets >2000 bytes because of loads and lots of subnets.

    4)Is there a pattern when the connectionwrite fails? Perhaps a sqlprofiling could help. Current connections can be viewed with sp_who2.

    5)Is connectionpooling being used? If it isn't used, it could cause server not available. Does the application opens/closes the connection immediately or does it try to keep the connection open (with more chance of connection failure)?

    6)Last resort,perhaps 1 of the cumulative hotfixes for sql server SP4 fixes the issue.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply