How to fix ODBC error 772 windows 11 22H2

Question

ODBC connection with sql server 2005 (compatible 2000) failed after november update.

January update didn't fix the problem.

Already tried with installing newer version of the ODBC driver, but this didn't work.

Anyone any other idea ?

Answer 1

Had the same issue and Error and managed to get it working using the below fix, you will need to either put in a GPO or change the local group policy settings to the below.

In Group Policy go Computer Configuration -> Administrative Templates -> Network -> SSL Configuration Settings

Open SSL Cipher Suite Order, set it to enabled and replace with the below.

TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_NULL_SHA256,TLS_RSA_WITH_NULL_SHA,TLS_PSK_WITH_AES_256_GCM_SHA384,TLS_PSK_WITH_AES_128_GCM_SHA256,TLS_PSK_WITH_AES_256_CBC_SHA384,TLS_PSK_WITH_AES_128_CBC_SHA256,TLS_PSK_WITH_NULL_SHA384,TLS_PSK_WITH_NULL_SHA256

Answer 2

I also have the same question. The January update seems to update the sqlsrv32.dll in the windows\system32 folder. I had to add the registry entries manually and reboot. That did not help. Other systems running the 21H1 version are connecting ok to the leagacy system. The new systems with the 22H2 version will NOT connect. I get the exact same errror message as Kristine above.

Are there other suggestions of what to try?

Thanks, andrejs

Answer 3

I have exactly the same problem with version 22H2. The update in January that was supposed to fix the problem has made no difference. The only way I could get the machine working again was by reverting to a previous version. Hopefully this can be resolved soon.

It has now been over 3 months without a fix.

Gordon

Answer 4

Hi Kristine Heyman,

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.

For more information, please refer to this link: [https://bobcares.com/blog/sql-server-error-772/

BTW, what is the version of ODBC you used?

Best regards,

Seeya

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Answer 5

You are using the SQL Server ODBC driver that comes with the OS and which originally shipped 20 years ago. You should move to a more recent ODBC driver, for instance ODBC Driver 18 for SQL Server.