Backing up SQL2016 server using on-premise Microsoft Azure Backups Server - DPM could not enumerate application component (ID: 964) (ID: 966)

Question

I have an on-premise MABS/DPM server 2022 and I am attempting to sync my on-premise SQL servers. I am unable to add SQL databases from 2 of my servers, a 2012 and a 2016. I am able to sync 2 other sql servers in my environment without issue.

I have updated the SQL OLE DB driver on the MABS and the SQL servers. I have validated that NT AUTHORITY\SYSTEM has the sysadmin role on the SQL servers. I have validated the VSS writers are in a functional state, have uninstalled/reinstalled the DPM client.

At this point I am at a loss how to proceed and any input would be appreciated.

Answer 1

Hi Sam O'Halloran**

Please make sure that below mentioned components are installed on DPM server:**

SQL OLEDB V19 drivers (These drivers needed to be installed on SQL server if you are protecting SQL 2022 and above)

VC++ Redistributable 2022, 32 bits and 64 bits both. VC++ Redistributable 2022 64 bits is needed as pre-req for SQL OLEDB V19 drivers and VC++ Redistributable 2022 32 bits is required as 64 bit package has the dependency on it.

After installing the above components, please restart DPM server and then try to protect DPM instance which should fix the issue.

Error 964 – "DPM could not enumerate application component from the protected server."

Error 966 – "DPM cannot protect the specified data source because it could not enumerate the application component."

These usually occur when:

DPM can't properly discover SQL instances/databases via WMI or VSS

There's a problem with the SQL VSS Writer

Network, firewall, or DCOM/WMI permissions are misconfigured

SQL instance is not fully patched or is inaccessible via standard protocols

Ensure SQL VSS Writer is Running:

vssadmin list writers

Look for:

Writer name: 'SqlServerWriter'

Writer Id: ...

State: [1] Stable

Last error: No error

If it's not listed or not stable, restart the writer:

net stop SQLWriter

net start SQLWriter

If that doesn’t work, re-register VSS writers:

cd /d %windir%\system32

net stop winmgmt

winmgmt /verifyrepository

winmgmt /salvagerepository

net start winmgmt

Verify WMI Namespace Exists

1.Run wbemtest

2.connect to root\Microsoft\SqlServer

3.If that works, try: root\Microsoft\SqlServer\ComputerManagement15

ComputerManagement10 for SQL Server 2012 (the number depends on version).

If you can't connect or browse, the WMI provider is broken. Fix by repairing SQL Server installation or re-registering the SQL WMI provider:

mofcomp "C:\Program Files (x86)\Microsoft SQL Server\120\Shared\sqlmgmproviderxpsp2up.mof"

adjust path and version accordingly: 110 for 2012, 130 for 2016, etc.)

Check SQL Version Compatibility: SQL Server 2012 is SP4, SQL Server 2016 is SP2 or higher

If the issue persists after all these checks, try these final steps:

Temporarily disable antivirus or endpoint protection — some AVs block WMI/DCOM

Use wbemtest from DPM server to test WMI connectivity remotely:

wbemtest → Connect to \<SQLServer>\root\Microsoft\SqlServer

https://learn.microsoft.com/en-us/troubleshoot/system-center/dpm/vnext-dpm-error-codes#error-codes-900-999

Kindly let us know if the above helps or you need further assistance on this issue. 

---

Please do not forget to "Accept the answer” and upvote it wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.