mssql-docker
mssql-docker copied to clipboard
microsoft
Length specified in network packet did not match the number of packets read error- 17836
Seeing the following error in Kitematic Container Log. MSSQL-SERVER linux is running but unable to connect to server
2019-07-22 21:38:12.21 Logon Error: 17836, Severity: 20, State: 17. 2019-07-22 21:38:12.21 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: 192.168.99.1]
Getting this error the when trying to create a new connection in Azure Date Studio "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server)"
I am facing the same error, but the difference is that my sql server is installed on windows server, while my .net core is containered on linux; have u find a way to fix it? someone tells me to intall SQL_AS_OLEDB.msi on that sql server machine to resolve it. I've not tried it, its company server only dba can get access to it.
My bad not the same issue, my issue is about the asp.net core 3.0 docker image.
Same issue with default version mcr.microsoft.com/mssql/server on MacOS with Docker.
2020-02-09 22:35:00.80 Logon Error: 17836, Severity: 20, State: 17. 2020-02-09 22:35:00.80 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.
Same issue for me as well, using this image: mcr.microsoft.com/mssql/server:2019-GA-ubuntu-16.04
Having the same issue with this image: mcr.microsoft.com/mssql/server:2017-latest
"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"
Anybody have a solution / workaround?
Update: I cleared out all my container volumes following this link. After that, ran a docker-compose up --build and my issue was resolved. Hope this helps someone.
This error is logged immediately multiple times a minute when starting up a container using the SQL Server image: microsoft/mssql-server-windows-developer
@sandyrogersACF I dont have that option on the newest version of Docker Desktop for Mac.
Happening to me too. Latest 2017 image. These messages only seem to appear when I have the Docker Dashboard open and am looking at the containers.
Same issue for me running Docker Desktop. I got the image from docker hub
When running it I get the following:
This looks like the typical message you will see when someone or something is trying to scan/use the SQL Server port. Does anyone have any sort of Antivirus scanning the port 1433?
The problem for me was the encription. When I disabled I could login with out issue.
anyone got solution to this issue. M facing similar issue in macbook. Docker doesnt have this option in General tab as per the above solution
Tried all of the solutions in this thread, none of them worked. I'm using the image mcr.microsoft.com/mssql/server:2019-CU15-ubuntu-20.04
I've also got this issue using mcr.microsoft.com/mssql/server:2022-latest, neither suggested workaround worked for me
I also had this issue while running the docker container for 2019 latest.
Was using the login server name : .\
When trying to connect using Sql manager - I had to specify the TCP/IP network protocol - thinking it was because I was behind a corp proxy.
This worked in the SQL Studio however when running from the Microsoft.Data.SqlClient I was getting handshake and no response from endpoint errors.
After some tracing, I noticed I was running a local install version of MSSQL also.. This was causing the above errors..
Felt pretty stupid but maybe will help others.
** Edit : 2019 Latest not 2017
I also had this issue while running the docker container for 2019 latest.
Was using the login server name :
.\When trying to connect using Sql manager - I had to specify the TCP/IP network protocol - thinking it was because I was behind a corp proxy.
This worked in the SQL Studio however when running from the
Microsoft.Data.SqlClientI was getting handshake and no response from endpoint errors.After some tracing, I noticed I was running a local install version of MSSQL also.. This was causing the above errors..
Felt pretty stupid but maybe will help others.
** Edit : 2019 Latest not 2017
Now that I think of it...this is almost certainly my issue too! I'll test and confirm.