Activity overview
Latest activity by BlueBSH
After a lot of testing and a lot of VM snapshots to isolate changes.... I traced this down to TLS 1.3 being enabled in windows server, if you remove the registry keys for TLS 1.3 it works, put them back error / comments
After a lot of testing and a lot of VM snapshots to isolate changes.... I traced this down to TLS 1.3 being enabled in windows server, if you remove the registry keys for TLS 1.3 it works, put them...
Created a Windows Server 2019 VM and installed SQL 2017 then upgraded to SQL 2019 like this problem environment was, then tried to connect and it worked fine.. leading me to believe something is not correct on the server, but it's still odd that only SQL Compare and SQL Data compare have an issue and nothing else does / comments
Created a Windows Server 2019 VM and installed SQL 2017 then upgraded to SQL 2019 like this problem environment was, then tried to connect and it worked fine.. leading me to believe something is no...
Mark R said:
BlueBSH said:
To make this more confusing why do I need to trust a server certificate on a server that does not have encryption enabled? There should be no SSL exchange happening if encryption isn't set up or enforced... I get this same problem on a system that has no SSL encryption so there is no cert to trust
As you're not expectingt the connection to be encrypted, could you try adding ;Encrypt=False to the server name?
I've tried that also before posting this and no luck / comments
Mark R said:
BlueBSH said:
To make this more confusing why do I need to trust a server certificate on a server that does not have encryption enabled? There should be no SSL exchange h...
Same error in 14.6.0 / comments
Same error in 14.6.0
Mark R said:
Huh. If the same problem happens when on the server itself, it can't possibly be the issue from that Microsoft doc as that's about running things on *different* Windows versions!
What authentication method are you using?
We use windows authentication only, server is set up to only allow that we also only use TCP/IP for connections. The 14.5 version will connect to our Server 2012R2 / SQL Server 2017 system with no issues, just this with 14.5 to our Sever 2019 / SQL 2019 box. / comments
Mark R said:
Huh. If the same problem happens when on the server itself, it can't possibly be the issue from that Microsoft doc as that's about running things on *different* Windows versions...
Mark R said:
Is the connection
- on the local machine
- over the LAN
- over the internet?
Everything is local inside a windows domain on machines on the same domain I can even reproduce this locally on the server / comments
Mark R said:
Is the connection
- on the local machine
- over the LAN
- over the internet?
Everything is local inside a windows domain on machines on the same domainI can even reproduce th...
DanC said:
Hi @BlueBSH I suspect actually you may be hitting this, please see the following: https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/apps-forcibly-closed-tls-connection-errors
I've already went down that KB article route... If that was the case then why does version 13.8 work of data compare? It would still be an issue in 13.8 if that was the case.. It also makes no sense why this is only affecting SQL compare and SQL Data compare and no other red-gate products on the latest releases / comments
DanC said:
Hi @BlueBSH I suspect actually you may be hitting this, please see the following:https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/apps-forcibly-closed-tls-conn...
Also, that doesn't work either [image] / comments
Also, that doesn't work either
BlueBSH said:
DanC said:
Hi @BlueBSH This error came about due to the recent update on the Microsoft Data
Connection client update and so now you will need to do the following: You
can work around this by adding ";Trust Server Certificate=true" to
the end of the server name in the connection dialog. [image] [image]
I'm sorry, but that is not a good solution.... our security policy forbids us from trusting certificates blindly.. our certificate is valid and signed by a CA it shouldn't need to be trusted
To make this more confusing why do I need to trust a server certificate on a server that does not have encryption enabled? There should be no SSL exchange happening if encryption isn't set up or enforced... I get this same problem on a system that has no SSL encryption so there is no cert to trust / comments
BlueBSH said:
DanC said:
Hi @BlueBSH This error came about due to the recent update on the Microsoft Data
Connection client update and so now you will need to do the following:You
can ...
DanC said:
Hi @BlueBSH This error came about due to the recent update on the Microsoft Data
Connection client update and so now you will need to do the following: You
can work around this by adding ";Trust Server Certificate=true" to
the end of the server name in the connection dialog. [image] [image]
I'm sorry, but that is not a good solution.... our security policy forbids us from trusting certificates blindly.. our certificate is valid and signed by a CA it shouldn't need to be trusted / comments
DanC said:
Hi @BlueBSH This error came about due to the recent update on the Microsoft Data
Connection client update and so now you will need to do the following:You
can work around this by a...