none
Unable install DPM 2010 Rollup KB 2250444 RRS feed

  • Question

  • Hi all.

    We use DPM 2010 RTM on W2008R2 . When we've tried to install the Rollup KB 2250444 installation always fails. When I look at log files I see the following errors written below.

    Property(S): PATCHNEWPACKAGECODE = {0E04F3AE-75C1-40FD-A961-4C771668E8EE}
    Property(S): PATCHNEWSUMMARYSUBJECT = Microsoft System Center Data Protection Manager Setup v3.0.7696.0
    Property(S): PATCHNEWSUMMARYCOMMENTS = This installer database contains the logic and data required to install Microsoft System Center Data Protection Manager 2010.
    MSI (s) (A0:40) [10:08:14:166]: Product: Microsoft System Center Data Protection Manager 2010 - Update 'Microsoft Data Protection Manager 2010 Update - KB2250444' could not be installed. Error code 1603. Additional information is available in the log file C:\ProgramData\..\DPMLogs\DataProtectionManager-KB2250444.log.

    MSI (s) (A0:40) [10:08:14:167]: Windows Installer installed an update. Product Name: Microsoft System Center Data Protection Manager 2010. Product Version: 3.0.7696.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: Microsoft Data Protection Manager 2010 Update - KB2250444. Installation success or error status: 1603.

    MSI (s) (A0:40) [10:08:14:168]: Note: 1: 1729
    MSI (s) (A0:40) [10:08:14:168]: Transforming table Error.

    MSI (s) (A0:40) [10:08:14:169]: Transforming table Error.

    MSI (s) (A0:40) [10:08:14:169]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (A0:40) [10:08:14:170]: Transforming table Error.

    MSI (s) (A0:40) [10:08:14:170]: Transforming table Error.

    MSI (s) (A0:40) [10:08:14:170]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (A0:40) [10:08:14:170]: Product: Microsoft System Center Data Protection Manager 2010 -- Configuration failed.

    MSI (s) (A0:40) [10:08:14:171]: Windows Installer reconfigured the product. Product Name: Microsoft System Center Data Protection Manager 2010. Product Version: 3.0.7696.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1603.

    MSI (s) (A0:40) [10:08:14:175]: Attempting to delete file C:\Windows\Installer\4291acc3.msp
    MSI (s) (A0:40) [10:08:14:249]: Deferring clean up of packages/files, if any exist
    MSI (s) (A0:40) [10:08:14:249]: Attempting to delete file C:\Windows\Installer\4291acc3.msp
    MSI (s) (A0:40) [10:08:14:249]: Unable to delete the file outside of the engine. LastError = 2
    MSI (s) (A0:40) [10:08:14:249]: MainEngineThread is returning 1603
    MSI (s) (A0:B0) [10:08:14:259]: RESTART MANAGER: Session closed.
    MSI (s) (A0:B0) [10:08:14:259]: No System Restore sequence number for this installation.
    === Logging stopped: 12/20/2010  10:08:14 ===
    MSI (s) (A0:B0) [10:08:14:450]: User policy value 'DisableRollback' is 0
    MSI (s) (A0:B0) [10:08:14:450]: Machine policy value 'DisableRollback' is 0
    MSI (s) (A0:B0) [10:08:14:450]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (A0:B0) [10:08:14:451]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (A0:B0) [10:08:14:451]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (A0:B0) [10:08:14:452]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (A0:B0) [10:08:14:453]: Restoring environment variables
    MSI (s) (A0:B0) [10:08:14:454]: Destroying RemoteAPI object.
    MSI (s) (A0:34) [10:08:14:454]: Custom Action Manager thread ending.
    MSI (c) (4C:1C) [10:08:14:477]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (4C:1C) [10:08:14:478]: MainEngineThread is returning 1603
    MSI (c) (4C:80) [10:08:14:486]: RESTART MANAGER: Session closed.
    === Verbose logging stopped: 12/20/2010  10:08:14 ===

    Monday, December 20, 2010 8:19 AM

Answers

  • Hi

    Got a similar failure. I canceld all my jobs and rebooted the DPM server and tried it again, it sovled my problem.

     

    BR

    Robert Hedblom



    Check out my DPM blog @ http://robertanddpm.blogspot.com

    Monday, December 20, 2010 9:08 PM
    Moderator

