SBX - Search With Button

SBX - Forum Post Title

Issue with TLS protocols and Development Environment

Microsoft Dynamics NAV Forum

Carlos Herrando asked a question on 27 Jun 2018 4:11 AM
My Badges

Question Status

Verified

Recently we have disabled protocols TLS 1.0 and TLS 1.1 in our servers and we have detected that Dynamics NAV Development environment has stoppped connecting to the database. We are using NAV 2016 CU25.

 

We get the following error quickly when trying to connect to the database.

"The XXX server cannot be found. Try again later or contact with your administrator."

 

And this one on the event viewer at the same time:

 

Source: Schannel

"A fatal error error ocurred while creating an SSL client credential. The internal error state is 10013."

 

It is not a network problem because the NAV server instances are running and connected without issues from the same server to the same database we are trying to connect. Also windows client works fine.

We are using Database Server Authentication when connecting to the database because SQL Server is installed on a server that is connected to a different domain than the server from we are trying to connect.

Could you tell us if this application is compatible with TLS 1.2? Is there any workaround to connect using TLS 1.2?

Many thanks and regards.

Reply
Sergisoft responded on 15 Aug 2018 9:46 AM

Hi Carlos,

I think we are facing the same problem. Did you finally find a solution to it?

Regards,
Sergi.

Reply
Daniel Berg responded on 28 Nov 2018 8:14 AM
My Badges
Verified Answer

We had the same problem after disabling TLS1.0 on the server for the SQL server.

The problem is not the development client (finsql.exe), but the ODBC driver used, which is installed and used by the development client.

Since we had NAV 2015 CU5 in use, the ODBC driver "SQL-Server Native Client 11.0" (2011.110.701.00) from 11.02.2012 was installed. NAV 2015 CU49 comes with the same ODBC driver from Microsoft.

You can test yourself if the ODBC driver can connect to the database. Open the program "ODBC Data Sources (64-Bit)" on the NAV server. Click in the tab "User DSN" on "Add...".

First check the driver date from "SQL Server Native Client 11.0". The date already gives the first hint if you have an old client.

Then click on "Finish".

In the new Datasource dialog enter any name and in Server enter the SQL server name.

Click "Next >" to enter the required credentials or use Windows authentication and click "Next >".

In the next window check "Change the default database to". Then try to expand the list.

If you don't get an error message, but the list unfolds and you see the existing databases, then the development client has another problem, which I don't know about.

If you get an error message, the ODBC driver cannot connect to the SQL server you have to replace it.

Error text:

Connection failed:

SQLState '08001'

SQL Server Error: 10054

[Microsoft][SQL Server Native Client 11.0]Client unable to establish connection

To do this, close the Data Resource Creation window and proceed as follows:

Download the latest 64-bit ODBC driver from Microsoft:

www.microsoft.com/.../details.aspx

Copies the sqlncli.msi to the NAV server and executes it.

When prompted if you want to update the client, click "Yes" and follow the installation instructions.

After the installation you can either open the development client directly and test the connection to the SQL server or you can do it via the "ODBC Data Sources (64-Bit)" and do the steps until loading the SQL databases.

Reply
Carlos Herrando responded on 4 Feb 2019 9:52 AM
My Badges

We talked to Microsoft and give us the same answer, thanks!!!

Reply
Daniel Berg responded on 28 Nov 2018 8:14 AM
My Badges
Verified Answer

We had the same problem after disabling TLS1.0 on the server for the SQL server.

The problem is not the development client (finsql.exe), but the ODBC driver used, which is installed and used by the development client.

Since we had NAV 2015 CU5 in use, the ODBC driver "SQL-Server Native Client 11.0" (2011.110.701.00) from 11.02.2012 was installed. NAV 2015 CU49 comes with the same ODBC driver from Microsoft.

You can test yourself if the ODBC driver can connect to the database. Open the program "ODBC Data Sources (64-Bit)" on the NAV server. Click in the tab "User DSN" on "Add...".

First check the driver date from "SQL Server Native Client 11.0". The date already gives the first hint if you have an old client.

Then click on "Finish".

In the new Datasource dialog enter any name and in Server enter the SQL server name.

Click "Next >" to enter the required credentials or use Windows authentication and click "Next >".

In the next window check "Change the default database to". Then try to expand the list.

If you don't get an error message, but the list unfolds and you see the existing databases, then the development client has another problem, which I don't know about.

If you get an error message, the ODBC driver cannot connect to the SQL server you have to replace it.

Error text:

Connection failed:

SQLState '08001'

SQL Server Error: 10054

[Microsoft][SQL Server Native Client 11.0]Client unable to establish connection

To do this, close the Data Resource Creation window and proceed as follows:

Download the latest 64-bit ODBC driver from Microsoft:

www.microsoft.com/.../details.aspx

Copies the sqlncli.msi to the NAV server and executes it.

When prompted if you want to update the client, click "Yes" and follow the installation instructions.

After the installation you can either open the development client directly and test the connection to the SQL server or you can do it via the "ODBC Data Sources (64-Bit)" and do the steps until loading the SQL databases.

Reply

SBX - Two Col Forum

SBX - Migrated JS