Comments
Sort by recent activity
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...
and just to add to the what the of this somehow going back to 13.8.0 triggers and easter egg that plays asteroids?! [image] / comments
and just to add to the what the of this somehow going back to 13.8.0 triggers and easter egg that plays asteroids?!
I just reverted SQL Compare back to version 13.8.0.12703 and it works again....... something isn't right with the latest version / comments
I just reverted SQL Compare back to version 13.8.0.12703 and it works again....... something isn't right with the latest version
I've now installed SQL Compare and SQL Datacompare locally on the server to test that and it still returns the same SSL Provider error....... / comments
I've now installed SQL Compare and SQL Datacompare locally on the server to test that and it still returns the same SSL Provider error.......
version that is having issues is version 14.5.1.18536 for SQL Compare and the same version for SQL Data Compare / comments
version that is having issues is version 14.5.1.18536 for SQL Compare and the same version for SQL Data Compare
To add to this I just tried to connect with SQL Doc and it connected to this same server that is throwing an error with SQL Compare with no issues. I also tried SQL Data Generator and it connected and listed the databases just fine with no errors... The only problems are with SQL Compare and SQL Data compare, what is different about them? / comments
To add to this I just tried to connect with SQL Doc and it connected to this same server that is throwing an error with SQL Compare with no issues. I also tried SQL Data Generator and it connected ...
I found the <IgnoreTfsPolicies>True</IgnoreTfsPolicies> tag and this solves this issue, but what do you do it you still do want to force comments on a check-in, is it even possible with devops and sql compare? / comments
I found the <IgnoreTfsPolicies>True</IgnoreTfsPolicies> tag and this solves this issue, but what do you do it you still do want to force comments on a check-in, is it even possible with devops and...
appears to be working correctly now / comments
appears to be working correctly now
Awesome, was trying to find a workaround for this and the Library file copy worked great / comments
Awesome, was trying to find a workaround for this and the Library file copy worked great