x

SQL 2008 R2 Error 4014

Hi,

We have a two node active-active Windows 2008 R2 cluster with two instances of SQL 2008 R2 installed on it. ServerA and ServerB are the physical nodes, ServerF and ServerG\Inst2 are the default and named instances respectively. From last few days we have been receiving following error quite frequently in our SQL error logs.Please advise.

Error: 4014, Severity: 20, State: 2." A fatal error occurred while reading the input stream from the network.

more ▼

asked Aug 28, 2011 at 10:27 AM in Default

spellbound gravatar image

spellbound
21 3 4 5

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

1 answer: sort voted first

Just googled after the error and found [this connect item][1]

It talks about 4014 errors and says to check if the errors are occurring with the same client or not. If yes, then check for NIC issues on the client, if no, then check the server.

Following query should give information on connectivity issues of this kind :

 
SELECT * FROM sys.dm_os_ring_buffers where ring_buffer_type='RING_BUFFER_CONNECTIVITY'

[1]: http://connect.microsoft.com/SQLServer/feedback/details/518158/-packet-error-a-fatal-error-occurred-while-reading-the-input-stream-from-the-network
more ▼

answered Aug 28, 2011 at 11:43 AM

WilliamD gravatar image

WilliamD
25.9k 17 19 41

I had also gone through the same link but setting up the trace is a challenge in our environment as client is not ready to make any changes on the production server. Is there any other alternative way of troubleshooting this error.
Aug 29, 2011 at 03:59 AM spellbound
Have you tried the query that @WilliamD mentions? This is provided in the connect post after information of the trace.
Aug 29, 2011 at 05:02 AM sp_lock

If the client isn't prepared to let you troubleshoot the problem, how can you help them?

I would make sure that all patches are installed for O/S, SQL Server, NIC Drivers etc.

You don't have to run the trace to begin with, but at least make sure these things are covered. You can tell if the error is happening to one client or multiple clients, this should point you in the right direction.
Aug 29, 2011 at 05:07 AM WilliamD
I had run query mentioned above but the client details are not logged in the record column for error 4014. I had investigated about OS patches and drivers' update and they are up to date. I had also inquired from clients about errors, if any, logged in their application logs. They updated that no issues have been experienced from application end so far. Please advice any other way of troubleshooting.
Aug 29, 2011 at 09:49 AM spellbound
run the trace! Tell client that it is the next logical step, quoting the connect entry with official MS answer. If they don't want to, then you are stuck. I would double-check patch levels and drivers if I were you.
Aug 29, 2011 at 10:21 AM WilliamD
(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.

New code box

There's a new way to format code on the site - the red speech bubble logo will automatically format T-SQL for you. The original code box is still there for XML, etc. More details here.

Follow this question

By Email:

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

By RSS:

Answers

Answers and Comments

SQL Server Central

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

Topics:

x715
x581

asked: Aug 28, 2011 at 10:27 AM

Seen: 4893 times

Last Updated: Aug 30, 2011 at 07:56 AM