Length specified in network packet payload did not match number of bytes read

Question

Length specified in network packet payload did not match number of bytes read

smoham22

Mr or Mrs. 500

Points: 525
More actions
March 2, 2015 at 2:38 pm

#295677

Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: xxx.xx.xxx.xx]
Client IP address is same as the server its producing the error on. I get these messages around 12pm everyday. Can someone please help me.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

sql-lover SSCoach Points: 18530 More actions · Answer 1

smoham22 (3/2/2015)
Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: xxx.xx.xxx.xx]
Client IP address is same as the server its producing the error on. I get these messages around 12pm everyday. Can someone please help me.

Perform a nslookup on that IP and find the computer that is using that IP. Contact your network admin if you can't or you don't have permissions. Once you identify that machine, find out what is connecting to your SQL box. It may be easier for you if that happens everyday at 12pm.

-- EDIT --

I missed that part where you say that the IP is the same as your SQL box, is that's correct? On that case, check what process or application is running on SQL server at that time.

smoham22 Mr or Mrs. 500 Points: 525 More actions · Answer 2

I checked nothing is running around that time. its around 12pm each day

sql-lover SSCoach Points: 18530 More actions · Answer 3

smoham22 (3/2/2015)
I checked nothing is running around that time. its around 12pm each day

You sure? Can you setup an extended events and capture workload at that time ?

swoozie SSCrazy Points: 2770 More actions · Answer 4

I know this is an older thread, was wondering if you found a resolution. I am experiencing the same thing.

We moved from 2005 to 2014 AG and we have a service broker running and we believe that it is the cause of the error but we can't figure out how to narrow it down. I have been running Trace on the broker and there is nothing.

Sue_H SSC Guru Points: 90860 More actions · Answer 5

swoozie (9/6/2016)
I know this is an older thread, was wondering if you found a resolution. I am experiencing the same thing.
We moved from 2005 to 2014 AG and we have a service broker running and we believe that it is the cause of the error but we can't figure out how to narrow it down. I have been running Trace on the broker and there is nothing.

You should look at the client IP address that accompanies the error and try to track it down that way. Monitoring and probing software are often the cause of the error. IDS or inventory programs.

Sue

swoozie SSCrazy Points: 2770 More actions · Answer 6

the client IP is the IP address of the SQL server it is running on.

Sue_H SSC Guru Points: 90860 More actions · Answer 7

Didn't realize you had duplicated this post and have info in another post.

Refer to: http://www.sqlservercentral.com/Forums/Topic1815590-3411-1.aspx

Sue

Frank.Ferlise SSC Rookie Points: 39 More actions · Answer 8

smoham22 - Monday, March 2, 2015 2:38 PM
Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: xxx.xx.xxx.xx]Client IP address is same as the server its producing the error on. I get these messages around 12pm everyday. Can someone please help me.

Has anyone seen this error with Nessus running discovery scan running.