DLL error on connecting to Latin1_General_BIN collation server using Docker image

There is a DLL error being throwing when trying to connect to mcr.microsoft.com/mssql/server:2017-latest on Docker using Latin1_General_BIN with the node.js tedious driver. More info can be found here: https://github.com/tediousjs/tedious/issues/1195

For e.g., running this command: docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=Password(12)" -e "MSSQL_COLLATION=Latin1_General_BIN" -p 1433:1433 -d mcr.microsoft.com/mssql/server:2017-latest

Tedious returns an error thrown from the server: RequestError: Could not load the DLL (server internal), or one of the DLLs it references. Reason: 126(The specified module could not be found.).

Any thoughts?

Thanks!

Erland Sommarskog 109.8K Reputation points MVP

2021-01-06T23:02:19.59+00:00

I installed a docker image according to the above and did a quick test through SQLCMD, but the issue did not repro.

The issue could be related to tedious (with which I am unacquainted, but the error message clearly comes from SQL Server.

Any particular reason you want a BIN collation and not a BIN2? BIN collations are quite funny. They swap the bytes of the first character in nvarchar, but the rest is byte-wise comparing. In a BIN2 collation they are comparing on character codes all the way.
Ian Chok (Simba Technologies Inc) 1 Reputation point

2021-01-06T23:11:08.67+00:00

According to the original poster, they were able to connect successfully using other drivers such as "msnodesqlv8@2, sqlcmd, pymssql, PHP PDO, and JDBC via DataGrip", so indeed it could be tedious driver, but OP also posted the error logs from the server:
2020-12-24 01:36:03.31 spid51 Error: 17750, Severity: 16, State: 0. 2020-12-24 01:36:03.31 spid51 Could not load the DLL (server internal), or one of the DLLs it references. Reason: 126(The specified module could not be found.) which indicates a missing internal module.

Also note, another tedious maintainer was also able to reproduce the error on mcr.microsoft.com/mssql/server:2019-latest container as well.
Ian Chok (Simba Technologies Inc) 1 Reputation point

2021-01-06T23:15:18.117+00:00

Sorry I just realized that it's the same error posted earlier.
Cris Zhan-MSFT 6,626 Reputation points

2021-01-11T03:42:46.1+00:00

Hi,
Just following up. Is there any update on this case?

3 answers

Erland Sommarskog 109.8K Reputation points MVP

2021-01-07T22:35:37.463+00:00
I tried connecting to the Docker image with a .NET client and that worked.

Unfortunately, I don't think I can try Tedious myself, because I'm not at all into Javascript. But there must be something that you are API is doing differently that provokes this error.

But here are some things to try to narrow this down a bit:

Install a regular SQL Server instance with Latin1_General_BIN as the server collation.

Try other collations, for instance Latin1_General_BIN2.

When you get this error, do you get it directly on connection? Or do you need to submit a query?
Please sign in to rate this answer.

1 person found this answer helpful.
Ian Chok (Simba Technologies Inc) 1 Reputation point

2021-01-07T23:07:54.767+00:00

Ah sorry I should've clarified that the error occurs when submitting a query. Connection seems fine.

Gozdzielewski, Slawomir 1 Reputation point

2021-07-07T06:10:53.283+00:00

I have similar issue, with Latin1_General_BIN2, when I try to execute sp_executesql procedure, I get this error:
Msg 17750, Level 16, State 0, Procedure sp_executesql, Line 1 [Batch Start Line 0]
Could not load the DLL (server internal), or one of the DLLs it references. Reason: 126(The specified module could not be found.).

Erland Sommarskog 109.8K Reputation points MVP

2021-07-07T08:26:04.81+00:00

Are you using Tedious? Are you connecting to Docker?

If you are using Tedious, and want to add your input, you should probably post to the GitHub issue listed in the original post.

If you are not using Tedious, you should post a new Question, and include a full description of your environment and the steps you are taking.

Gozdzielewski, Slawomir 1 Reputation point

2021-07-07T08:31:09.01+00:00

Hi,

I have started docker container with latest MSSQL 2019 image, and collation set to one I mentioned. Then I connected to it by SSMS and tried to execute exec sp_executesql 'select 1'. As a result I got error as above.

Erland Sommarskog 109.8K Reputation points MVP

2021-07-07T09:10:27.577+00:00

So you are not using Tedious. Please start a new thread, so that it is easier to track.

In you Question, please include the full information about your environment, including the name of the Docker image and the host OS.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Erland Sommarskog 109.8K Reputation points MVP

2021-01-08T17:23:55.407+00:00

I looked at Tedious at little more and I realise that you speak TDS directly from Javascript without an underlying API.

I will have to say that there is a fair chance that you are not doing something a bit incorrectly. But what exactly what it would be, I don't know.

You should absolutely test against a non-Docker instance of SQL Server with Latin1_General_BIN as the server collation. And preferably both on Windows and Linux. If it fails in these two cases, I would be quite confident that this is an issue in Tedious.

Does any query fail, for instance a simple one as SELECT 1 AS n? Or does it have to be one with parameters? String parameters? (These are questions I mainly ask to inspire your troubleshooting.)
Please sign in to rate this answer.

1 person found this answer helpful.
Ian Chok (Simba Technologies Inc) 1 Reputation point

2021-01-08T20:25:19.817+00:00

Thanks for the feedback! I'll definitely take a deeper dive and try to see what is going on and see if I can answer your questions!

David Browne 111 Reputation points Microsoft Employee

2021-01-08T20:39:40.133+00:00

tediousjs is a community open-source project, and it's a direct implementation of the TDS protocol, not using a Microsoft-supported driver stack. So there may well be bugs in its handling of the network protocol. If you can repro the problem, post an issue to its repo: https://github.com/tediousjs/tedious/issues
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Erland Sommarskog 109.8K Reputation points MVP

2021-07-07T22:34:53.737+00:00
Thanks to Sławomir's post, it is clear that this is purely an SQL Server, and Tedious was just an unfortunate victim. I was able to repro the problem by installing SQL Server with a BIN2 collation, and then running

EXEC sp_executesql N'SELECT 1'
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

DLL error on connecting to Latin1_General_BIN collation server using Docker image

3 answers

Your answer