none
System Center 2012 R2 Data Protection Manager UR2 - UR6 cannot be installed RRS feed

  • Question

  • Hey Guys,

    now I'm trying since a few weeks to install and run DPM. Started with some specification issues and now I'm ended in running DPM with a remote SQL Database.

    We are using SQL2014, so I've just installed SQL2012 SP1 as evaluation to apply all the UR Updates and move the DB to the SQL2014 later on.

    Well, UR1 wasn't any kind of a problem. But I can't apply UR2, UR3, UR4, UR5 or UR6.

    SQL Server log: everything is fine, DB was backed up (as I can see on the time stamp as well), no user login problems, nothing.

    All the DPM Install-Log tells me is: Error 1603 and that could nearly be everything as my research is so far (checking everything since this morning...).

    Maybe one of you guys know how to do the trick - here is my DPM Install log:

    MSI (s) (E8:64) [16:57:41:541]: Produkt: Microsoft System Center 2012 R2 Data Protection Manager - Update "Microsoft System Center 2012 R2 Data Protection Manager Update - KB2963543" konnte nicht installiert werden. Fehlercode 1603. Weitere Informationen sind in der Protokolldatei C:\Program Files\Microsoft System Center 2012 R2\DPM\DPMLogs\DataProtectionManager-KB2963543.log enthalten.

    MSI (s) (E8:64) [16:57:41:541]: Ein Update wurde durch Windows Installer installiert. Produktname: Microsoft System Center 2012 R2 Data Protection Manager. Produktversion: 4.2.1205.0. Produktsprache: 1033. Hersteller: Microsoft Corporation. Updatename: Microsoft System Center 2012 R2 Data Protection Manager Update - KB2963543. Erfolg- bzw. Fehlerstatus der Installation: 1603.

    MSI (s) (E8:64) [16:57:41:541]: Note: 1: 1729 
    MSI (s) (E8:64) [16:57:41:541]: Transforming table Error.

    MSI (s) (E8:64) [16:57:41:541]: Transforming table Error.

    MSI (s) (E8:64) [16:57:41:541]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (E8:64) [16:57:41:541]: Transforming table Error.

    MSI (s) (E8:64) [16:57:41:541]: Transforming table Error.

    MSI (s) (E8:64) [16:57:41:541]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (E8:64) [16:57:41:541]: Transforming table Error.

    MSI (s) (E8:64) [16:57:41:541]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (E8:64) [16:57:41:541]: Transforming table Error.

    MSI (s) (E8:64) [16:57:41:541]: Transforming table Error.

    MSI (s) (E8:64) [16:57:41:541]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (E8:64) [16:57:41:541]: Transforming table Error.

    MSI (s) (E8:64) [16:57:41:541]: Transforming table Error.

    MSI (s) (E8:64) [16:57:41:541]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (E8:64) [16:57:41:541]: Transforming table Error.

    MSI (s) (E8:64) [16:57:41:541]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (E8:64) [16:57:41:541]: Product: Microsoft System Center 2012 R2 Data Protection Manager -- Configuration failed.

    MSI (s) (E8:64) [16:57:41:541]: Das Produkt wurde durch Windows Installer neu konfiguriert. Produktname: Microsoft System Center 2012 R2 Data Protection Manager. Produktversion: 4.2.1205.0. Produktsprache: 1033. Hersteller: Microsoft Corporation. Erfolg- bzw. Fehlerstatus der neuen Konfiguration: 1603.

    MSI (s) (E8:64) [16:57:41:541]: Attempting to delete file c:\Windows\Installer\26beaf.msp
    MSI (s) (E8:64) [16:57:41:635]: Deferring clean up of packages/files, if any exist
    MSI (s) (E8:64) [16:57:41:635]: Attempting to delete file c:\Windows\Installer\26beaf.msp
    MSI (s) (E8:64) [16:57:41:635]: Unable to delete the file outside of the engine. LastError = 2
    MSI (s) (E8:64) [16:57:41:635]: MainEngineThread is returning 1603
    MSI (s) (E8:B0) [16:57:41:635]: RESTART MANAGER: Session closed.
    MSI (s) (E8:B0) [16:57:41:635]: No System Restore sequence number for this installation.
    === Logging stopped: 25.06.2015  16:57:41 ===
    MSI (s) (E8:B0) [16:57:41:650]: User policy value 'DisableRollback' is 0
    MSI (s) (E8:B0) [16:57:41:650]: Machine policy value 'DisableRollback' is 0
    MSI (s) (E8:B0) [16:57:41:650]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (E8:B0) [16:57:41:650]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (E8:B0) [16:57:41:650]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (E8:B0) [16:57:41:650]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (E8:B0) [16:57:41:650]: Destroying RemoteAPI object.
    MSI (s) (E8:9C) [16:57:41:650]: Custom Action Manager thread ending.
    MSI (c) (90:E8) [16:57:41:666]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (90:E8) [16:57:41:666]: MainEngineThread is returning 1603
    MSI (c) (90:FC) [16:57:41:666]: RESTART MANAGER: Session closed.
    === Verbose logging stopped: 25.06.2015  16:57:41 ===

    Cheers

    Thursday, June 25, 2015 3:07 PM

