Share via

Cannot enumerate local SQL Server databases on Primary DPM 2025

Michael 86 Reputation points
2025-01-15T02:17:01.59+00:00

When attempting to create a new protection group for the primary DPM server’s database, errors 964 (Please make sure that writer is in good state) and 966 (Please make sure that SQL server instance is in good state) are generated when I refresh the primary DPM server in the Protection Group Wizard tree control. The SQL server is installed on the same system as the DPM server. All the databases except the DPM database give error 964 (master, etc.) while error 966 is given for the DPM database.

Any ideas to the cause? Thanks.

Microsoft System Center | Other
Answer accepted by question author
  1. Amardeep Saini 1,740 Reputation points Microsoft Employee
    2025-01-15T08:12:41.4933333+00:00

    Hi @Michael, Thank you for contacting us on Microsoft Q&A platform. Happy to help!

    I am assuming you might be using SQL 2022 for installing DPM 2025. 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.

    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

    2 people found this answer helpful.
    0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. XinGuo-MSFT 22,246 Reputation points
    2025-01-15T07:31:46.8266667+00:00

    Hi,User's image

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

    If the DPM SQL Server instance isn't running on the DPM server, install the DPM protection agent on the SQL Server computer before you can protect the DPM databases on that server.

    https://learn.microsoft.com/en-us/system-center/dpm/back-up-the-dpm-server?view=sc-dpm-2025#back-up-the-dpm-database

    0 comments
  2. Michael 86 Reputation points
    2025-01-15T15:31:26.3333333+00:00

    As I said in the initial message, the SQL server is running on the DPM server. It is SQL 2019 as I upgraded an old DPM 2022 server in place.

    The issue is the SQL OLEDB drivers were not installed on the DPM server. I installed them on my other protected SQL data sources because the error messages were very clear for those when they failed. I should have thought of this for the DPM server itself as well. Of course, may be DPM should install these on the DPM server as part of the installation process since this is probably a common configuration?

    0 comments
  3. JEmlay 46 Reputation points
    2025-07-09T03:15:11.8566667+00:00

    Warning for anyone doing this. My ONLY issue was DPM not being able to enumerate it's own SQL Server. We are SQL 2022 company wide. I had no issue with any of my clients or servers. I was able to backup all other SQL Servers. Just not the DPM SQL Server.

    After installing VC++ x86, updating the x64 version to match and installing OLE DB v19 (it was on 18 which is what installs by default) on the DPM server I can no longer see any database instances on any client or server. I no longer get the error but my DPM 2025 server is now no longer able to see any SQL DBs anywhere and all protection groups containing SQL instances are now in a failed state.

    At least for me, this was horrible advice.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.