none
Can't install DPM 2010 error ID 4387 RRS feed

  • Question

  • I'm having massive problems installing DPM 2010 on a server that previously had DPM 2007 installed.

    DPM2007 stopped working and after a little bit of help from Microsoft we decided to dump it and go to 2010. Upgrading wouldn't work so we tried to uninstall what we could, but removing DPM 2007 and SQL 2005 was a complete nightmare including manually removing files and registry entries.

    Anyway, we're trying to install on what appears to be a clean server now. My own preference would be to wipe the OS and start again but the client is unwilling to do that at the moment.

    I'm following the instructions on this site:

    http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/backup-recovery/installing-data-protection-manager-dpm-2010-Part1.html

    SQL 2008 installed without any problems and I upgraded it to SP1. I then began the DPM 2010 install, hit the "install Data Protection Manager" link, accept the terms and conditions and watch the "Please wait while setup is copying temporary files" box with progress bar.

    I don't get to the "Data Protection Manager Setup Wizard" screen instead a box pops up saying:

    "An unexpected error occurred during the installation.

    For details, check the DPM Setup error logs.

    ID: 4387"

    Now, I believe that the installation log files are supposed to be in C:\DPMLogs but that folder does not exist and I've search all drives on the server for the DPMSetup.log file but that is not on the system.

    Microsoft's own "DPM 2010 error code catalog" doesn't even list 4387 as a possibility.

    Can anyone help with this?

    Thanks

    Kieran.

     

    Friday, September 10, 2010 2:13 PM

Answers

  • I had to rebuild the server which was disappointing.

     

    None of the uninstall switches worked.

     

    • Marked as answer by Kieran Walsh Wednesday, September 29, 2010 9:49 AM
    Wednesday, September 29, 2010 9:49 AM

