none
Update Rollup 8 for System Center 2012 SP1 - Data Protection Manager (KB2991995) install problem RRS feed

  • Question

  • Hi,

    A couple days ago I started the upgrade path of DPM2010 to DPM 2102 R2 on the management server with WinSrv 2008 R2.
    I got issues when installing Update Rollup 8 for System Center 2012 SP1 - and now the DPM 2012 SP1 is in a flawed state .

    Followed more or less the list in this post - https://social.technet.microsoft.com/Forums/en-US/6ba80102-0622-4fce-8229-635eecd44976/dpm-2010-to-2012sp1-setup-fails?forum=dpmsetup :  

    • Upgraded from DPM 2010 to DPM 2012 without any problems. Updated the agents  - and the Protection Groups Ok.
    • Upgraded from DPM 2010 to DPM 2012 SP1 without any problems - Updated the agents  - and the Protection Groups Ok.
    • Applied the Update Rollup 3 for System Center 2012 Service Pack 1 without any problems - and the Protection Groups Ok.

    Then I got problems with Update Rollup 8 for System Center 2012 SP1 - Data Protection Manager (KB2991995) - and DPM 2012 SP1 is now in a flawed state.

    I took backup of the DPM database for each step. But now I release that I have continue to backup the old DPM 2010 db - as I manually run this as a task from Task Shed.  - and forgot to change the instanceName in "DpmBackup.exe -db -instanceName msdpm2010 -targetLocation E:\DPMBackup" to instance msdp2012 after updating to DPM 2012.

    I have verified all the suggestions in https://support.microsoft.com/en-us/help/972727/error-message-when-you-try-to-install-a-system-center-data-protection - and found and resolved some issuses with db backup problems/settings - but still problems.  Also tried the SKIPDBBACKUP=1 method, but no success.

    Please find the current installlog file for the Update Rollup 8 for System Center 2012 SP1 here: https://netserv-my.sharepoint.com/:u:/g/personal/sjb_net-service_no/EcYO3bd0j45CsqClma2dfq8B-7ZKnGJGBPFWWl3RUWK6Ew?e=iyAuCz

    Any help to resolve the issu would be apriciated!

    PS - should the old SQL server 2008 be uninstalled (along with the DPM 2010 instance, after upgraded to DPM 2012 - ? 

    Best regards

    /Stig Jarle



    • Edited by SJBu Tuesday, August 6, 2019 12:19 AM
    Tuesday, August 6, 2019 12:14 AM

All replies

  • Hello Stig,

    Your upgrade process appears to be OK, it looks like the error you're receiving when attempting to install the Update Rollup 8 for DPM 2012 SP1 is the same as in the post below, did you have a look?

    Unable to install Update Rollup 8 for System Center 2012 SP1 - Data Protection Manager (KB2991995)

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, August 6, 2019 6:42 AM
  • Hi Leon,

    Thanks for your reply. Yes - I had already found this post, and reviewed all the suggestions - but none solved the update problem.

    Made just a new attempt to update - please find the log here: 

    DataProtectionManager-KB2991995 2019-08-06

    Also found this in C:\Program Files\Microsoft DPM\DPM\Temp\MSDPMCurr.errlog:

    MSDPMCurr_errlog.txt

    Best regards,
    Stig Jarle




    • Edited by SJBu Tuesday, August 6, 2019 10:20 AM
    Tuesday, August 6, 2019 9:12 AM
  • What exact SQL Server version are you currently running? And what version did you have for DPM 2010?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, August 6, 2019 10:37 AM
  • Hi Leon,

    When upgrading to DPM2012 from DPM 2010 the SQL was updated to SQL Server 2008 R2 (native)  - works fine.

    Also DPM2012 SP1 worked fine with Rollup 3

    Orginal DPM 2010 installed products (back in 2012) was:

    EEC-00682 OLP-NL/SA Microsoft System Center Essentials 2010 Server Management m/ SQL  License
    T7F-00295 OLP-NL/SA Microsoft System Center Essentials Plus 2010 Server Management License

    Regards

    Stig Jarle

    Tuesday, August 6, 2019 11:12 AM
  • The SQL Server version appears to be fine and supported, but it coud be that something didn't got changed properly during the upgrade in the Windows registry, as it is complaining about the following:

    NORMAL CServiceModule::DoStartupValidation
    NORMAL Logging event to NT log from d:\btvsts\14920\private\product\engine\service\dll\servicemodule.cpp(183): DatabaseVersionMismatch
    WARNING Failed: Hr: = [0x80070666] Exiting since the database version doesn't match

    If you've followed Mike's step-by-step over THIS thread, which is the correct way of doing the upgrade, then you might have to create a support ticket to Microsoft (DPM 2012 SP1 still has extended support) so they can dig deeper.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, August 6, 2019 11:29 AM
  • Hi,

    For the interest of other users, I update this post how this case ended:

    I contacted MS Support and raised a case – but I was told that DPM2012 SP1 was out of mainstream support - and the end customer was not entitled to extended support (not SA agreement).

    However, they pointed to the direct cause of the failure - a corrupt table field in the DPM database when applying the Update Rollup 8 for DPM2012 SP1:

    Here is the reply from MS Support:

    As we spoke, looking at the logs from the DPM 2012 SP1 installation failure, the errors are below:

    MSI (s) (D0!E4) [10:59:56:333]: Product: Microsoft System Center 2012 SP1 - Data Protection Manager -- Error 26204. Error -2147217900: failed to execute SQL string, error detail: Invalid column name 'LastRefreshTime'., SQL key: sqlscript_KB2991995Fix.sql SQL string: CREATE  PROCEDURE [dbo].[prc_AM_InstalledAgents_GetAllServers]

    [0x80070666] Exiting since the database version doesn't match=>

    0ED0    16E8    08/06    10:09:47.633    09    servicemodule.cpp(150)            NORMAL    CServiceModule::DoStartupValidation 0ED0    16E8    08/06    10:09:48.163    02    EventManager.cs(143)            NORMAL    Logging event to NT log from d:\btvsts\14920\private\product\engine\service\dll\servicemodule.cpp(183): DatabaseVersionMismatch 0ED0    16E8    08/06    10:09:48.709    09    servicemodule.cpp(187)            WARNING    Failed: Hr: = [0x80070666] Exiting since the database version doesn't match 0ED0    16E8    08/06    10:09:48.709    09    servicemodule.cpp(375)    [0000000069824360]        WARNING    Failed: Hr: = [0x80070666] : Encountered Failure: : lVal : DoStartupValidation() 0ED0    16E8    08/06    10:09:48.709    09    servicemodule.cpp(539)    [0000000069824360]        WARNING    Failed: Hr: = [0x80070666] : Encountered Failure: : lVal : Initialize() 0ED0    16E8    08/06    10:09:48.725    09    servicemodule.cpp(258)    [0000000069824360]        WARNING    Failed: Hr: = [0x80070666] : Encountered Failure: : lVal : InitializeSecurity() 0ED0    16E8    08/06    10:09:48.725    09    servicemodule.cpp(751)            WARNING    Failed: Hr: = [0x80070666] : Encountered Failure: : lVal : m_serviceModule.InitializeLocal() 0ED0    0284    08/06    10:09:51.424    09    MsdpmService.cs(137)            WARNING    Unable to start MSDPM service, Reason = FailedToStart, Stopping MSDPM service 0ED0    16E8    08/06    10:09:51.439    09    servicemodule.cpp(664)            NORMAL    CServiceModule::ShutdownInternal - Starting shutdown. 0ED0    16E8    08/06    10:09:51.439    16    jobmanagerservices.cpp(72)            NORMAL    CJobManagerServices::Shutdown(void) 0ED0    16E8    08/06    10:09:51.502    09    servicemodule.cpp(689)            NORMAL    Deregistered MSDPM COM server successfully 0ED0    0284    08/06    10:09:56.463    09    MsdpmService.cs(169)            NORMAL    MSDPM service status = Stopped 0ED0    0284    08/06    10:09:56.463    09    MsdpmService.cs(185)            NORMAL    Cleanup completed for MSDPM service

    The above means previous upgrades of the DPM DB didn’t go well for some reason. You could go back to DPM 2010, as you have the DBs backed up, and try the upgrade process again, but this is not recommended as from experience we can say, that there is “garbage” left in the DB after each upgrade and this will create possible future problems with DPM, so upgrading from that old version of DPM definitely not a good move in the long run.

    Regarding the “extended support” option for DPM 2012 SP1, it is a service available to customers that have actually paid for it. You customers contract unfortunately doesn’t cover that. Support for DPM 2012 SP1 has ended in November 2017 as well as support for DPM 2012 R2.

    Just as before, our recommendation here is to build a new DPM 2019 server.

    I this case, I ended with reinstalling the DPM server with  Windows Server 2012 R2 – and installed a fresh copy of DPM2012 R2.  All Is now functioning well – and I have to agree that reinstalling from scratch in many cases is a better solution than migrating and troubleshooting!

    Best Regards
    /Stig Jarle

    • Proposed as answer by Leon Laude Monday, August 19, 2019 9:36 AM
    Monday, August 19, 2019 9:31 AM
  • Thanks for sharing!

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, August 19, 2019 9:36 AM