Executed as user: NT Service\SQLSERVERAGENT. [Microsoft][ODBC Driver 18 for SQL Server]SSL Provider: The target principal name is incorrect. Process Exit Code -1. The step failed.
@Gostev,
We had to update the ODBC Driver on a SQL server due to another product requiring it.
When will Veeam update the MSSQL plugin to allow ODBC 18 to be used for SQL back up using the product?
This is a logical progression for the product to be used for sql backup and recovery.
..and to complete this, with the upcoming 12.1.2 cumulative patch we have the plan to support ODBC driver 18 directly. But today you can use both drivers on same system to use our and your product.
So for your environment the solution is to install both drivers.
We have both odbc drivers 17 and 18 installed. The Veeam plugin for SQl installed is 12.0.3.1423. Is it possible to pin the plugin to use ODBC 17 Driver for SQL even though 18 was installed for another product that requires it for their latest upgrade?
Ideas when 12.1.2 cumulative patch will be release to the general public?
We have case #07186380 open for this issue. It appears that the Veeam MS SQL plugin process wants to use version 18 of the ODBC driver instead of 17 when both are present and then fails for both backup and restores.
Thank you. It looks like that this processing is not as expected. Upcoming patch in April will use always use the version 17 ODBC driver and will fall back to the latest. It will have a xml setting to select a specific one. If you can, please delay the ODBC18 installation and maybe if you can not consider backing up the server for some time with our Image level backup option until the new update is out.