Share via

XP VM to SQL Server/Win11 ODBC Connection gets SQL error 772

Terry Lindeman 0 Reputation points
2023-05-08T22:23:23.7233333+00:00

Hi:

I have been searching for two days and can't find a solution for this. I am supporting clients using an ERP system written in ancient Visual Basic. The VB development environment won't run on anything more recent than Windows XP. (I know, you weren't even born yet!) So, I have been using a Hyper-V VM for many years. It connects to my host system using XP's ODBC driver. It works fine on a Windows 10 dev system with any version of SQL Server up to 2022. However, I recently purchased a Windows 11 Pro system. The VM works fine. SQL 2022 works fine. However, the ODBC Driver is getting SQL Server error 772, which is supposedly related to TLS 1.2, which the XP ODBC driver does not support. SQL is not requiring encryption. I can't find anything that says that encryption of an XP ODBC connection is even possible without a lot of work that I definitely didn't do. Windows 11 seems to be the only difference between a working and non-working environment. Can someone offer me some advice? Thanks in advance!

Terry

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,361 questions
VB
VB
An object-oriented programming language developed by Microsoft that is implemented on the .NET Framework. Previously known as Visual Basic .NET.
2,668 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,989 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jiachen Li-MSFT 29,261 Reputation points Microsoft Vendor
    2023-05-09T01:29:24.81+00:00

    Hi @Terry Lindeman ,

    • The most common reason for this error is the use of an ODBC driver that requires TLS 1.0. Most of the browsers have officially removed the support for TLS versions 1.0 and 1.1. You can manually start TLS 1.0. Open the registry and go to below path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0 To enable the TLS version change the value in the enabled file to 1. similarly, changing it to 0 will disable it.
    • You could try to move to a more recent ODBC driver, for instance ODBC Driver 18 for SQL Server.

    Best Regards.

    Jiachen Li

    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Terry Lindeman 0 Reputation points
    2023-05-10T17:08:40.9533333+00:00

    I think you are right, Erland. It's interesting that SQL does not require encryption but the OS is apparently forcing the issue. I am hopeful there is a Windows 11 setting to not require encryption in the VM connection, I have found that you can turn on or off TLS 1.0, 1,1, 1.2 and/or 1.3 in internet options. I haven't found anything similar for the local network, but will keep looking.

    I downloaded ODBC 11, but XP says it is not supported on that OS.

    I tried explicitly enabling and disabling TLS 1.0 in the XP registry for both server and client, but get the same results.

    Thanks for your suggestions. They gave me some more paths to follow, but alas, they were dead ends.

    I've found a way to install TLS 1.2, but I am hesitant to use thord party products.

    Thanks

    Terry

    0 comments