Ms sql server ошибка 17836

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.
Error: 17836, Severity: 20, State: 14. I am getting this error 5 times at the same time almost and want to know the reason for its occurrence.

asked Apr 15, 2016 at 7:21

See the solution here:

Since the SQL Server has Event ID 17836 logged, the SQL port is open.
It is more like authentication issue. Based on this articles
(Configuration for querying SQL database remotely –
http://www.howtonetworking.com/others/testsqlconnect2.htm ), we may
have 3 fixes:

creating SQL login ID (recommended)

join the computer to the domain

allow anonymous connections to SQL Server 2000 or to SQL Server 2005 (don’t recommend)

And this MSDN forum

Perform a nslookup of the CLIENT IP Address that is listed in the
error message and find out what computer it is that is connecting.
Then you need to check that machine and determine what specifically is
connecting to the SQL Server. You might get more infromation from
doing a SQL Trace for the Errors and Warnings Event Class and have the
ClientProcessID column in the trace data. When the error spikes, you
might get the PID for the process that is connecting from that
10.26.32.96 machine, and then you can find that process in Task Manager on that machine by adding the PID to the data displayed (View
-> Select Columns).

answered Apr 15, 2016 at 7:24

Rahul TripathiRahul Tripathi

165k31 gold badges271 silver badges327 bronze badges

In my case, these events coincided with me doing telnet connectivity tests to our SQL Servers. We would see one entry in the Windows Event Log for each instance we successfully did a telnet to.

answered Apr 25, 2018 at 4:03

MikeMike

1,59818 silver badges14 bronze badges

Источник

Remove From My Forums

Question
I am researching an issue where our users are being disconnected from our Application and SQL Server.

I discovered the message Error: 17836, Severity 20, State 17; Length specified in network packet payload did not match number of bytes read in the SQL Server Error Log.

When the above message is encountered, is only the single connection affected, or could this cause SQL server to disconnect all sessions?

At the time of the error, our Network folks were performing various scans across the enterprise.

Thanks.

DJ

Answers

When the above message is encountered, is only the single connection affected, or could this cause SQL server to disconnect all sessions?

Since the error message refers to data coming on a single connection, there is no reason why SQL Server would throw out everyone.

But if the network team were fooling around, they have severed the connection for several users, and on some connection this resulted in corruption of a packet that was in flight.

Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
- Marked as answer by
  
  Wednesday, June 10, 2015 12:36 PM

Источник

Remove From My Forums

Question
I am researching an issue where our users are being disconnected from our Application and SQL Server.

I discovered the message Error: 17836, Severity 20, State 17; Length specified in network packet payload did not match number of bytes read in the SQL Server Error Log.

When the above message is encountered, is only the single connection affected, or could this cause SQL server to disconnect all sessions?

At the time of the error, our Network folks were performing various scans across the enterprise.

Thanks.

DJ

Answers

When the above message is encountered, is only the single connection affected, or could this cause SQL server to disconnect all sessions?

Since the error message refers to data coming on a single connection, there is no reason why SQL Server would throw out everyone.

But if the network team were fooling around, they have severed the connection for several users, and on some connection this resulted in corruption of a packet that was in flight.

Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
- Marked as answer by
  
  Wednesday, June 10, 2015 12:36 PM

Источник

Remove From My Forums

Question
I am researching an issue where our users are being disconnected from our Application and SQL Server.

I discovered the message Error: 17836, Severity 20, State 17; Length specified in network packet payload did not match number of bytes read in the SQL Server Error Log.

When the above message is encountered, is only the single connection affected, or could this cause SQL server to disconnect all sessions?

At the time of the error, our Network folks were performing various scans across the enterprise.

Thanks.

DJ

Answers

When the above message is encountered, is only the single connection affected, or could this cause SQL server to disconnect all sessions?

Since the error message refers to data coming on a single connection, there is no reason why SQL Server would throw out everyone.

But if the network team were fooling around, they have severed the connection for several users, and on some connection this resulted in corruption of a packet that was in flight.

Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
- Marked as answer by
  
  Wednesday, June 10, 2015 12:36 PM

Источник

Remove From My Forums

Question
I am getting below error on SQL Server 2005 instance.

2009-04-18 08:03:03.750 Logon        Error: 17836, Severity: 20, State: 1.
2009-04-18 08:03:03.750 Logon        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: 10.26.32.96]
Error: 17836, Severity: 20, State: 1.
2009-04-25 08:03:07.090 Logon        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: 10.26.32.96]
009-05-02 08:02:49.890 Logon        Error: 17836, Severity: 20, State: 1.
2009-05-02 08:02:49.890 Logon        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: 10.26.32.96]