All replies

  • Hi,

    Yes - finding the real error in the update rollup logs can be tricky.

    Most common is caused by service control manager having trouble stopping or starting DPM services in a timely manner. 

    Example to search for:

    1: PatchCA: 2: start dpmwriter returned hr=8007041d
    1: PatchCA: 2: Error in EnableAndStartService. hr=8007041d
    1: PatchCA: 2: EnableDpmServices returned hr 0x8007041d
    CustomAction _EnableServices.97DDF5B3_3770_4C3E_8673_52BD081E1EFD returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (14:28) [14:00:17:193]: User policy value 'DisableRollback' is 0
    MSI (s) (14:28) [14:00:17:193]: Machine policy value 'DisableRollback' is 0
    Action ended 14:00:17: InstallExecute. Return value 3.

    If you find similar error then the below will resolve that issue.

    When a service starts, the service communicates to the Service Control Manager how long the service must have to start (the time-out period for the service). If the Service Control Manager does not receive a "service started" notice from the service within this time-out period, the Service Control Manager terminates the process that hosts the service. This time-out period is typically less than 30 seconds. If you do not adjust this time-out period, the Service Control Manager ends the process.
     
    To adjust this time-out period, follow these steps:

    Event ID 7011 — Basic Service Operations
    http://technet.microsoft.com/en-us/library/dd349371(v=WS.10).aspx


    a.  In Registry Editor, locate, and then right-click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control 

    b.  Point to New , and then click DWORD Value.
    c.  Enter:  ServicesPipeTimeout  and then press ENTER. 
    d.  Right-click the ServicesPipeTimeout registry entry that you created in step c, and then click Modify . The Edit DWORD Value dialog box appears. 
    e.  In the Value data text box, type 300000 decimal, and then click OK

    Note TimeoutPeriod is a placeholder for the value of the time-out period (in milliseconds) that you want to set for the service. For example, if you want to set the time-out period to be 5 minutes (300000 milliseconds), type 300000.
     
    f.  Restart the computer. You must restart the computer for Service Control Manager to apply this change. 

    If you did not find that specific error code, then search the log for the below string, and then look above that line for the real error.

        InstallExecute. Return value 3.

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Thursday, June 25, 2015 11:00 PM
    Moderator
  • Hey Mike,

    thanks for your reply and please pardon me for my late answer, but I was on vacation.

    After trying to find 0x8007041d without success, I went up for your second possibility "InstallExecute. Return value 3."

    And now this is what I've found:

    ExecuteSqlStrings:  Error 0x80040e14: failed to execute SQL string, error: Ungültiger Spaltenname 'BackupTime'., SQL key: sqlscript_KB2963543Fix.sql SQL string: CREATE PROCEDURE . (
        @smstatsID guid,
        @startTime datetime,
        @endTime datetime)
    AS

        DECLARE @error int
        DECLARE @numDays int
        DECLARE @tempRPStatus TABLE
        (
            DatasourceName ,
            ServerName nvarchar(400),
            BackupTime datetime,
            BackupDate datetime,
            ProtectionGroupName NVARCHAR(64),
            DiskRecoveryPointPresent BIT,
            TapeRecoveryPointPresent BIT,
            CloudRecoveryPointPresent BIT,
            DataSourceId ,
            PGSLA int,
            Row_num 
        )
        -- compute and insert statistics

        SELECT @numDays = DATEDIFF( DAY, @startTime, @endTime)

        IF(EXISTS(SELECT * FROM dbo.tbl_SM_SLA_Trend
                WHERE SMStatsID = @smstatsID))
         GOTO  SkipComputation

        INSERT INTO @tempRPStatus EXEC dbo.prc_Reporting_RecoveryPointStatus @endTime, 0, @numDays

        INSERT INTO dbo.tbl_SM_SLA_Trend (
            SMStatsId,
            DatasourceId,
            DatasourceName,
            ServerName,
            ProtectionGroupName,
            BackupTime,
            DiskRecoveryPointAvailable,
            TapeRecoveryPointAvailable,
            CloudRecoveryPointAvailable,
            SLA)
        SELECT
            @smstatsID,
            DataSourceId,
            DatasourceName,
            ServerName,
            ProtectionGroupName,
            BackupTime,
            DiskRecoveryPointPresent,
            TapeRecoveryPointPresent,
            CloudRecoveryPointPresent,
            PGSLA
        FROM @tempRPStatus

    SkipComputation:
        SET @error = @@ERROR
        RETURN @error
    MSI (s) (E8!A4) [16:57:25:756]: Transforming table Error.
    MSI (s) (E8!A4) [16:57:25:756]: Transforming table Error.
    MSI (s) (E8!A4) [16:57:25:756]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (E8!A4) [16:57:25:756]: Transforming table Error.
    MSI (s) (E8!A4) [16:57:25:756]: Transforming table Error.
    MSI (s) (E8!A4) [16:57:25:756]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (E8!A4) [16:57:25:756]: Transforming table Error.
    MSI (s) (E8!A4) [16:57:25:756]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (E8!A4) [16:57:25:756]: 
    CustomAction ExecuteSqlStrings returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (E8:64) [16:57:25:881]: Note: 1: 2265 2:  3: -2147287035 
    MSI (s) (E8:64) [16:57:25:881]: User policy value 'DisableRollback' is 0
    MSI (s) (E8:64) [16:57:25:881]: Machine policy value 'DisableRollback' is 0
    Action ended 16:57:25: InstallExecute. Return value 3.

    Sorry for the German error message:

    ExecuteSqlStrings:  Error 0x80040e14: failed to execute SQL string, error: Ung??ltiger Spaltenname 'BackupTime'., SQL key: sqlscript_KB2963543Fix.sql SQL string: CREATE PROCEDURE . (

    This one means: "[...]Invalid column name 'BackupTime'[...]"

    So the actual Error code is 1603. On that topic I just find general install errors. Any ideas?

    Cheers

    Tuesday, July 7, 2015 1:12 PM
  • Hi, Not sure why that SQL scripts is trying to add backupTime to the dbo.tbl_SM_SLA_Trend table because my UR6 dpmdb has CreationTime in that table.

    INSERT INTO dbo.tbl_SM_SLA_Trend (
            SMStatsId,
            DatasourceId,
            DatasourceName,
            ServerName,
            ProtectionGroupName,
            BackupTime,
            DiskRecoveryPointAvailable,
            TapeRecoveryPointAvailable,         CloudRecoveryPointAvailable,
            SLA)
     
    What does your dbo.tbl_SM_SLA_Trend table show ?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, July 7, 2015 11:14 PM
    Moderator
  • Hey Mike,

    thanks again for your reply!

    That was what I've wondered about, too.

    Here are the columns from my dbo.tbl_SM_SAL_Trend:

    [SMStatsID]
    [DatasourceId]
    [DatasourceName]
    [ServerName]
    [ProtectionGroupName]
    [CreationTime]
    [DiskRecoveryPointAvailable]
    [TapeRecoveryPointAvailable]
    [CloudRecoveryPointAvailable]
    [SLA]

    So it's in my database as well "CreationTime". Maybe it fixes the issue when I manually add "BackupTime" to all necessary tables?

    Cheers

    Wednesday, July 8, 2015 10:02 AM
  • If you still have the server presenting the issue, can you share the output of this SQL Query?

    select distinct Name from tbl_AM_AgentPatch order by name desc

    as well as from this PowerShell command below?

    dir ((Get-Itemproperty -Path 'HKLM:SOFTWARE\Microsoft\Microsoft Data Protection Manager\Setup\').installpath +'bin') | %{ $_.VersionInfo } | ? { $_.productversion -ne $null} | Sort-Object productversion -Unique


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights






    Thursday, July 9, 2015 6:14 AM
  • After adding "BackupTime" to "dbo.tbl_SM_SAL_Trend" I was able to install the RU2!

    Now on UR3, 4, 5 or 6 I get errors again.

    Hey Wilson, thanks for your reply!

    Here is the output from the SQL Query:

    DPM RA Update v4.2.1312.0
    DPM RA Update v4.2.1292.0
    DPM RA Update v4.2.1235.0
    DPM RA Update v4.2.1217.0
    DPM RA Update v4.1.3465.0
    DPM RA Update v4.1.3441.0

    and as well the PS output:

    ProductVersion   FileVersion      FileName
    --------------   -----------      --------
                     8.5.2.0          C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\interop.activeds.dll
    4.2.1176.0       4.2.1176.0       C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\DpmFilter.sys
    4.2.1205.0       4.2.1205.0       C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\StoragePoolManager.dll
    4.2.1235.0       4.2.1235.0       C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\SQLWriterHelperPlugin...
    4.2.1254.0       4.2.1254.0       C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\TBD6E48.tmp
    6.0.6000.16386   6.0.6000.1638... C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\SqmAPI.dll
    Thursday, July 9, 2015 8:19 AM
  • Hi,

    Update rollups are all inclusive, so you can just install UR6 and that will include fixes and features from earlier UR's.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, July 9, 2015 3:39 PM
    Moderator
  • Hey,

    sorry for the late reply.

    Still no changes on this topic. I still can't install the UR6.

    Does anyone has an other idea?

    Monday, August 3, 2015 2:11 PM