none
DPM 2010 Agent install error 0x80070643 RRS feed

  • Question

  • Receiving the following error trying to install the DPM 2010 agent on a Windows Server 2008 R2 box with SQL 2008:

    DPMAgentInstaller failed with errorcode =0x80070643, error says: Fatal error dur
    ing installation.

    Check log files in [WINDIR]Temp\MSDPM*.LOG
    Press Enter key to close the window

    The DPM log shows this as the failure:

    MSI (s) (1C:E8) [11:58:24:294]: Invoking remote custom action. DLL: C:\Program Files\Microsoft Data Protection Manager\DPM\bin\SetupUtilv2.dll, Entrypoint: UpdatePSDataSourceConfigXML
    UpdatePSDataSourceConfigXML Entered
    LoadPSDataSourceConfigXML Entered
    LoadLHSystemStateDSConfigXML: xml file path C:\Program Files\Microsoft Data Protection Manager\DPM\Datasources\PSDatasourceConfig.xml
    LoadPSDataSourceConfigXML: LoadXmlDocument successful
    DeleteDataSourceConfigNode Entered
    DeleteDataSourceConfigNode: Deleting Node DisconnectedClient
    DeleteDataSourceConfigNode return code = 0x00000000
    DeleteDataSourceConfigNode Entered
    DeleteDataSourceConfigNode: Deleting Node System Protection
    DeleteDataSourceConfigNode return code = 0x00000000
    DeleteDataSourceConfigNode Entered
    DeleteDataSourceConfigNode return code = 0x00000000
    DeleteDataSourceConfigNode Entered
    DeleteDataSourceConfigNode: Deleting Node System State
    DeleteDataSourceConfigNode return code = 0x00000000
    DeleteDataSourceConfigNode Entered
    DeleteDataSourceConfigNode: Deleting Node Bare Metal Recovery
    DeleteDataSourceConfigNode return code = 0x00000000
    AddClientDataSourceConfigNode Entered
    AddClientDataSourceConfigNode: Node Added.
    AddClientDataSourceConfigNode return code = 0x00000000
    AddSystemProtectionDataSourceConfigNode Entered
    AddSystemProtectionDataSourceConfigNode return code = 0x800705af
    UpdatePSDataSourceConfigXML return code = 0x800705af
    CustomAction _UpdatePSDataSourceConfigXML.88BD42D4_8EBE_4E98_B407_81775C1F7E9C returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (1C:70) [11:58:24:494]: User policy value 'DisableRollback' is 0
    MSI (s) (1C:70) [11:58:24:494]: Machine policy value 'DisableRollback' is 0
    Action ended 11:58:24: InstallExecute. Return value 3.

    Is it possible to skip modifying the PSDataSourceConfig.xml file during install? I can modify the paths manually after installation (we used to do this on DPM 2007). Any idea why I'd be getting this error in the first place?


    Jeff Graves, ORCS Web, Inc.
    Tuesday, August 10, 2010 4:06 PM

Answers

  • Please check the following registry key on the proctected server.

    HKLM\SOFTWARE\MICROSOFT\Microsoft Data Protection Manager\Setup

    Does the InstallPath value have the correct path?

    On second thought, if you have this key and you do NOT have any agent installed why not export HKLM\SOFTWARE\MICROSOFT\Microsoft Data Protection Manager to a .reg file and delete it. Also remove any lingering directories in the Program Files directory pertaining to DPM.

    Before you attempt to reinstall you may rename any MSDPM log files in the [windir]\temp directory. Then attempt the agent install. If if faills verify in the log that you are hitting the same issue. Then let me know.

    /Steve


    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, August 11, 2010 5:21 PM
    Moderator