Sivaprasad S
http://sivasql.blogspot.com
Please click the Mark as Answer button if a post solves your problem!

Answers

Perform a nslookup of the CLIENT IP Address that is listed in the error message and find out what computer it is that is connecting. Then you need to check that machine and determine what specifically is connecting to the SQL Server. You might get more infromation from doing a SQL Trace for the Errors and Warnings Event Class and have the ClientProcessID column in the trace data. When the error spikes, you might get the PID for the process that is connecting from that 10.26.32.96 machine, and then you can find that process in Task Manager on that machine by adding the PID to the data displayed (View -> Select Columns).

Jonathan Kehayias
http://sqlblog.com/blogs/jonathan_kehayias/
http://www.sqlclr.net/
Please click the Mark as Answer button if a post solves your problem!
- Marked as answer by
  
  Wednesday, May 13, 2009 9:53 AM

Источник

One of the prospect in hardening SQL Server includes changing the port from default 1433 to a customized one.

And while making such changes, application teams unknowingly try to establish connections and in turn, we notice the below errors in SQL Server error log file-

Error: 17836, Severity: 20, State: 17.
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.

Users can lose connectivity to SQL Server if such error message is reported in the SQL Server error log file.

This issue occurs when the Detect services running on non-standard ports option is enabled in the Discovery module. The event is logged because SQL Server 2005/8/8R2 is unable to interpret the incoming packet.

Perform a nslookup of the CLIENT IP Address that is listed in the error message and find out what computer it is that is connecting. Then you need to check that machine and determine what specifically is connecting to the SQL Server. You might get more infromation from doing a SQL Trace for the Errors and Warnings Event Class and have the ClientProcessID column in the trace data. When the error spikes, you might get the PID for the process that is connecting from that machine, and then you can find that process in Task Manager on that machine by adding the PID to the data displayed (View -> Select Columns).

If you have antivirus running on your system and SQL Server is not running default port then Disable the Detect services running on non-standard ports option in the scan configuration.

Hope this helps.

Cheers!
Aman Kharbanda

Database Consultant by profession.
I am a geek and a avid sports lover too.

«Progress informed by the past, inspired by future».
View all posts by sqlserverposts

Источник

February 9, 2013 at 4:02 pm

#273941

Greetings fellow SQL enthusiasts. I was alerted to this error on both SQL 2008 and 2005 instances and just beginning to troubleshoot. The error does not appear to be recurring, and as you see from the error message below, the client was on a subnet address.

I have reviewed Windows logs, including security logs, and have not come across anything else unusual. I have also checked the configuration history of each SQL Server to see if there have been any unauthorized changes. I am open to suggestions from my all time favorite SQL Server community 🙂

Excerpt from SQL Server error logs:

Error: 17836, Severity: 20, State: 17.

SourceLogon

Message

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: 165.xx.xx.x]
Gail Shaw

SSC Guru

Points: 1004494

Buggy network driver, something broken somewhere on the network or a hack attempt.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass
SQLmountain

SSCommitted

Points: 1505

Thank you Gail, I will surely look into that.

Fingers crossed, the error still has not recurred, but I will be looking out for it. When I get back to the office Monday morning I’ll be able to have a close talk with the sysadmin as well, to see if we are running any new network monitoring software that might have triggered the error.
john.saldanha

SSC Enthusiast

Points: 174

Please check if a critical watch server is causing this error. A CW server is used for the security scan for vulnerabilities. Since it is a scanner for exploring the security vulnerabilities, this behavior might be expected .

Traditionally this type of products tries to find any vulnerability including accounts with blank passwords, that is why it should try to access the DB.

Get with you company security officer to find out.

John
SQL-DBA

Hall of Fame

Points: 3050

john.saldanha (10/27/2013)

Please check if a critical watch server is causing this error. A CW server is used for the security scan for vulnerabilities. Since it is a scanner for exploring the security vulnerabilities, this behavior might be expected .

Traditionally this type of products tries to find any vulnerability including accounts with blank passwords, that is why it should try to access the DB.

Get with you company security officer to find out.

John

Exactly. The same thing happened in our shop during a Tenable security scan.

Viewing 5 posts — 1 through 4 (of 4 total)

Источник

Ms sql server ошибка 17836

Question

Answers

Question

Answers

Question

Answers

Question

Answers

А вот еще интересные материалы: