Data Protection Manager (DPM) problems backing up SQL Server 2016 with TLS 1.2

Question

I am having problems backing up some SQL 2016 servers using the latest build of DPM 2019 after enabling only TLS 1.2 on them. When I look in agent logs, I see these errors:

1810 1534 07/03 10:57:24.141 03 sqlqueryhelper.cpp(196) [0000001290CBEEB0] C732D443-1F8D-4877-9021-A564FFC66E28 WARNING Failed: Hr: = [0x80004005] SQL Instance - [......] refusing connection

1810 1534 07/03 10:57:24.141 03 sqlqueryhelper.cpp(339) [0000001290CBEEB0] C732D443-1F8D-4877-9021-A564FFC66E28 WARNING SQL - Error Description "[DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error."

1810 1534 07/03 10:57:24.141 03 sqlqueryhelper.cpp(352) [0000001290CBEEB0] C732D443-1F8D-4877-9021-A564FFC66E28 WARNING Failed: Hr: = [0x80004005] SQL - sql code = 18 (Errorlevel - 0)

I have tried reinstalling agent, installing newest SQL ODBC and native drivers and nothing seems to help.

Answer 1

I run for an issue where DPM 2025 was unable to enumerate any SQL 2019 databases. It could enumerate all SQL 2025 databases. I got DPM error 964 and 966. As per the hint, I updated all OLEDB and ODBC drivers to match the same on DPM and all SQL Servers instances. Only after that I could enumerate sql databases in individual SQL servers and SQL Clusters. I been able to get the checkboxes displayed and able to select database for backup. What I suspect is that DPM does not just rely on VSS. It also uses SQL client libraries underneath for:

Metadata enumeration

AG detection

• Database listing
• Replica creation
• Log chain validation

Took me 3 days to sort it out. greg

Answer 2

I run for an issue where DPM 2025 was unable to enumerate any SQL 2019 databases. It could enumerate all SQL 2025 databases. I got DPM error 964 and 966. As per the hint, I updated all OLEDB and ODBC drivers to match the same on DPM and all SQL Servers instances. Only after that I could enumerate sql databases in individual SQL servers and SQL Clusters. I been able to get the checkboxes displayed and able to select database for backup. What I suspect is that DPM does not just rely on VSS. It also uses SQL client libraries underneath f

Hope that helps. Took me 3 days to sort it out.

Answer 3

Hi,

Based on the provided error messages, it looks like there is an issue with the SSL security while connecting to the SQL Server 2016 after enabling only TLS 1.2 on them. This is a known issue with DPM 2019 and above versions, as they do not support MSOLEDB 18 for SQL Server 2016 and 2017 which is required to perform discovery and protection of SQL Server over TLS 1.2 [^1].

To work around this issue, you can follow the below steps:

• Apply Hotfix for DPM 2019 UR1 [^1].
• Update the DPM agents, which are installed on the SQL Server 2016.
• Install MSOLEDB 18 on the protected SQL Servers.

References: [^1]: DPM 2019 Release Notes