December 29, 2016 at 7:50 am
We are seeing the following error on a few of our systems ... I've searched the internet, but cannot find the "exact" error. Any suggestions?
A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: -1, output error: 0).
December 29, 2016 at 9:48 am
mmsheehan (12/29/2016)
We are seeing the following error on a few of our systems ... I've searched the internet, but cannot find the "exact" error. Any suggestions?A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: -1, output error: 0).
Are you seeing this error on the SQL Server log? Looks to me like a memory pressure error but you need to provide more information (read ALL information)
😎
December 29, 2016 at 10:04 am
Seeing it in the Windows Application Log and SQL Server Error log ... one particular server has 256 GB of ram -- SQL Server is using about 210 GB (and total memory used at the time of the error is 227 GB). So, it doesn't "seem" to me memory related i don't think ... The only alert that I really see at this time is deadlocks (i know - bad too) and the Lock Statistics: Wait Time (Latch) isreally high some of the times. Thank you for your time and reply!!!
December 29, 2016 at 12:25 pm
mmsheehan (12/29/2016)
We are seeing the following error on a few of our systems ... I've searched the internet, but cannot find the "exact" error. Any suggestions?A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: -1, output error: 0).
One possibility that I've seen before was when we had NICs that didn't support TCP Chimney features. We had disabled that as well as SynAttackProtect feature. There are a few Microsoft articles about this but some list specific NICs and we had different NICs but still had the issue. Those features are supported better on the current firmware, drivers for the NICs so you may want to check if these are current.
I know there are several blogs and articles about it but this is the only one I could find for now:
https://support.microsoft.com/en-us/kb/942861
There was an MS blog out there with better info on all of this but I can't find it at the moment. The KB article above does cover the gist of it all.
Sue
January 1, 2017 at 9:28 pm
This was removed by the editor as SPAM
January 3, 2017 at 12:47 pm
There is a lot of mixed messages about disabling "Chimney Offload State" and "Receive-Side Scaling State" (RSS) -- The information in the following link suggests not disabling these:
https://blogs.technet.microsoft.com/onthewire/2014/01/21/tcp-offloadingchimney-rsswhat-is-it-and-should-i-disable-it/[/url]
January 3, 2017 at 7:20 pm
mmsheehan (1/3/2017)
There is a lot of mixed messages about disabling "Chimney Offload State" and "Receive-Side Scaling State" (RSS) -- The information in the following link suggests not disabling these:https://blogs.technet.microsoft.com/onthewire/2014/01/21/tcp-offloadingchimney-rsswhat-is-it-and-should-i-disable-it/[/url]
Doesn't seem you really read what I wrote or you missed the point. Here it is again
Those features are supported better on the current firmware, drivers for the NICs so you may want to check if these are current.
Sue
January 4, 2017 at 1:15 pm
Thank you for everyone's reply -- i have compiled your suggestions and requested that our Server Team investigate them :0) Thanks again for your time!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply