none
Can't install Update Rollup 14 RRS feed

  • Question

  • Hi all - firstly apologies for the long story ahead, but I've totally run out of ideas.

    I had a SCDPM 2012 R2 UR14 server running a local SQL instance that I attempted to upgrade to DPM 2016.  Before doing so I took a full backup of the DPM database.  The upgrade failed due to me not having the correct permissions to perform the upgrade on the SQL instance.  Turns out I was a domain admin and sysadmin everywhere except on THIS particular SQL instance.

    Once I got the correct permissions to the SQL instance, I had to back everything out and start again.  

    This meant uninstalling SCDPM 2012 R2 (retaining disk based recovery points), and then deleted the database from the SQL instance.  So now I'm in the process of restoring the DPM server back to what it was so I can attempt the upgrade again.

    As far as I'm aware, I should be able to do this by performing the following...

    1. Install SCDPM 2012 R2 (this will create a new database)

    2. Update SCDPM 2012 R2 to UR14 (so the database is the same version as it was before)

    3. Use dpmsync to restore my backed up database to the new (empty) database created by the install I just did.

    4. Use dpmsync again to sync everything up - open the DPM console and I should be back to where I was

    ^someone please correct me if I'm wrong about this...

    Now the problem I have is, I'm at Step 2 and I just cannot get UR14 installed.   The installation of UR14 fails and in the log this is what I see.

    MSI (s) (DC:1C) [12:08:48:394]: Product: Microsoft System Center 2012 R2 Data Protection Manager - Update 'Microsoft System Center 2012 R2 Data Protection Manager Update - KB4043315' could not be installed. Error code 1603. Additional information is available in the log file C:\Program Files\Microsoft System Center 2012 R2\DPM\DPMLogs\DataProtectionManager-KB4043315.log.

    MSI (s) (DC:1C) [12:08:48:409]: Windows Installer installed an update. Product Name: Microsoft System Center 2012 R2 Data Protection Manager. Product Version: 4.2.1205.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: Microsoft System Center 2012 R2 Data Protection Manager Update - KB4043315. Installation success or error status: 1603.

    MSI (s) (DC:1C) [12:08:48:409]: Note: 1: 1729

    MSI (s) (DC:1C) [12:08:48:409]: Transforming table Error.

    MSI (s) (DC:1C) [12:08:48:409]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (s) (DC:1C) [12:08:48:409]: Product: Microsoft System Center 2012 R2 Data Protection Manager -- Configuration failed.

    MSI (s) (DC:1C) [12:08:48:409]: Windows Installer reconfigured the product. Product Name: Microsoft System Center 2012 R2 Data Protection Manager. Product Version: 4.2.1205.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1603.

    I know that Error -2147287038 is "access denied" or "unauthorised" or something like that.  So then I went and looked in the SQL logs.

    On the SQL side - this is what I see (it repeats a few times)

    Setting database option SINGLE_USER to ON for database 'DPMDB_MYDPMSERVER'.

    Error: 18456, Severity: 14, State: 38.

    Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'DPMDB_MYDPMSERVER'. [CLIENT: <local machine>]

    I can verify that NT AUTHORITY\SYSTEM does have the sysadmin server role on the SQL instance, and the SQL Service runs as Local System on the machine (it's SQL 2012 with SP4).

    Can anybody point me in the right direction of things to check/do, so that I may get UR14 installed and try recovering this DPM database?

    Thanking you in advance!


    http://www.dreamension.net

    Thursday, February 22, 2018 4:16 AM

Answers

  • Well I got it working.  I genuinely exhausted just about every avenue I had and internet search result.   Even procmon and SQL Profilers returned nothing of value in regards to this issue, and removing/re-adding the NT AUTHORITY\SYSTEM account, sysadmin, db owner, schema owner, explicit file permissions etc - none of it worked.

    The solution

    In a last ditch effort before uninstalling SQL and rebuilding that - I thought I'd try one last thing.  Rather than run the update manually (even though my account is a full admin & sysadmin now) - I thought I'd let Windows Update have a go at applying the update.

    And what do you know - that worked.  

    So Windows Update applied UR14 to my empty DPM 2012 R2 RTM database, and I was able to use dpmsync to restore my backed up UR14 database and resynchronise.  Now it's all back up and running like nothing happened.

     

    http://www.dreamension.net

    Friday, February 23, 2018 2:03 AM

All replies

  • I can also confirm the NT AUTHORITY\SYSTEM uses the "master" database as it's default, and that database exists and is online.  (I read some articles that said to check that).

    http://www.dreamension.net

    Thursday, February 22, 2018 4:31 AM
  • I can post the full KB4043315 installation log if anybody would like to look - but it's huge...  6Mb.

    http://www.dreamension.net

    Thursday, February 22, 2018 6:14 AM
  • Well I got it working.  I genuinely exhausted just about every avenue I had and internet search result.   Even procmon and SQL Profilers returned nothing of value in regards to this issue, and removing/re-adding the NT AUTHORITY\SYSTEM account, sysadmin, db owner, schema owner, explicit file permissions etc - none of it worked.

    The solution

    In a last ditch effort before uninstalling SQL and rebuilding that - I thought I'd try one last thing.  Rather than run the update manually (even though my account is a full admin & sysadmin now) - I thought I'd let Windows Update have a go at applying the update.

    And what do you know - that worked.  

    So Windows Update applied UR14 to my empty DPM 2012 R2 RTM database, and I was able to use dpmsync to restore my backed up UR14 database and resynchronise.  Now it's all back up and running like nothing happened.

     

    http://www.dreamension.net

    Friday, February 23, 2018 2:03 AM
  • It worked! Thnx!
    Monday, July 30, 2018 5:27 AM