Share via

I cannot create a protection group getting wmi error 33507

John Fournier 35 Reputation points
2023-06-29T06:14:08.66+00:00

On a server with no antivirus (removed Defender) and no other backup software (even tried removing Windows Server Backup), I am unable to create a protection group. At the end it always says error 33507: dpm could not execute a WMI query.

The server used to have iDrive on it, but it was removed before MABS was installed.

No solution I've been able to find online has made any difference.

Running Server 2016 and DPM 14.0.30.0

Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
1,490 questions
Accepted answer
  1. Amardeep Saini 1,735 Reputation points Microsoft Employee
    2023-07-12T16:33:55.88+00:00

    Hey John, seems you have installed MABSv4 on Windows Server 2016 which is not supported OS version.

    Please check the below article as the supported version for MABSv4 is Windows Server 2019 or Windows Server 2022.

    https://learn.microsoft.com/en-us/azure/backup/backup-azure-microsoft-azure-backup#using-an-on-premises-server

    I would suggest installing MABSv4 on supported OS version and then try to create the protection group which might work.

    1 person found this answer helpful.

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Tech-Hyd-1989 5,816 Reputation points
    2023-06-29T06:19:22.59+00:00

    Hello John Fournier

    Error 33507 in Data Protection Manager (DPM) indicates a problem with the Windows Management Instrumentation (WMI) queries that DPM uses to interact with the system. This error can occur due to various reasons, such as misconfiguration, corrupted WMI repository, or conflicts with other software. Here are a few troubleshooting steps you can try to resolve the issue:

    Ensure WMI Service is running:

    • Open the Services console (services.msc).
    • Locate the "Windows Management Instrumentation" service and ensure it is running. If it's not, start the service.
    1. Rebuild the WMI repository:
    • Open an elevated Command Prompt.
      • Run the following commands one by one:
       net stop winmgmt
winmgmt /resetrepository
    1. Verify WMI namespace security settings:
    • Open the "wbemtest" utility by searching for it in the Start menu.
      • Click "Connect" and leave the default namespace as root\cimv2.
      • Click "Connect" again without entering credentials.
      • Click "Enum Classes" and ensure you can see the list of classes without any errors.

    Check for conflicting software:

    • Make sure there are no other backup software or antivirus solutions installed on the server that could interfere with DPM's operations.
    • If any remnants of iDrive or other backup software are still present, try removing them completely using the manufacturer's removal tool or manual cleanup procedures.

    Reinstall Data Protection Manager:

    • If the above steps do not resolve the issue, consider uninstalling and reinstalling DPM.
    • Before reinstalling, ensure that you have a backup of the DPM database and the necessary configuration settings.

    It's worth mentioning that running a server without any antivirus protection is generally not recommended as it exposes the system to potential security risks. Consider reinstalling a reliable antivirus solution to protect your server.

    If the issue persists after following these steps, you may need to consult Microsoft Support or the DPM community for further assistance, as they can provide more specific guidance tailored to your environment.

    0 comments
  2. Amardeep Saini 1,735 Reputation points Microsoft Employee
    2023-07-14T14:39:55.9566667+00:00

    Hey John, looking at your comment you are getting WMI or 40002 error on MABS server which seems to be point on a storage issue on the REFS volume.

    Could you please try to reconfigure the Protection Group and once you have the error message could share the logs to look into it.

    You need to get the MSDPM.errlog,AccessManager.errlog and DPMRA.errlog which would be on location C:\Program Files\Microsoft Azure Backup Server\DPM\DPM\Temp.

    Please share the logs to look into it.

    0 comments
  3. John Fournier 35 Reputation points
    2023-07-14T17:14:31.4633333+00:00

    @Anonymous I'm not sure I understand your statement - You say my choice of running MABS in a 2019 VM is not recommended for production, then you suggest creating a VM in a Hyper-V server. Are you saying running a 2019VM on a 2016 Server is not recommended? Otherwise, I don't see how these are two different things.

    Regardless, this strategy has worked. I brought up a clean 2019 virtual machine, joined the domain, and installed MABSv4 and all updates. I then used the MABS console to install the DPM agent on the 2016 HyperV server/host. I have been able to create a protection group and all but one of the VMs on the 2016 server has finished syncing to Azure.

    So to clarify, are you saying that this is not a supported/recommended configuration?

    0 comments

Your answer

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