All replies

  • Hi

    Got a similar failure. I canceld all my jobs and rebooted the DPM server and tried it again, it sovled my problem.

     

    BR

    Robert Hedblom



    Check out my DPM blog @ http://robertanddpm.blogspot.com

    Monday, December 20, 2010 9:08 PM
    Moderator
  • I'm getting the same errors, but have no pending jobs. I even tried stopping the MSDPM service, but no luck. Any suggestionss?
    Wednesday, June 15, 2011 1:47 PM
  • Dont want to start a new topic on this

    I am also having issues installing this.  No jobs running, stopped all services.

    Tried the cmd line to skip the backup, still no joy.

     

    Friday, July 8, 2011 8:30 AM
  • I am having the same issue.  Adio82 - did you ever fix your issue? 

    Thanks

     

    Wednesday, August 3, 2011 4:45 PM
  • I have this issue. After several tests I found that the DPM AccessManager Service is terminated before installing the update. After resolving the problem of the service, the installation problem resolved.

     


    • Edited by R.Alikhani Thursday, September 8, 2011 7:23 AM
    • Proposed as answer by R.Alikhani Thursday, September 15, 2011 2:10 PM
    Thursday, September 8, 2011 7:22 AM
  • I received the same error as noted in the log included by the OP.  The DPMRA service was stuck in a state of "stopping".  I manually forced it to stop via Task Manager at which point the install went through fine.  Hope this helps...
    Monday, September 26, 2011 8:00 PM
  • im afraid i didnt
    Tuesday, July 10, 2012 9:51 AM
  • I wanted to share this issue I’ve have for a few months. We use 2 DPM 2010 on Server 2008 R2 running SP1. I noticed that I had missed the Update Rollup’s for DPM since RU1 on one server. I then started to update first with RU6 since that was the most recent one. The update would fail and would see error 1603 in the logs. Did the usual troubleshooting, tried extracting the update, google’d for hours trying to find an answer. Finally came across an event on the logs with

    “error in disableandstopservice. hr=80070424”

    The event showed its face when the update was trying to open service handle DPMAC and would fail with access denied. I found that the DPMAC was the DPM agent Coordinator, and it would cause the Update to fail when DPM tried to disable the service temporarily while it was being patched. I then started to look at the obvious, the actual service that may have been corrupted. Come to my surprise, the service was not even there! I then tried to find was to reinstall DPM without having to back up the database, uninstall DPM, reinstall it and restore the database. So… I created a new service using the SC command. I simply made it easier on myself by comparing the services from my other server and copied them over.

    Here it is:

    1. Verify the service is actually missing by using the SC command to query the service.
      1. Open  CMD and type SC query DPMAC and you should get something like

    SERVICE_NAME: dpmac

    TYPE               : 10  WIN32_OWN_PROCESS

    STATE              : 1  STOPPED

    WIN32_EXIT_CODE    : 0  (0x0)

    SERVICE_EXIT_CODE  : 0  (0x0)

    CHECKPOINT         : 0x0

    WAIT_HINT          : 0x0

    1. If you don’t get that result you can always open the “services.msc” console and look for the “DPM Agent Coordinator Service”. If it’s not there, you can proceed with the next steps.
      1. In the Command prompt, type SC create DPMAC binPath <root installation folder of your DPM installation>\DPM\bin\dpmac.exe

    (This creates the basic service, you still need to go in and edit some properties.)

    1. Open REGEDIT and browse to “HKLM\SYSTEM\CurrentControllSet\Serivces\DPMAC”, right click and create a new Mutly-String Value, and name it “DependOnService”, then enter the value “RpcSs”.
    2. Create a new String Value and name it “DisplayName” and enter value “DPM Agent Coordinator” then create another String Value and name it “Description”, and enter value “Manages the installation, uninstallation, and upgrade of protection agents to remote servers.” As its value.
    3. Open the value “Image path” and add “-DPMAC” at the end of the path. Is should look something like this

                       "F:\Program Files\Microsoft DPM\DPM\bin\dpmac.exe" -DPMAC

    Now you should be able to open the services.msc console and look for the “DPM agent Coordinator” service. It should be set to manually start up, and set logon as “local system”

    (Note: you might find the service listed as “DPMAC” until you restart the machine.)

    Now the update should install just fine.

    PS: I also found that this fixed and issue with client installation and update issues.

    • Proposed as answer by Dan1C Friday, May 17, 2013 7:39 PM
    Friday, May 17, 2013 7:38 PM