none
DPM 2007 install fails, error 80070643 RRS feed

  • Question

  • Hi,

    I'm trying to install the DPM 2007 agent on a 2008 server that hosts MSExchange 2007.  The DPM server is 2008 as well.  Both are 64-bit.

    I've tried manually installing the agent, but keep getting the 80070643 error.  The firewalls are down, I've given permissions and shares to everything I can think of.  We have a half-dozen other servers that are protected by the DPM, no problems. 

    From the log, the below seems to be the relevant error message, but I can't find what this psservices is or what to do with it.

    Thanks for your help.

     

    MSI (s) (28:34) [15:12:17:830]: Executing op: ActionStart(Name=_EnablePsServicesRollback,,)

    CreateDummyFileInMTADir: Succeeded

    MSI (s) (28:34) [15:12:17:830]: Executing op: CustomActionSchedule(Action=_EnablePsServicesRollback,ActionType=1345,Source=BinaryData,Target=EnablePsServices,)

    MSI (s) (28:34) [15:12:17:830]: Executing op: ActionStart(Name=_DisablePsServices,,)

    MSI (s) (28:34) [15:12:17:830]: Executing op: CustomActionSchedule(Action=_DisablePsServices,ActionType=3073,Source=BinaryData,Target=StopAndDisablePsServices,)

    MSI (s) (28:44) [15:12:17:846]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI7860.tmp, Entrypoint: StopAndDisablePsServices

    Error in DisableAndStopService. hr=80070424

    StopAndDisablePsServices returned hr = 0x80070424

    MSI (s) (28:34) [15:12:17:862]: User policy value 'DisableRollback' is 0

    MSI (s) (28:34) [15:12:17:862]: Machine policy value 'DisableRollback' is 0

    Action ended 15:12:17: InstallExecute. Return value 3.

    • Moved by MarcReynolds Wednesday, September 29, 2010 12:17 PM (From:Data Protection Manager)
    Wednesday, September 29, 2010 9:46 AM