All replies

  • Jeff,

     

    The error code I checked in on was "AddSystemProtectionDataSourceConfigNode return code = 0x800705af." This error coded maps to 0x800705af = ERROR_COMMITMENT_LIMIT: The paging file is too small for this operation to complete.

    Please check the page file configuration on the protected server and try the installation again.

    /Steve


    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, August 11, 2010 1:18 PM
    Moderator
  • Thanks for the follow-up Steve. I found that too when searching for the error code. The server has 16GB of RAM, and has 2 pagefiles. A system managed pagefile on the C: drive of 16GB and a static 24GB pagefile on the D: drive. It is running SQL, so there's not much free RAM (250MB it looks like) - but there's not any paging going on. Could it be because there's 2 pagefiles?


    Jeff Graves, ORCS Web, Inc.
    Wednesday, August 11, 2010 1:24 PM
  • It does not sound like a page file issue. I don't think this is it but go ahead and check and make sure you have free disk space on C: (I am sure you do).

    Let's verify we have WMI connectivity. On the protected server we'll use wbemtest.exe to test.

    • Click the 'Start' button
    • Start -> Run -> wbemtest
    • Click 'Connect' and enter 'root\cimv2' then click 'Connect' again. This should connect without an error.
    • Click 'Connect' and enter 'root\default' then click 'Connect' again. This should connect without an error.

    Let us know if this succeeds or not.

    /Steve


    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, August 11, 2010 3:12 PM
    Moderator
  • Thanks Steve. Plenty of free space on the C: partition (68GB free) - D: as well (395GB free). I can connect to both WMI namespaces without an error.
    Jeff Graves, ORCS Web, Inc.
    Wednesday, August 11, 2010 3:18 PM
  • Please run "vssadmin list writers" on the protected server and post the output.


    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, August 11, 2010 4:15 PM
    Moderator
  • No errors there:

    C:\Users\jeff>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {4f21a541-937f-4c39-ad8b-01c9dd3032da}
       State: [1] Stable
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {2c15885d-4476-4ffa-be95-d046159cc45d}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {9f05e98e-fb74-4548-a98e-952f2a0ef78f}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {814cfd8d-d94a-416b-8da6-77eb7e9b74d7}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {98a0f6ba-6bd2-4563-876c-b0b99f831b20}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {ec410fb2-c867-4d7c-9252-10bd333b6b4b}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {05ad0659-d9c0-46f5-868d-bd05bf9789e1}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {125821b9-73a4-46f4-bb71-4f0ca692ceec}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {9b5cd859-8e01-42a2-9ef7-fcff78b8c342}
       State: [1] Stable
       Last error: No error


    Jeff Graves, ORCS Web, Inc.
    Wednesday, August 11, 2010 4:19 PM
  • Your writers look fine and you can access WMI. I re-read your initial post. What was the issue you had with PSDataSourceConfig.xml in the previous version of DPM?

    /Steve


    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, August 11, 2010 5:09 PM
    Moderator
  • In DPM 2007, we would typically modify the PSDataSourceConfig.xml file after installation to put System State backups on the D: drive. Typically, there would not be sufficient space on the C: partition to store the 15GB system state.

    I am getting this error just trying to perform a standard installation of the DPM 2010 agent on this system. It previously had the DPM 2007 agent, which I uninstalled before installing the new agent. I also tried deleting the MS DPM folder under Program Files to ensure everything was cleaned up before trying to install the new agent.


    Jeff Graves, ORCS Web, Inc.
    Wednesday, August 11, 2010 5:13 PM
  • Please check the following registry key on the proctected server.

    HKLM\SOFTWARE\MICROSOFT\Microsoft Data Protection Manager\Setup

    Does the InstallPath value have the correct path?

    On second thought, if you have this key and you do NOT have any agent installed why not export HKLM\SOFTWARE\MICROSOFT\Microsoft Data Protection Manager to a .reg file and delete it. Also remove any lingering directories in the Program Files directory pertaining to DPM.

    Before you attempt to reinstall you may rename any MSDPM log files in the [windir]\temp directory. Then attempt the agent install. If if faills verify in the log that you are hitting the same issue. Then let me know.

    /Steve


    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, August 11, 2010 5:21 PM
    Moderator
  • Looks like clearing that registry key ended up fixing this. Agent successfully installed this time. Tx for your help!
    Jeff Graves, ORCS Web, Inc.
    Wednesday, August 11, 2010 6:07 PM
  • Woot! Glad I could help.
    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, August 11, 2010 6:52 PM
    Moderator