Forum Discussion
Cannot connect to SQL 2022 Preview at Windows Server 2022 Standard by JDBC driver(TCP, 1433)
As a workaround until it's fixed, try disabling TLS 1.3. Either in the server OS' registry
https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings#tls-dtls-and-ssl-protocol-version-settings
Or just in SQL Server by setting the global trace flag 11808.The trace flag will be effective only after service restart. So it’s better to specify it when the service starts with the switch -T11808.It will need to be set using SQL Server Configuration Manager so that it is applied on startup.
As a workaround until it's fixed, try disabling TLS 1.3. Either in the server OS' registry
https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings#tls-dtls-and-ssl-protocol-version-settings
Or just in SQL Server by setting the global trace flag 11808. The trace flag will be effective only after service restart. So it’s better to specify it when the service starts with the switch -T11808. It will need to be set using SQL Server Configuration Manager so that it is applied on startup.
- Thanks this fix worked for me as well!
- Hi David-Engel,
Thanks for your help in figuring out its TLS compatibility issues. It's working now after I disabled TLS1.3 from OS registry.
I also tried DBCC TRACEON (11808, -1), that workaround did not work no matter if service was rebooted. Once it was rebooted DBCC TRACESTATUS was back to 0.
I believe Microsoft will resolve this before SQL Server 2022 is officially released. It's not good to ask customers to use workarounds. If it could not be resolved before it's officially released we have to document it and let customers to take the risks and use the workaround if they have to use SQL Server 2022.- You would need to enable the trace flag as a startup parameter using SQL Server Configuration Manager. Just running DBCC TRACEON won't work. (Edited my previous reply to be more specific.)
Yes, the issue is/will be resolved in the next release (RC0).- Hi David-Engel, glad to know that it will be resolved in next release (RC0). Didn't realize that you were from Microsoft SQL Server team. My company opened a ticket 698802 for this, please close that one together when it's fixed. Appreciate your help!
