Change Automation stops working after latest update (to version 4.5.23019.535)
Grisu
Posts: 4 New member
We experience issues with SQL Change Automation over Azure DevOps with the latest update to version 4.5.23019.535. It seems like the connection is broken, even though "Trust server certificate" is set in the build and/or release step. Everything is still working fine when specifying version 4.5.23011.422.
Error given is:
[error]SQLCompare.exe terminated with the exit code 126: Failed due to a SQL Server error.
Error given is:
[error]SQLCompare.exe terminated with the exit code 126: Failed due to a SQL Server error.
SQLCompare.exe produced this error output:
Error: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The target principal name is incorrect.)
Is there something wrong with this version?
Is there something wrong with this version?
Tagged:
Answers
One of our other customers hitting this issue resolved it by placing the certificate on the target server
Kind regards
Dan Calver | Redgate Software
Have you visited our Help Center?
I thought the whole idea behind this "Trust Server Certificate" to accept every certificate/skip certificate check?
The issue here is that I don't have access to the Windows machine where SQL Server is running on because we use this as a PaaS instance and also not to the build machine itself.
Other ideas to fix this issue?
Hi @Grisu
I'm going to escalate this to the developers and get some more ideas on the solution
If you specifically set the SQL Change Automation version in the pipeline to "4.5.23011.422" you'll be able to get up and running again in the meantime!
Kind regards
Dan Calver | Redgate Software
Have you visited our Help Center?
Hi @Grisu
Nothing yet, I'll post when there's new information
Kind regards
Dan Calver | Redgate Software
Have you visited our Help Center?
This should now be resolved in the latest version, could you please verify this?
Kind regards
Dan Calver | Redgate Software
Have you visited our Help Center?
I just tried it again and it looks still broken. Is my version the latest one? Please see script location below.
...
...
That's frustrating as it's the right version. In this case I'm going to reach out via the support ticket so I can grab the verbose logs from yourself to pass onto the development team!
Kind regards
Dan Calver | Redgate Software
Have you visited our Help Center?