February 24, 2010 at 6:46 am
Hi
I have had a problem with our SQL server which has resulted in the error message below. I have searched Microsoft but they don't have any further information on the error. I wondered if anyone else has come across it. It is causing a problem because it caused our ISA to crash as it was unable to write to the database for more than 30 seconds!
Any ideas much appreciated!
Many thanks!
Fraggle
Log Name: Application
Source: MSSQL$CORPORATE
Date: 24/02/2010 12:20:53
Event ID: 4014
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: W8-SQL3A.XXX
Description:
A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 64, output error: 0)
February 24, 2010 at 9:37 am
It looks like a network error. I would check your network connectivity, see if you are dropping packets. Netmon or wireshark [/url] would both be a help in packet investigation, plus you can use perfmon to look at your network stats.
Also, have a look at http://support.microsoft.com/kb/942861 as regards network issues with certain NIC's and TCP Chimney Offloading.
February 24, 2010 at 9:46 am
Thank you so much for the reply, I will look into this and let you know how I get on!
February 24, 2010 at 9:50 am
Oh, and don't forget to check out both ends of the communication chain. I spent a good while troubleshooting something in the past just to find out it was the front end actually causing the problem.
July 23, 2010 at 3:04 am
Fraggle, did you resolve this?
---------------------------------------------------------------------
July 23, 2010 at 3:09 am
I wish I could offer some good advice to help resolve this however it just seemed to go away on its own! I think it could perhaps have been dropping some packets of data due to heavy network traffic whilst performing database backups across the network to our tape jukebox however, I was never certain!
July 23, 2010 at 3:37 am
ok, thanks for replying. We also see these on a new super-spec server at times of load.
---------------------------------------------------------------------
July 23, 2010 at 3:41 am
Interestingly, our server was also virtually brand new and very high spec also which is why my thoughts turned to the point of packet loss being the cross network traffic.
July 15, 2013 at 1:06 am
Hello All,
I guess the reason for this error is given in the below link. Have a look once.
Its due to TCP Chimney offloading data to Network Adapter.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply