[Bill Jones]

?Part of our compliance requirements for all our systems is that we have to disable the TLS 1.0 protocol on all servers.  We have done this with Dynamics GP 2015 which is running on older versions of Windows Server and SQL Server versions.

We are testing the upgrade to GP2018 R2 with the intent to move to Windows Server 2016 and SQL Server 2016.  We are getting all kinds of errors with installation with GP Web Services for Dynamics GP 2018 R2 as well as some 3rd party products.  In fact, without updating the SQL Server Native Client ODBC driver, you can not even create an ODBC needed to run basic 32 bit Dynamics GP client.  In fact, you can not create an ODBC connection while on the SQL Server to connect to the SQL databases.

Has anyone else run into this?  Any ideas why TLS being disabled with SQL Server 2012 and Windows Server 2012 is ok with GP2015 R2 but when moving to 2016 Windows Server and SQL Server with GP2018 is not ok?  Anyone working with GP 2018 without TLS 1.0 with the 2016 servers?  What did you do to patch/configure your way around TLS 1.0? 

We do have TLS 1.2 enabled which should be backwards compatible but it does not appear as such.

Any help would be appreciated.
Thank you.

——————————
Bill Jones
Systems Engineer, Financial Systems
Universal Service Administrative Company
Washington DC
——————————

[Derek Albaugh]

I believe the information you’re looking for is in this blog:

Microsoft Dynamics GP and TLS 1.0
https://community.dynamics.com/gp/b/dynamicsgp/archive/2018/02/16/dynamics-gp-and-tls-1-0

Specifically the following regarding Web Services:

“The only ongoing issue that we are working through is that the install of Web Services will fail with the following error should you try to install in an environment with TLS 1.0 disabled: “Access to the Authorization Manager store was denied.”

This issue is being worked on by our Development team, and we are working at getting this resolved in a timely manner. The supported configuration for Web Services is to leave TLS 1.0 enabled until we can determine the cause and publish a resolution.”

Thanks

——————————
Derek Albaugh
Sr. Support Engineer
Microsoft
Moorhead MN
——————————
——————————————-