Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL 2008 Error: 4014, Severity: 20, State: 11 Expand / Collapse
Author
Message
Posted Wednesday, February 24, 2010 6:46 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, September 30, 2011 3:49 AM
Points: 22, Visits: 3,098
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)
Post #871883
Posted Wednesday, February 24, 2010 9:37 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, April 14, 2014 2:01 PM
Points: 2,007, Visits: 6,065
It looks like a network error. I would check your network connectivity, see if you are dropping packets. Netmon or wireshark 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.




Shamless self promotion - read my blog http://sirsql.net
Post #872014
Posted Wednesday, February 24, 2010 9:46 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, September 30, 2011 3:49 AM
Points: 22, Visits: 3,098
Thank you so much for the reply, I will look into this and let you know how I get on!
Post #872022
Posted Wednesday, February 24, 2010 9:50 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, April 14, 2014 2:01 PM
Points: 2,007, Visits: 6,065
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.



Shamless self promotion - read my blog http://sirsql.net
Post #872027
Posted Friday, July 23, 2010 3:04 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 4:24 PM
Points: 5,847, Visits: 12,580
Fraggle, did you resolve this?

---------------------------------------------------------------------

Post #957829
Posted Friday, July 23, 2010 3:09 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, September 30, 2011 3:49 AM
Points: 22, Visits: 3,098
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!
Post #957831
Posted Friday, July 23, 2010 3:37 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 4:24 PM
Points: 5,847, Visits: 12,580
ok, thanks for replying. We also see these on a new super-spec server at times of load.


---------------------------------------------------------------------

Post #957843
Posted Friday, July 23, 2010 3:41 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, September 30, 2011 3:49 AM
Points: 22, Visits: 3,098
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.
Post #957845
Posted Monday, July 15, 2013 1:06 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 09, 2014 4:47 AM
Points: 2, Visits: 44
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.

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/9fcefe31-e525-46c0-8e62-e6a7e1178feb/error-occurred-while-reading-the-input-stream-from-the-network

Post #1473485
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse