Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested answer

versions of GP and TLS 1.2

(0) ShareShare
ReportReport
Posted on by 366

My client is on GP 2016 16.00.0620 (R2) and need to turn on TLS 1.2 because they use Avalara - is this version of GP compatible with TLS 1.2?

Categories:
  • Suggested answer
    Derek Albaugh Profile Picture
    on at
    RE: versions of GP and TLS 1.2

    With Web Services, you must have TLS 1.0/1.1 enabled on the server or it will not work. In order to have Web Services to work with TLS 1.x disabled, you must use an AD security store with Web Services.

    community.dynamics.com/.../microsoft-dynamics-gp-web-services---how-to-setup-an-active-directory-security-store

    For SQL Server connectivity, we've found using the latest (and last?) SQL Native Client driver has resolved many issues with the ODBC DSN failing to connect to SQL.

    This article has links for SQL updates that are required for the various SQL Server versions to be able to connect via TLS 1.2, which is the protocol that would be used if TLS 1.0/1.1 were disabled.

            support.microsoft.com/.../tls-1-2-support-for-microsoft-sql-server  [support.microsoft.com] [nam06.safelinks.protection.outlook.com] [nam06.safelinks.protection.outlook.com]

    The Microsoft SQL Server 2012 Native Client QFE patch is the main one that GP would require to be able to connect to SQL 2012 or SQL 2014 should TLS 1.0 be disabled and what we've had success in with this type of DSN issues.

    Microsoft SQL Server 2012 Native Client - QFE > SQL Server 2012 Native Client (11.0.7001.0)

    The link is here:

            www.microsoft.com/.../details.aspx [microsoft.com] [nam06.safelinks.protection.outlook.com] [nam06.safelinks.protection.outlook.com]

      As it mentions in the notes at the bottom of this page:

      Note that Microsoft will not be releasing a SQL Server 2014 or later version of the SQL Server Native Client. The SQL Server 2012 Native Client (v11, e.g. sqlncli11.dll), can continue to be utilized by SQL Server 2014 and later versions.

    Thanks

  • sdcraig Profile Picture
    366 on at
    RE: versions of GP and TLS 1.2

    I was reading through what you sent but since they are using SQL Connectivity and webservcies - how do you keep those at TLS 1.0 - while taking the reset of GP to TLS 1.2

  • Suggested answer
    Derek Albaugh Profile Picture
    on at
    RE: versions of GP and TLS 1.2

    Dynamics GP itself is fine with TLS, it's more the additional functionality that may or may not be impacted by TLS, such as emailing, SQL Server connectivity, Web Services, etc.

    I'd start with the following blogs:

    community.dynamics.com/.../microsoft-dynamics-gp-fall-2020---tls-1-2

    community.dynamics.com/.../dynamics-gp-and-tls-1-0

    The second block is from 2018 when the conversation of disabling TLS 1.x began and the first blog is more related to GP 18.x.

    Let us know if you have any questions.

    Thank you,

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Ramesh Kumar – Community Spotlight

We are honored to recognize Ramesh Kumar as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Abhilash Warrier Profile Picture

Abhilash Warrier 565

#2
Martin Dráb Profile Picture

Martin Dráb 536 Most Valuable Professional

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 402 Super User 2025 Season 1

Product updates

Dynamics 365 release plans