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