Answers

  • SUCCESS!  I had to completely uninstall all previous attempts to install the DPM from the protected server and then I could run the install as normal from the DPM server.  To get rid of the installs, I had to use an uninstall utility... I used http://www.revouninstaller.com/, which took about two minutes.

    So, in summary:

    1. I cleared out pending reboots by going here:

    HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress
    HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

    2.  Installed the latest hotfix rollup package for System Center Data Protection Manager 2007: March 29, 2010 (http://support.microsoft.com/kb/979970 )

    3.  Cleared out all previous install attempts using the uninstaller as above.

    Thanks for pointing me in the right direction, Steve.  Appreciate it!

    Fedor

    • Marked as answer by Fedor Steer Tuesday, October 5, 2010 1:52 PM
    Tuesday, October 5, 2010 1:52 PM

All replies

  • The 0x80070643 error could be caused by just about anything. It is an installer error. The two main causes I've seen for this error have been 1) pending reboots from other installs prevented DPM agent installation and 2) NTFS permissions on %windir%\Tasks preventing write access to DPMRA.msi installation process.

    Two things to look at are the following.

    • Clear the pending reboots on the the protected server by rebooting it.
    • Address the permissions to the Tasks directory. The account doing the agent install needs permissions to write in the directory.

    If it is a permissions issue you may use CACLS.exe/ICACLS.exe to view permissions on a working system and then execure the syntax shown below to grant full control permissions to the account(s) necessary:

    • CACLS.exe /E /G <account_name>:F C:\windows\Tasks
    • ICACLS.exe C:\Windows\Tasks /grant <account_name>:(F)

    /Steve

     


    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, September 30, 2010 12:05 PM
    Moderator
  • Thanks Steve, but no luck with those.

    It did remind me, however, that this particular server (only about six months old), has always had trouble with rebooting.  It works flawlessly otherwise, but hangs in a restart and requires a long walk across campus to manually power off/power on.  Where you mentioned that pending reboots may interfere, and from the below part of the install log, could that be a source of the problem?  And if so, where would I look for a solution?  There's a couple of other error codes there, too, that I haven't made progress with.

    Fedor

     

    Property(S): REBOOT = ReallySupress
    Property(S): ProductToBeRegistered = 1
    Property(S): TempFolder = C:\Windows\TEMP\
    Property(S): ProductState = 5
    Property(S): RemoteAdminTS = 1
    Property(S): PATCHNEWPACKAGECODE = {8A986E31-32C8-412F-8371-E6BA461C4409}
    Property(S): PATCHNEWSUMMARYSUBJECT = Microsoft System Center Data Protection Manager Replication Agent Setup v2.0.8793.0
    Property(S): PATCHNEWSUMMARYCOMMENTS = This installer database contains the logic and data required to install Microsoft System Center DPM Protection Agent.
    Property(S): REINSTALL = DPMRA,DPMFLTR
    Property(S): MsiRebootActionScheduled = 1
    MSI (s) (28:34) [15:12:18:002]: Product: Microsoft System Center DPM Protection Agent - Update 'Microsoft System Center DPM Protection Agent Update - KB959605' could not be installed. Error code 1603. Additional information is available in the log file C:\Windows\\Temp\MSDPMAgentInstall.LOG.

    MSI (s) (28:34) [15:12:18:002]: Windows Installer installed an update. Product Name: Microsoft System Center DPM Protection Agent. Product Version: 2.0.8793.0. Product Language: 1033. Update Name: Microsoft System Center DPM Protection Agent Update - KB959605. Installation success or error status: 1603.

    MSI (s) (28:34) [15:12:18:002]: Note: 1: 1729
    MSI (s) (28:34) [15:12:18:002]: Note: 1: 2205 2:  3: Error
    MSI (s) (28:34) [15:12:18:002]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1729
    MSI (s) (28:34) [15:12:18:002]: Note: 1: 2205 2:  3: Error
    MSI (s) (28:34) [15:12:18:002]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
    MSI (s) (28:34) [15:12:18:002]: Product: Microsoft System Center DPM Protection Agent -- Configuration failed.

    MSI (s) (28:34) [15:12:18:002]: Windows Installer reconfigured the product. Product Name: Microsoft System Center DPM Protection Agent. Product Version: 2.0.8793.0. Product Language: 1033. Reconfiguration success or error status: 1603.

    MSI (s) (28:34) [15:12:18:002]: Attempting to delete file C:\Windows\Installer\142eb94b.msp
    MSI (s) (28:34) [15:12:18:002]: Attempting to delete file C:\Windows\Installer\142eb94b.msp
    MSI (s) (28:34) [15:12:18:002]: Unable to delete the file. LastError = 2

    Thursday, September 30, 2010 3:17 PM
  • Fedor,

    Not being an MSI guru the one way I've found to check for pending reboots is to check the following registry keys. If they are not present you probably do not have any pending reboots.
    HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress
    HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

    If you have those keys then you need to reboot. Then try installing the DPMRA agent.

    Hey, one thing I noticed is that your are trying to install the DPM 2007 SP1 version of the agent (2.0.8793.0). If that is the version of DPM you are running I recommend updating to the latest version, 2.0.8864.0. Not only is DPM updated but the agents are as well.
    Description of the hotfix rollup package for System Center Data Protection Manager 2007: March 29, 2010 (http://support.microsoft.com/kb/979970)

    /Steve


    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, September 30, 2010 5:21 PM
    Moderator
  • Sure enough, there were about a dozen pending reboots sitting there that the restarts hadn't cleared up.  I also installed the hotfix, which went smoothly, and I was able to update the existing protected server agents without a problem.

    But still not getting the agent on the problem server.  The error message has changed, so I think we're making progress.

    It now says "Error details: This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package (0x80070663)".  Quite a few errors in the log... not sure where to start.  Can I email you the log?

    Thanks for your help, Steve.

     

     

    Friday, October 1, 2010 2:37 PM
  • The error log is not that long.  I'll just post it.  This is the log from the target server.

    When I compare this log with the one from another 2008 server where the dpm installed successfully, things started to differ where I have it bolded below.  I can't figure out how to get this patch.

    Thanks.

     

    === Verbose logging started: 10/1/2010  10:20:12  Build type: SHIP UNICODE 4.05.6001.00  Calling process: C:\Windows\Microsoft Data Protection Manager\DPM\Agents\AC\2.0.5820.0\dpmac.exe ===
    MSI (c) (10:98) [10:20:12:457]: Resetting cached policy values
    MSI (c) (10:98) [10:20:12:457]: Machine policy value 'Debug' is 0
    MSI (c) (10:98) [10:20:12:457]: ******* RunEngine:
               ******* Product: C:\Windows\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8864.0\dpmra.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (10:98) [10:20:12:457]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (10:98) [10:20:12:457]: Grabbed execution mutex.
    MSI (c) (10:98) [10:20:12:457]: Cloaking enabled.
    MSI (c) (10:98) [10:20:12:457]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (10:98) [10:20:12:473]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (24:7C) [10:20:12:473]: Running installation inside multi-package transaction C:\Windows\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8864.0\dpmra.msi
    MSI (s) (24:7C) [10:20:12:473]: Grabbed execution mutex.
    MSI (s) (24:8C) [10:20:12:473]: Resetting cached policy values
    MSI (s) (24:8C) [10:20:12:473]: Machine policy value 'Debug' is 0
    MSI (s) (24:8C) [10:20:12:473]: ******* RunEngine:
               ******* Product: C:\Windows\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8864.0\dpmra.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (24:8C) [10:20:12:473]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (24:8C) [10:20:12:473]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (24:8C) [10:20:12:473]: End dialog not enabled
    MSI (s) (24:8C) [10:20:12:473]: Original package ==> C:\Windows\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8864.0\dpmra.msi
    MSI (s) (24:8C) [10:20:12:473]: Package we're running from ==> C:\Windows\Installer\1b0f5750.msi
    MSI (s) (24:8C) [10:20:12:473]: APPCOMPAT: looking for appcompat database entry with ProductCode '{72BF00D8-53E0-1539-F523-4347082BCC11}'.
    MSI (s) (24:8C) [10:20:12:473]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (24:8C) [10:20:12:489]: MSCOREE not loaded loading copy from system32
    MSI (s) (24:8C) [10:20:12:489]: Opening existing patch 'C:\Windows\Installer\1b0f5775.msp'.
    MSI (s) (24:8C) [10:20:12:489]: Note: 1: 2203 2: C:\Windows\Installer\1b0f5775.msp 3: -2147286960
    MSI (s) (24:8C) [10:20:12:489]: Opening existing patch 'C:\Windows\Installer\1b0f5775.msp'.
    MSI (s) (24:8C) [10:20:12:489]: Note: 1: 2203 2: C:\Windows\Installer\1b0f5775.msp 3: -2147286960
    MSI (s) (24:8C) [10:20:12:489]: Couldn't find local patch 'C:\Windows\Installer\1b0f5775.msp'. Looking for it at its source.
    MSI (s) (24:8C) [10:20:12:489]: Resolving Patch source.
    MSI (s) (24:8C) [10:20:12:489]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (24:8C) [10:20:12:489]: User policy value 'DisableMedia' is 0
    MSI (s) (24:8C) [10:20:12:489]: Machine policy value 'AllowLockdownMedia' is 0
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Looking for sourcelist for product {0286D30D-18CD-4196-94EC-8837BA10E6E2}
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Adding {0286D30D-18CD-4196-94EC-8837BA10E6E2}; to potential sourcelist list (pcode;disk;relpath).
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Now checking product {0286D30D-18CD-4196-94EC-8837BA10E6E2}
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Media is enabled for product.
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Trying source C:\Windows\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8793.0\.
    MSI (s) (24:8C) [10:20:12:489]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
    MSI (s) (24:8C) [10:20:12:489]: Note: 1: 2203 2: C:\Windows\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8793.0\DPMProtectionAgent_KB959605.msp 3: -2147287037
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (24:8C) [10:20:12:489]: Note: 1: 1706 2: -2147483647 3: DPMProtectionAgent_KB959605.msp
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Processing net source list.
    MSI (s) (24:8C) [10:20:12:489]: Note: 1: 1706 2: -2147483647 3: DPMProtectionAgent_KB959605.msp
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Processing media source list.
    MSI (s) (24:8C) [10:20:12:489]: SOURCEMGMT: Resolved source to: 'DPMProtectionAgent_KB959605.msp'
    MSI (s) (24:8C) [10:20:12:489]: Note: 1: 1314 2: DPMProtectionAgent_KB959605.msp
    MSI (s) (24:8C) [10:20:12:489]: Unable to create a temp copy of patch 'DPMProtectionAgent_KB959605.msp'.
    MSI (s) (24:8C) [10:20:12:489]: Searching provided command line patches for patch code {0286D30D-18CD-4196-94EC-8837BA10E6E2}
    MSI (s) (24:8C) [10:20:12:489]: Note: 1: 1708
    MSI (s) (24:8C) [10:20:12:489]: Product: Microsoft System Center DPM Protection Agent -- Installation failed.

    MSI (s) (24:8C) [10:20:12:489]: Windows Installer installed the product. Product Name: Microsoft System Center DPM Protection Agent. Product Version: 2.0.5820.0. Product Language: 1033. Installation success or error status: 1635.

    MSI (s) (24:8C) [10:20:12:489]: MainEngineThread is returning 1635
    MSI (s) (24:7C) [10:20:12:489]: No System Restore sequence number for this installation.
    This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.
    C:\Windows\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8864.0\dpmra.msi
    MSI (s) (24:7C) [10:20:12:489]: User policy value 'DisableRollback' is 0
    MSI (s) (24:7C) [10:20:12:489]: Machine policy value 'DisableRollback' is 0
    MSI (s) (24:7C) [10:20:12:489]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (24:7C) [10:20:12:489]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (24:7C) [10:20:12:489]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (24:7C) [10:20:12:489]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (24:7C) [10:20:12:489]: Restoring environment variables
    MSI (c) (10:98) [10:20:12:504]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (10:98) [10:20:12:504]: MainEngineThread is returning 1635
    === Verbose logging stopped: 10/1/2010  10:20:12 ===

    Monday, October 4, 2010 6:09 PM
  • Not being an MSI expert by any stretch what I've been able to piece together is this. The SP1 version of the DPM agent was installed on this server at one point. The installer information in the registry points to some locations where the source of the install is supposed to be located. When the installer can't find it it fails the install. Why the installer needs to know about the old version of the agents and all of that I have no idea.

    First of all, on the protected server do you have the following file present? C:\Windows\Installer\1b0f5775.msp? This may be the renamed SP1 agent source file the installer is looking for.

    Secondly, do you have this registry value on the protected server? HKEY_CLASSES_ROOT\Installer\Patches\{0286D30D-18CD-4196-94EC-8837BA10E6E2}? This should be where the installer thinks the source files for the SP1 agent are.

    You may be able to copy the SP1 agent file from the DPM server agents directory and put it where the installer thinks it is. You could copy the this DPMProtectionAgent_KB959605.msp file from the DPM server to the C:\Windows\Installer\1b0f5775.msp file on the protected server the installer works. This MSP file lives on the DPM server in the agents directory (C:\Program Files\Microsoft DPM\DPM\Agents\RA\2.0.8793.0\<x86 0r x64>\1033\), taking into account the archetecture of the protected server.

    /Steve


    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, October 4, 2010 6:59 PM
    Moderator
  • Argh... my brain is getting muddy.  No success.  But I did discover that KB959605 was originally installed back in April and I thought I should uninstall that copy first and try from scratch, but the uninstall failed to find its source.  Couldn't get it out.  So clearly things are corrupted in this whole area.  I don't think I'll be able to make progress until I figure out a way to get rid of that original install.  In the meantime I have copies of copies all over the place and I think I should start fresh in the morning.  Try and clear it all out and start over.
    Monday, October 4, 2010 8:16 PM
  • OK. Please let us know what you find and/or be sure to mark any relevant thread as the answer.

    /Steve


    Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, October 5, 2010 12:50 PM
    Moderator
  • SUCCESS!  I had to completely uninstall all previous attempts to install the DPM from the protected server and then I could run the install as normal from the DPM server.  To get rid of the installs, I had to use an uninstall utility... I used http://www.revouninstaller.com/, which took about two minutes.

    So, in summary:

    1. I cleared out pending reboots by going here:

    HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress
    HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

    2.  Installed the latest hotfix rollup package for System Center Data Protection Manager 2007: March 29, 2010 (http://support.microsoft.com/kb/979970 )

    3.  Cleared out all previous install attempts using the uninstaller as above.

    Thanks for pointing me in the right direction, Steve.  Appreciate it!

    Fedor

    • Marked as answer by Fedor Steer Tuesday, October 5, 2010 1:52 PM
    Tuesday, October 5, 2010 1:52 PM