March 19, 2007 at 2:27 pm
Hello,
I keep getting these errors in Event Log.
Source: MSSQLSERVER
A fatal error occurred while reading the input stream from the network. The session will be terminated.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Has anyone seen these events? I couldn't find any information on this error and if you know anything about it would you please share?
Thanks
March 20, 2007 at 8:27 am
I could be wrong but i think i've seen this sort of thing in the past when there was a problem on our internal network. I'd ask the network admin to take a look.
March 20, 2007 at 8:44 am
Do you remember what kind of problems? Any pointers?
Thanks for you reply!
October 5, 2007 at 3:33 pm
i am getting the exact same message, can you please help
January 9, 2008 at 11:46 am
I was just curios if anyone has found a good solution for this. I have been receiving these for the past few weeks and I am starting to see this a lot. The error is so generic I cannot seam to find any answers
January 9, 2008 at 1:12 pm
I might be completly off the base but I read somewhere that it has to do soemthing with the TCP Chimney is enabled on a Wondows 2003 SP 2 with SQL 2005 Enterprise with HP as the network card.
-Roy
January 13, 2009 at 8:13 am
http://support.microsoft.com/?scid=kb%3Ben-us%3B942861&x=7&y=7
please post if resolve.
August 5, 2009 at 5:06 am
Hi Grasshopper
Just wondering if you or anybody else managed to resovle this issue?
August 12, 2009 at 10:28 am
I think mines a little diff... with State: 13
As for the Microsoft Solution for the TCP Chimney... that didn't work... any ideas?
Event Type:Error
Event Source:SQLServer
Event Category:Server
Event ID:4014
Date:Today
Time:Now
User:N/A
Computer:SQLDB2
Description:
A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 64, output error: 0).
DateToday
LogSQL Server
SourceServer
Message
Error: 4014, Severity: 20, State: 13.
August 12, 2009 at 10:42 am
Make sure the machine is not with the virus conficker. it can cause this problem.
August 14, 2009 at 12:33 pm
Systems are all clear... no viruses, spam or spyware any where!
Any other ideas?
Kindly advise:-D
August 10, 2010 at 3:47 pm
What worked for me was to turn on Profiler and use "Error and Warnings" events. Then select all the expanded columns to get as much data as I could. It gave me alot more data to review. Still need to see how to resolve but now I know what .exe and from what server that is doing the calling that generates the error.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply