Comments
3 comments
-
Hi,
Thanks for your post.
This error is likely due to recent changes around handling certificates and you can hopefully workaround this by adding ";Trust Server Certificate=true" to the end of the server name in the connection dialog.
If the above doesn't work. I'll raise you a ticket and we'll look again. -
that worked thank you
-
Hi, I realize that this is an older thread, but I encountered this situation today. My SQLCompare 15 was working fine and then stopped. Adding the suggestion above re: "Trust Server Certificate" did not work, but I did notice there is now a check box with the same option right on the connection dialog. Click that and it accomplishes the same thing, apparently. It was obvious to me because nothing changed about how I use this tool. Then I read this thread and noticed it.
Add comment
Please sign in to leave a comment.
the certificate chain was issued by an authority that is not trusted
the server is on a different domain but i have it registered in windows credential manager and i have no issue connecting to both source and target in SSMS so its almost as if SQ compare isnt seeing or using credential manager