DPM 2019 does not recognize protcted SQL Server version after upgrade

Tibor Marchyn 21 Reputation points


we have upgraded DPM 2019 protected SQL Server from 2016 to 2017 in-place. Protection works but DPM still saying that auto-protection failed.

I have looking into logs and see that DPM is still querying SQL version 2016 instead of 2017 over WMI. It didn't recognized that SQL was upgraded and Refresh in protection group showing same error regarding WMI.

I have figured it through Process Monitor and saw wmiprvse.exe asking for following path


but it should be


I have tried to remove all backups, uninstall agent, install again and add targets, but wmi error keeps showing.

In DPM agent logs is

0778 2734 12/06 12:10:43.764 03 wmiqueryhelper.cpp(145) [00000069D6E7EC60] FA6F4362-B271-46FC-9120-54A46E9F8755 WARNING Failed: Hr: = [0x80041013] : unable to execute the WQL query: SELECT * FROM ServerSettings
0778 2734 12/06 12:10:43.764 61 sqlmirroringhelper.cpp(175) [00000069D6E7F260] FA6F4362-B271-46FC-9120-54A46E9F8755 WARNING Failed: Hr: = [0x80041013] : Encountered Failure: : lVal : wmiQueryHelper.ExecuteWQLQuery(ssWMIQuery)
0778 2734 12/06 12:10:43.764 61 sqlmirroringhelper.cpp(81) [00000069D6E7F260] FA6F4362-B271-46FC-9120-54A46E9F8755 WARNING Failed: Hr: = [0x80041013] : unable to get instance names from sql 2016 wmi: lVal : GetInstanceNamesFromWMI(ssWMINamespace, arrLocalInstanceNames)

Is it possible somehow manually update protected SQL Server version from 2016 to 2017 in DPM 2019? In database or any file or registry?


SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,312 questions
0 comments No comments
{count} votes

Accepted answer
  1. Tom Phillips 17,711 Reputation points

    Your question is about System Center. I suggest you post your question here:

0 additional answers

Sort by: Most helpful