none
DPM 2016 Agent installation throwing error saying Fatal error during installation with error code 0x80070643

    Question

  • Hi,

    Im trying to install the DPM 2016 agent manually on few servers which are having Win 2012 R2 OS.It worked for most,but for few,it throws this error saying fatal error during installation with the error code 0x80070643.

    The MSDPMAgent.log has this error message:

     Note: 1: 2205 2:  3: Error 

     Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708

     Note: 1: 2205 2:  3: Error 

    Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 

    Product: Microsoft System Center 2016  DPM Protection Agent -- Installation failed.

    Windows Installer installed the product. Product Name: Microsoft System Center 2016  DPM Protection Agent. Product Version: 5.0.158.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

    The MSDPMAgentBootstrap0Curr error log file throws this error:

    WARNING Failed: Hr: = [0x80070424] : Encountered Failure: : lVal : (HANDLE)(schService = OpenServiceW( schSCManager, strServiceName.PeekStr(), (0x00010000L) | 0x0020 | 0x0004 | 0x0002))

    WARNING Failed: Hr: = [0x80070424] DeleteServiceByName for service[DPMRA] failed

    WARNING Failed: Hr: = [0x80070426] StopService failed for service[VssNullProvider] and returned

    WARNING Failed: Hr: = [0x8004e00f] : Encountered Failure: : lVal : pCOMAdminCatalog->GetCollection(bsApplications, (IDispatch**)&pAppsCatalogCollection)

    WARNING Failed: Hr: = [0x80070426] StopService failed for service[VssNullProvider] and returned

    WARNING Failed: Hr: = [0x8004e00f] : Encountered Failure: : lVal : pCOMAdminCatalog->GetCollection(bsApplications, (IDispatch**)&pAppsCatalogCollection)

    WARNING Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : reg.DeleteValue(g_wszLaunchPermission)

    WARNING Failed: Hr: = [0x80070426] StopService failed for service[DPMRA] and returned

    Had gone through various other threads where people faced the same issue.Nothing has helped till now.

    Could anyone please suggest what needs to be done to resolve this?

    Tuesday, August 8, 2017 10:28 AM

Answers

All replies

  • Same issue.

    My hyper-v host was running Hyper-V Server 2012R2 and had a 2012R2 protection agent which was uninstalled.

    Maybe QA didn't realize that some users would like to upgrade instead of running a clean install and replicating 30TB of data over the WAN again.


    -=Chris

    Mine seems to bomb around here.

    InstallProvider entered.
    Unregistering VSS providers
    UnInstallProviderCatalogAndDLL entered.
    DisableNullProviderInstalled Entered
    CreateNullProviderInstalledRegKey: Setting NullProviderInstalled Key to 0
    DisableNullProviderInstalled Succeeded
    Error in UnInstallProviderCatalogAndDLL. hr=0x80110809
    Error in InstallProvider. hr=0x80110809
    CustomAction _InstallProvider.E785582E_DD9D_4A85_B866_3A1BC05C6110 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (20:AC) [17:44:13:895]: Note: 1: 2265 2:  3: -2147287035

    • Edited by Progent.CT Tuesday, August 22, 2017 12:51 AM
    Monday, August 21, 2017 9:12 PM
  • I found a solution.

    Altaro VM Backup.


    -=Chris

    • Marked as answer by Jenny Annet Wednesday, August 23, 2017 5:13 AM
    Tuesday, August 22, 2017 3:08 AM
  • We had to open a case with Microsoft and finally after troubleshooting, the issue was found to be of the DCOM. The DCOM component services weren't enabled.

    Once we got the DCOM services up and running, we were able to install the agents successfully.

    Tuesday, August 22, 2017 11:17 AM
  • What exactly did you have to do to fix this with DCOM?

    I am attempting to install the agent on Server 2016 Core, and DCOM services are all up and running.

    Thursday, March 7, 2019 5:06 PM
  • What exactly did you have to do to fix this with DCOM?

    I am attempting to install the agent on Server 2016 Core, and DCOM services are all up and running.

    Would love to know as well.

    -=Chris

    Thursday, March 14, 2019 10:18 PM