All replies

  • Hi,

    Are you using a Remote SQL server 2008 instance ?   If not, why did you pre-install SQL Server 2008 locally - if you manually installed SQL from the DPM 2010 installation CD, and did not enter a valid license key, then the sql will expire in 180 days, so I would un-install SQL SQL 2008 and just let DPM install it locally. 

     


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, September 10, 2010 8:02 PM
    Moderator
  • Nope, it's a local install, I didn't think that that would be a problem. It was installed with a serial at the time.

    To be honest, I've done so many installs/uninstalls over the last few days, I've basically tried every combination. I'll remove SQL 2008 for now and try the DPM 2010 install again.

    Thanks

    Kieran

     

    Friday, September 10, 2010 9:19 PM
  • Ok, I've uninstalled SQL 2008, rebooted and tried the DPm install again. Same problem and error message I'm afraid.

    Also, there are no error messages in the event log after the failure.

     

    Friday, September 10, 2010 9:49 PM
  • Just for grins, just to be sure no DPM 2007 reminents are left behind, try running the following from the DPM 2007 Installation cd.

     

    Run the following from an elevated command prompt:

    Msiexec /x <path of msdpm.msi> BOOTSTRAPPED=1 /l*v c:\dpmlogs\uninstall.log.

    NOTE: Msdpm.msi will be present in CDlayout\DPM2007\msi folder of the installation media.

     

    Expect errrors since you already removed DPM 2007, but it may locate and remove something you missed.


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    • Proposed as answer by Parag Agrawal Wednesday, September 29, 2010 8:56 AM
    • Unproposed as answer by Kieran Walsh Wednesday, September 29, 2010 9:40 AM
    Friday, September 10, 2010 10:07 PM
    Moderator
  • Cheers Mike,

    After a reboot the server showed DPM 2007 in appwiz.cpl again - I guess that I'm never going to get rid of it :)

    So, I was glad to get your uninstall switch. The uninstall failed, but perhaps you may be able to understand why. The log file is 115KB in size so I can't post the whole thing here, but I'll post parts  of it and any bits with errors.

    Cheers

    Kieran

    -------------------------

    === Verbose logging started: 11/09/2010  20:28:38  Build type: SHIP UNICODE 4.05.6002.00  Calling process: C:\Windows\system32\msiexec.exe ===
    MSI (c) (B4:E4) [20:28:38:468]: Resetting cached policy values
    MSI (c) (B4:E4) [20:28:38:468]: Machine policy value 'Debug' is 0
    MSI (c) (B4:E4) [20:28:38:468]: ******* RunEngine:
               ******* Product: d:\Software Download\System Centre DPM 64bit\DPM2007\msi\msdpm.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (B4:E4) [20:28:38:484]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (B4:E4) [20:28:38:484]: Grabbed execution mutex.
    MSI (c) (B4:E4) [20:28:38:531]: Cloaking enabled.
    MSI (c) (B4:E4) [20:28:38:531]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (B4:E4) [20:28:38:546]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (24:E4) [20:28:38:578]: Running installation inside multi-package transaction d:\Software Download\System Centre DPM 64bit\DPM2007\msi\msdpm.msi
    MSI (s) (24:E4) [20:28:38:578]: Grabbed execution mutex.
    MSI (s) (24:6C) [20:28:38:578]: Resetting cached policy values
    MSI (s) (24:6C) [20:28:38:578]: Machine policy value 'Debug' is 0
    MSI (s) (24:6C) [20:28:38:578]: ******* RunEngine:
               ******* Product: d:\Software Download\System Centre DPM 64bit\DPM2007\msi\msdpm.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (24:6C) [20:28:38:578]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (24:6C) [20:28:38:718]: Machine policy value 'LimitSystemRestoreCheckpointing' is 0
    MSI (s) (24:6C) [20:28:38:718]: Note: 1: 1717 2: Microsoft System Center Data Protection Manager 2007
    MSI (s) (24:6C) [20:28:38:718]: Note: 1: 2205 2:  3: Error
    MSI (s) (24:6C) [20:28:38:718]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1717
    MSI (s) (24:6C) [20:28:38:718]: Calling SRSetRestorePoint API. dwRestorePtType: 1, dwEventType: 102, llSequenceNumber: 0, szDescription: "Removed Microsoft System Center Data Protection Manager 2007".
    MSI (s) (24:6C) [20:28:38:718]: The call to SRSetRestorePoint API failed. Returned status: 0. GetLastError() returned: 127
    MSI (s) (24:6C) [20:28:38:718]: End dialog not enabled
    MSI (s) (24:6C) [20:28:38:718]: Original package ==> d:\Software Download\System Centre DPM 64bit\DPM2007\msi\msdpm.msi
    MSI (s) (24:6C) [20:28:38:718]: Package we're running from ==> C:\Windows\Installer\1eba49.msi
    MSI (s) (24:6C) [20:28:38:750]: APPCOMPAT: looking for appcompat database entry with ProductCode '{67750D8C-C240-4B66-B2B1-EE0BAA7FD904}'.
    MSI (s) (24:6C) [20:28:38:750]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (24:6C) [20:28:39:109]: MSCOREE not loaded loading copy from system32
    MSI (s) (24:6C) [20:28:39:109]: Opening existing patch 'C:\Windows\Installer\1ebc5f.msp'.
    MSI (s) (24:6C) [20:28:39:578]: SequencePatches starts. Product code: {67750D8C-C240-4B66-B2B1-EE0BAA7FD904}, Product version: 2.0.5820.0, Upgrade code: {0BEE7F6A-CE2A-A5CF-FFEB-8E0F8A8CDE75}, Product language 1033
    MSI (s) (24:6C) [20:28:39:593]: SequencePatches returns success.
    MSI (s) (24:6C) [20:28:39:593]: Final Patch Application Order:
    MSI (s) (24:6C) [20:28:39:593]: {0286D30D-18CD-4196-94EC-8837BA10E6E2} -
    MSI (s) (24:6C) [20:28:39:593]: Machine policy value 'DisablePatch' is 0
    MSI (s) (24:6C) [20:28:39:593]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (24:6C) [20:28:39:593]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (24:6C) [20:28:39:593]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (24:6C) [20:28:39:609]: Looking for patch transform: DPMV2RTMBaseToDPMKB959605
    MSI (s) (24:6C) [20:28:39:625]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038
    MSI (s) (24:6C) [20:28:39:625]: Note: 1: 2262 2: LockPermissions 3: -2147287038
    MSI (s) (24:6C) [20:28:39:625]: Note: 1: 2262 2: AppSearch 3: -2147287038
    MSI (s) (24:6C) [20:28:39:625]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
    MSI (s) (24:6C) [20:28:39:625]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
    MSI (s) (24:6C) [20:28:39:656]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: ServiceInstall 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: DuplicateFile 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: Environment 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: Shortcut 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: Icon 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: RegLocator 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: Signature 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: ServiceControl 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: Feature 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: CustomAction 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: Upgrade 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: Registry 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: CreateFolder 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: Directory 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: LockPermissions 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: AppSearch 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: LaunchCondition 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: Binary 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
    MSI (s) (24:6C) [20:28:39:671]: Note: 1: 2262 2: FeatureComponents 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: Component 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: _Validation 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: ModuleSignature 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: ModuleComponents 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: ServiceInstall 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: DuplicateFile 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: Environment 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: Shortcut 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: Icon 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: RegLocator 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: Signature 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: ServiceControl 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: Patch 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: MsiPatchHeaders 3: -2147287038
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2205 2:  3: Patch
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2228 2:  3: Patch 4: CREATE TABLE `Patch` ( `File_` CHAR(72) NOT NULL, `Sequence` INTEGER NOT NULL, `PatchSize` LONG NOT NULL, `Attributes` INTEGER NOT NULL, `Header` OBJECT, `StreamRef_` CHAR(72)  PRIMARY KEY `File_`, `Sequence` )
    MSI (s) (24:6C) [20:28:39:687]: Note: 1: 2262 2: Patch 3: -2147287038
    MSI (s) (24:6C) [20:28:39:703]: Note: 1: 2715 2: F_addSCRSG.ps1
    MSI (s) (24:6C) [20:28:39:703]: Note: 1: 2715 2: F_removeSCRSG.ps1


    MSI (s) (24:6C) [20:28:39:734]: Adding new sources is allowed.
    MSI (s) (24:6C) [20:28:39:734]: Package name retrieved from configuration data: 'msdpm.msi'
    MSI (s) (24:6C) [20:28:39:734]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
    MSI (s) (24:6C) [20:28:39:734]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (24:6C) [20:28:39:734]: Transforming table Error.

    MSI (s) (24:6C) [20:28:39:734]: Transforming table Error.

    MSI (s) (24:6C) [20:28:39:734]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (24:6C) [20:28:39:750]: Note: 1: 2262 2: AdminProperties 3: -2147287038
    MSI (s) (24:6C) [20:28:39:750]: Machine policy value 'DisableMsi' is 1
    MSI (s) (24:6C) [20:28:39:750]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (s) (24:6C) [20:28:39:750]: User policy value 'AlwaysInstallElevated' is 0
    MSI (s) (24:6C) [20:28:39:750]: Product {67750D8C-C240-4B66-B2B1-EE0BAA7FD904} is admin assigned: LocalSystem owns the publish key.
    MSI (s) (24:6C) [20:28:39:750]: Product {67750D8C-C240-4B66-B2B1-EE0BAA7FD904} is managed.
    MSI (s) (24:6C) [20:28:39:750]: Running product '{67750D8C-C240-4B66-B2B1-EE0BAA7FD904}' with elevated privileges: Product is assigned.
    MSI (s) (24:6C) [20:28:39:750]: PROPERTY CHANGE: Adding BOOTSTRAPPED property. Its value is '1'.
    MSI (s) (24:6C) [20:28:39:750]: PROPERTY CHANGE: Adding REMOVE property. Its value is 'ALL'.
    MSI (s) (24:6C) [20:28:39:750]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Users\myusername'.
    MSI (s) (24:6C) [20:28:39:750]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '2'.
    MSI (s) (24:6C) [20:28:39:750]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '2484'.
    MSI (s) (24:6C) [20:28:39:750]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
    MSI (s) (24:6C) [20:28:39:765]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '5e2ce970311c3447bdc64c984b07a607'.
    MSI (s) (24:6C) [20:28:39:765]: RESTART MANAGER: Session opened.

    Property(S): CLIENTUILEVEL = 2
    Property(S): CURRENTDIRECTORY = C:\Users\myusername
    Property(S): REMOVE = ALL
    Property(S): BOOTSTRAPPED = 1
    Property(S): ProductToBeRegistered = 1
    Property(S): CostingComplete = 0
    Property(S): PATCHNEWPACKAGECODE = {BDE31B8F-FE05-4C57-A583-CA21D4F7CF46}
    Property(S): PATCHNEWSUMMARYSUBJECT = Microsoft System Center Data Protection Manager Setup v2.0.8793.0
    Property(S): PATCHNEWSUMMARYCOMMENTS = This installer database contains the logic and data required to install Microsoft System Center Data Protection Manager 2007.
    MSI (s) (24:6C) [20:28:40:250]: Note: 1: 1725
    MSI (s) (24:6C) [20:28:40:250]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (24:6C) [20:28:40:250]: Transforming table Error.

    MSI (s) (24:6C) [20:28:40:250]: Transforming table Error.

    MSI (s) (24:6C) [20:28:40:250]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (24:6C) [20:28:40:250]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (24:6C) [20:28:40:250]: Transforming table Error.

    MSI (s) (24:6C) [20:28:40:250]: Transforming table Error.

    MSI (s) (24:6C) [20:28:40:250]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (24:6C) [20:28:40:265]: Product: Microsoft System Center Data Protection Manager 2007 -- Removal failed.

    MSI (s) (24:6C) [20:28:40:265]: Windows Installer removed the product. Product Name: Microsoft System Center Data Protection Manager 2007. Product Version: 2.0.8793.0. Product Language: 1033. Removal success or error status: 1603.

    MSI (s) (24:6C) [20:28:40:265]: Deferring clean up of packages/files, if any exist
    MSI (s) (24:6C) [20:28:40:265]: MainEngineThread is returning 1603
    MSI (s) (24:E4) [20:28:40:265]: RESTART MANAGER: Session closed.
    MSI (s) (24:E4) [20:28:40:265]: No System Restore sequence number for this installation.
    === Logging stopped: 11/09/2010  20:28:40 ===
    MSI (s) (24:E4) [20:28:40:265]: User policy value 'DisableRollback' is 0
    MSI (s) (24:E4) [20:28:40:265]: Machine policy value 'DisableRollback' is 0
    MSI (s) (24:E4) [20:28:40:265]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (24:E4) [20:28:40:265]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (24:E4) [20:28:40:265]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (24:E4) [20:28:40:265]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (24:E4) [20:28:40:265]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (24:E4) [20:28:40:265]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (24:E4) [20:28:40:265]: Restoring environment variables
    MSI (s) (24:E4) [20:28:40:265]: Destroying RemoteAPI object.
    MSI (s) (24:B0) [20:28:40:265]: Custom Action Manager thread ending.
    MSI (c) (B4:E4) [20:28:40:265]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (B4:E4) [20:28:40:265]: MainEngineThread is returning 1603
    === Verbose logging stopped: 11/09/2010  20:28:40 ===
    Saturday, September 11, 2010 7:45 PM
  •                          =@

     

     T U M B L E W E E D

     

     

     

    Friday, September 17, 2010 3:54 PM
  • And that was that, another case solved by the Microsoft Support team!

     

    No, wait...

     

    Friday, September 17, 2010 3:55 PM
  • And a server rebuild is in order unless you want to persue this further in a support case, it's going to take some debugging which cannot be achieved in a forum setting.
    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, September 17, 2010 5:25 PM
    Moderator
  • Hi,

    Could you check if uninstall of DPM 2007 setup works by launching DPM 2007 setup.exe


    -- Thanks Venkata Praveen[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Sunday, September 19, 2010 11:18 AM
  • I had to rebuild the server which was disappointing.

     

    None of the uninstall switches worked.

     

    • Marked as answer by Kieran Walsh Wednesday, September 29, 2010 9:49 AM
    Wednesday, September 29, 2010 9:49 AM
  • Make sure the DPMR$SERVERNAME account has appropriate permissions.

    not sure what the fix is but I gave it admin rights during install and it installed for me.

     

    also I had to create a new domain account, i called it "DPMdmin", for reporting to work right. for email reporting to work you have to use DPMAdmin to start both reporting and sql server so might as well do this during install and change sql to start as that.
    • Proposed as answer by z_lives Wednesday, February 16, 2011 5:08 PM
    Wednesday, February 16, 2011 5:08 PM
  • This is what worked for me:

    You will need to rebuild your wmi repository and re-run the setup.


    Follow these steps:
    1. Go to elevated command prompt.
    2. Stop the Windows Management service using "net stop winmgmt".
    3. Using Windows Explorer, rename the folder
    %windir%\System32\Wbem\Repository. (For example,
    %windir%\System32\Wbem\Repository_bad). %windir% represents the path to the
    Windows directory, which is typically C:\Windows.
    4. Start the windows management service using "net start winmgmt".
    5. rebuild the repository using "winmgmt /salvagerepository".

    Monday, April 25, 2011 8:13 PM