DPM agent cannot upgrade to 10.22.189 (DPM 2022 UR2) due to failure to remove previous version

Question

DPM agent cannot upgrade to 10.22.189 on Windows Server 2022 Core. Looking at the logs, the following error is noted related to uninstalling the previous version of the agent. Any suggestions on getting this to work?

UnInstallProviderCatalogAndDLL entered.

DisableNullProviderInstalled Entered

CreateNullProviderInstalledRegKey: Setting NullProviderInstalled Key to 0

DisableNullProviderInstalled Succeeded

Error in UnInstallProviderCatalogAndDLL. hr=0x80110809

Error in InstallProviderRollback. hr=0x80110809

Answer 1

Hi,

The error you're encountering while trying to upgrade the DPM agent on a Windows Server 2022 Core system seems to be related to uninstalling the previous version of the agent. The error code 0x80110809 indicates that the uninstallation process failed.

Here are some steps you can take to resolve this issue:

1.Check Dependencies:

Ensure that all necessary dependencies for the DPM agent upgrade are met. This includes having the correct permissions, sufficient disk space, and any required prerequisites. Make sure the server is up to date with Windows updates as well.

2.Manual Uninstall:

If the uninstall process fails during the upgrade, you may need to manually uninstall the previous version of the DPM agent.

3.Registry Cleanup:

After the manual uninstall, check for any remaining registry keys related to the old DPM agent. Be cautious when editing the Windows Registry and only remove keys related to the DPM agent.

4.File System Cleanup:

Check for any remaining files or folders related to the old DPM agent. You might need to delete these manually if the uninstaller didn't remove them.

5.Reboot:

After you've manually uninstalled the old agent and cleaned up the registry and file system, reboot the server to ensure that any lingering processes or services are stopped.

6.Install the New DPM Agent:

Now, try installing the new DPM agent (10.22.189) on the server again.

Answer 2

After performing a cleanup from a script given to me by Microsoft support, I was able to install the agent. I had this problem on both Windows 2022 Server Core and Windows 2022 Server Standard. While the primary protection seems to work for these systems, secondary protection does not with "Agent incompatible" errors and "Agent not reachable" warnings for the same systems that gave me agent installation problems.

I also had an issue where you could not delete protected items that was introduced in this hotfix. They have already given me a new internal build to the hotfix to solve that issue, but the agent issues remain. I'm still waiting for a solution.

Personally, I would not recommend this update at this time as it is very problematic (even by DPM standards).

Answer 3

These systems had issues with secondary protection after the manual upgrade because the secondary server was not present in the DPMRADCOMTrustedMachines and DPMRADmTrustedMachines security groups.