New server with network error

I have a brand new server - Win Server 2008, SQL Standard 2008 and I am getting alerts being fired for Level 20 Alerts. In the log the entry is

Error: 4014, Severity: 20, State: 11.
A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)

This happens randomly, up to 4 or 5 times a day.

Does anyone have any ideas on what might be the cause, and indeed the resolution, please?

I have checked the NIC driver and it's the manufacturers own, not a generic Windows one.

Pings to the server don't drop any packets at all.

Currently the server is under almost no load as I am still benchmarking, configuring ready to go live next month. I am concerned that this problem will get worse if we go live with it.

I have Googled the error and cant see anyone who has actually applied a fix.

We have updated NIC (Broadcom) drivers and are leaving it 24hours. If it still occurs we will swap to a different port (currently using 1 of 2 on NIC). If it still occurs then we are going to add a PCI NIC from a different manufacturer and see if that has any effect.

more ▼

asked Aug 08, 2011 at 04:03 AM in Default

avatar image

Fatherjack ♦♦
43.8k 79 102 118

(comments are locked)
10|1200 characters needed characters left

3 answers: sort voted first

Is it a NIC card or onboard? If a card, maybe try reseating it? (although you'd expect ping drops if that was the case......)

more ▼

answered Aug 08, 2011 at 04:10 AM

avatar image

Kev Riley ♦♦
66.8k 48 65 81

both are onboard.

Aug 08, 2011 at 04:14 AM Fatherjack ♦♦

some of google results suggest it could actually be caused by the client and not the server?

Aug 08, 2011 at 04:38 AM Kev Riley ♦♦

the only client currently is my version of SSMS

Aug 08, 2011 at 07:04 AM Fatherjack ♦♦
(comments are locked)
10|1200 characters needed characters left

are the NICs from Broadcom? We've had issues with the misbehaving in the past. Not this exact error, but they were being strange. We swapped to Intel and everything was fine again.

more ▼

answered Aug 08, 2011 at 04:53 AM

avatar image

26.2k 18 38 48

yes, Broadcom. :(

Swapped drivers or NICs?

Was it done under warranty?

Aug 08, 2011 at 05:41 AM Fatherjack ♦♦

we have them as extra NICs and just went to the onboard intel ones. didn't bother with warranty, the machines are in production and have a total of 6 NICs, two broadcom, rest intel. Intel ones are rock-steady.

I/we suspect it is a problem with the broadcom tcp/ip offloading chip not playing nicely with our switches, or something similar.

Aug 08, 2011 at 05:57 AM WilliamD

We have had similar issues with broadcom, updating the firmware of the NIC cards has proven to be successful.

Aug 08, 2011 at 07:07 AM Tim
(comments are locked)
10|1200 characters needed characters left

We were having this issue at one time at previous employers. It was the client application that was using a slightly out of date version of ADO. I'd suggest checking on that first.

more ▼

answered Aug 08, 2011 at 05:06 AM

avatar image

Grant Fritchey ♦♦
137k 20 47 81

no clients are connecting yet, other than my SSMS ... :(

Aug 08, 2011 at 05:40 AM Fatherjack ♦♦

Then never mind. Hmmm... on a guess, @williamD is right and it's hardware, but that's a total SWAG.

Aug 08, 2011 at 05:43 AM Grant Fritchey ♦♦
(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.



asked: Aug 08, 2011 at 04:03 AM

Seen: 3658 times

Last Updated: Aug 08, 2011 at 07:22 AM

Copyright 2018 Redgate Software. Privacy Policy