none
DPM2012 R2 Update Rollup 3 Install Problem

    Question

  • Hi, 

    the update came through WSUS and wouldn't install successfully. I also tried to install manually, 
    but it doesn't go through. 

    Anyone else having issuse with this update?

    What I also noticed is, that VSS on the DPM Server itself was broken afterwards, and I found a VSS Null Provider and also a VSS Null Service that was running. Deleting those registry keys and stopping this service solved the VSS problem. Google didn't tell anything about this service or VSS Provider, only a dll that was packed within UR3. 

    I believe it also had to do with the failed UR3 Update that was rolled back.

    So happy to hear if anyone could successfully install it. The log didn't tell me a lot or I didn't know what to look after. 

    Thanks
    Patrick 

    Sunday, August 3, 2014 12:38 AM

Answers

  • OK it has been fixed.

    Problem was on a Server 2012 R2 system (physical)

    Could not use windows update on the DPM server so manually downloaded and ran the update which seemed to go OK - all of the protected servers were then restarted. I then had problems with a single protected server (2012R2). Unable to synchronise and with VSS errors as detailed earlier

    To fix this I removed the agent from the protected server using add/remove programs. Rebooted the server. Manually installed the agent. Restarted server. When it rebooted I was able to synchronise data again after I removed the protected server from the protection group, deleted the backups and recreated the server in the PG. This meant I lost several backups obviously :-()

    Note that on a Server 2012R2 system you do get the following output from vssadmin list providers so I would not advise deleting anything from the registry unless you are certain it is the cause of the problem.

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Provider name: 'Hyper-V IC Software Shadow Copy Provider'
       Provider type: Software
       Provider Id: {74600e39-7dc5-4567-a03b-f091d6c7b092}
       Version: 1.0.0.0

    Provider name: 'VSS Null Provider'
       Provider type: Software
       Provider Id: {8202aeda-45bd-48c4-b38b-ea1b7017aec3}
       Version: 4.2.1254.0

    Provider name: 'Microsoft File Share Shadow Copy provider'
       Provider type: Fileshare
       Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
       Version: 1.0.0.1

    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
       Provider type: System
       Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
       Version: 1.0.0.7

    Provider name: 'VSS Null Provider'
       Provider type: Fileshare
       Provider Id: {f4a69dd4-f712-40e3-a6b3-faeff03cb2b8}
       Version: 4.2.1254.0

    .


    prd




    Monday, August 4, 2014 11:46 PM

All replies

  • I am also having the same problem. The DPM logs in C:\Windows\Temp indicate there is an error in a service called VssNullProvider that doesn't seem to exist on the server I am trying to update. 

    This is what I found in the MSDPMAgentBootstrap0Curr.errlog 

    Trying to open windows service failed for Service = [VssNullProvider]

    While in the MSDPMAgentPatchInstall log contains the following error, which indicates FATAL ERROR DURING INSTALLATION:

    Windows Installer reconfigured the product. Product Name: Microsoft System Center 2012 R2 DPM Protection Agent. Product Version: 4.2.1254.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1603.

    Not even a Windows Updates with all the required security and critical and optional patches solved the problem

    From a DPM server perspective, there is no error, the error I am getting is a protected server side
    Monday, August 4, 2014 2:00 PM
  • I couldn't install on the DPM server from the widows update so I manually downloaded it and installed from the DPM server. This appeared to work OK and I was able to update the agents on all protected servers.

    However one protected server cannot run a consistency check and fails with VSS errors in the application logs located on the DPM server. It was OK before the update. The vss error in the application log is event 12289 as follows

    Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{8cc68ba9-084a-11e4-940a-00137264942c} - 0000000000000180,0x0053c06c,000000DBE3C7D190,0,000000DBE3C720E0,4096,[0]).  hr = 0x80070005, Access is denied.

    .

    Operation:

       Query diff area for this volume

    Context:

       Volume Name: \\?\Volume{8cc68ba9-084a-11e4-940a-00137264942c}\It appears to be looking for a different volume which is linked to the replica

    VSSADMIN list writers on the DPM server all show OK and the VSSADMIN  list providers is also OK

    If I look at the DPM log when the update is installed I can see a load of errors to do with modifying security groups but nothing obvious


    prd


    Monday, August 4, 2014 2:41 PM
  • Hmm

    When I checked the protected server giving me issues then I too see the VssNullProvider list providers issue.

    I ran the agent update from the DPM console and it worked fine on all of the servers but there is an issue on this single server. I will deinstall the agent on the protected server and run a manual install to see if this fixes it


    prd

    Monday, August 4, 2014 7:36 PM
  • OK it has been fixed.

    Problem was on a Server 2012 R2 system (physical)

    Could not use windows update on the DPM server so manually downloaded and ran the update which seemed to go OK - all of the protected servers were then restarted. I then had problems with a single protected server (2012R2). Unable to synchronise and with VSS errors as detailed earlier

    To fix this I removed the agent from the protected server using add/remove programs. Rebooted the server. Manually installed the agent. Restarted server. When it rebooted I was able to synchronise data again after I removed the protected server from the protection group, deleted the backups and recreated the server in the PG. This meant I lost several backups obviously :-()

    Note that on a Server 2012R2 system you do get the following output from vssadmin list providers so I would not advise deleting anything from the registry unless you are certain it is the cause of the problem.

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Provider name: 'Hyper-V IC Software Shadow Copy Provider'
       Provider type: Software
       Provider Id: {74600e39-7dc5-4567-a03b-f091d6c7b092}
       Version: 1.0.0.0

    Provider name: 'VSS Null Provider'
       Provider type: Software
       Provider Id: {8202aeda-45bd-48c4-b38b-ea1b7017aec3}
       Version: 4.2.1254.0

    Provider name: 'Microsoft File Share Shadow Copy provider'
       Provider type: Fileshare
       Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
       Version: 1.0.0.1

    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
       Provider type: System
       Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
       Version: 1.0.0.7

    Provider name: 'VSS Null Provider'
       Provider type: Fileshare
       Provider Id: {f4a69dd4-f712-40e3-a6b3-faeff03cb2b8}
       Version: 4.2.1254.0

    .


    prd




    Monday, August 4, 2014 11:46 PM
  • hi,

    well your issue might have been fixed, but it wasn't about the first question of mine, that installation doesn't work, neither WSUS nor manual install. Seems you didn't have problems with the install itself just with agents. 

    My problem is, that updating wsus fails first hand, with the 2nd problem, that a VSS error did happen which was only solved removing VSS Null  I believe, the VSS Null will work fine, if UR3 update went through. 

    Thanks
    Patrick

    Tuesday, August 5, 2014 9:46 PM
  • Hi Patrick

    Your question asked "So happy to hear if anyone could successfully install it." Which I did successfully on a DPM 2012 R2 system using Server 2012. I downloaded the update manually from the Microsoft site.

    I too had problems using windows update. A manual download to the DPM server and install worked as described but there was indeed a problem with one agent.


    prd

    Tuesday, August 5, 2014 10:34 PM
  • But loosing backups doing the update rollup is also not a good thing to hear.... well anyway. I will just wait and see if any solution pops up or any update is released. It has been twice now that an update rollup gives troubles, it's been I think 1 year from now the UR3 without SP1 came out and broke installations and needed to be fixed by microsoft itself with an sql query that you were not allowed to give anyone else. Here the update rolled back and it seems left just little damage on our side, as we didn't loose backup versions, 

    Thanks
    Patrick


    Tuesday, August 5, 2014 10:38 PM
  • Reading about others having trouble installing via Windows Update, and looking up some of the error codes mentioned in related forum posts, suggested that for the people who were experiencing this problem, that Windows Update may have failed to download all the required components for the update and attempted install with some files missing or corrupted.

    I therefore decided to play it safe, and download CU3 for DPM2012R2 directly from the Microsoft Catalog using the Microsoft Catalog enforced download manager.

    Funnily enough, each download attempt appeared to permanently stall at exactly the 59% mark, and never completed.  Attempted this numerous times from different computers, none of which used an explicit proxy server.

    Given the recent release of this update (less than a few days old), I assumed the CDN used by MS may not have fully delivered all the content to the download web server in my country yet., or similar.

    Attempting the same download from home worked fine, suggesting that maybe our enterprise edge firewall content filter may have timed out recursively scanning the contained containers in the file, or something.

    After transporting the successfully downloaded .CAB files to work using a USB stick, I was able to successfully update our test DPM server to 2012 R2 CU3 the first time with no issue.

    Its worth mentioning that the release notes installation instructions are written in such a way that they can be interpreted as only required for first time installs, especially for the Windows Server 2003 operating system.  It's been mentioned that the client agent for Windows Server 2003 is basically just DPM 2012 SP1, and as such isn't expected to change as DPM 2012 R2 gets updated.  However, the agent installers for Windows Server 2003 between DPM 2012 R2 CU2 and CU3 have different SHA1 values, so there is some kind of difference.

    Do Windows Server 2003 agents need to be updated with the CU3 version if CU2 was previously installed?  The DPM Console GUI appears to have been hard coded to never display "update required" for windows server 2003 guests, presumably because they will always be v4.1 instead of v4.2 agents, and the GUI cannot successfully perform the update since these need to be manually installed.  Therefore, whether to update server 2003 agents from 2012 R2 CU2 to CU3 is ambiguous.


    Tuesday, August 5, 2014 11:22 PM
  • Thanks for your answer. When I downloaded through the catalog, the download worked fine, 4 files, all .exes though. Might be I have to dig deeper into it.

    the last portion of the install.log shows following: 

    Installation Error Code 1603. (same as stated above). 

    MSI (s) (28:CC) [01:28:21:927]: Note: 1: 1729 
    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (28:CC) [01:28:21:927]: Transforming table Error.

    MSI (s) (28:CC) [01:28:21:927]: Note: 1: 2262 2: Error 3: -2147287038 
    MSI (s) (28:CC) [01:28:21:927]: Product: Microsoft System Center 2012 R2 Data Protection Manager -- Configuration failed.

    Not sure if the transforming table error mean a lot as those messages happen after UR3 update. 

    Only thing I am not sure, as I am getting the same error code as Ihab, if it could have to do with protection agent. But on the DPM itself, there is no separat installation of a protection agent, that could be uninstalled. 

    But seems quite some people have this problem as the comments of this blogpost... 

    http://blogs.technet.com/b/dpm/archive/2014/07/29/update-rollup-3-for-system-center-2012-r2-data-protection-manager-is-now-available.aspx


    Tuesday, August 5, 2014 11:38 PM
  • maybe you forgot to start the downloaded executable from an elevated command prompt?

    (Run As Administrator?)

    Detectoid for System Center 2012 R2 - Data Protection Manager Server-all-dataprotectionmanager2012r2-kb2966014_9f7ca4d5c695d550cdbb66aca36c693a392423be.exe

    Tuesday, August 5, 2014 11:53 PM
  • >Error 3: -2147287038 

    = System.IO.FileNotFoundException

    http://support.microsoft.com/kb/555650

    looks like some file can't be found...

    Wednesday, August 6, 2014 12:02 AM
  • I've made the update w/o any issues. I've installed the UR3 for DPM 2012 R2 via WSUS on an Windows Server 2012 R2 Backup Machine (physical) with SQL Server 2008 R2 on Windows 2008 R2 Database Server (virtual).
    Wednesday, August 6, 2014 12:37 PM
  • Is there a resolution for this yet? I'm also getting the 80070643 error trying to install UR3 on multiple DPM 2012 R2 servers.

    Wednesday, August 27, 2014 1:28 PM
  • I have exactly the same issue.

    I have installed Update Rollup 3 for SCDPM 2012 R2 on our DPM Server through WSUS. I then updated the DPM Agent on every Protected Computer one-by-one. Including all our Hyper-V Servers (based on WS2012R2) which are part of two Hyper-V Clusters. As required I restarted every Protected Computer, including those Hyper-V Servers.

    Now every Hyper-V Server reports the VssNullProvider service has stopped. VM backup seems to work, but this is not good.

    There is not much information on the internet yet. Any suggestions?


    Boudewijn Plomp, BPMi Infrastructure & Security

    Please remember, if you see a post that helped you please click "Vote as Helpful" and if it answered your question, please click "Mark as Answer".

    Thursday, August 28, 2014 10:24 AM
  • >every Hyper-V Server reports the VssNullProvider service has stopped

    I guess you can alter the recovery options for that windows service, so that the service manager restarts the service after 10 minutes if it stops, or more likely, doesn't start well so early in the boot cycle, but starts just fine later.  Alternatively set it's start-up to "Automatic (Delayed)". 

    Tuesday, September 2, 2014 9:18 AM
  • >every Hyper-V Server reports the VssNullProvider service has stopped

    I guess you can alter the recovery options for that windows service, so that the service manager restarts the service after 10 minutes if it stops, or more likely, doesn't start well so early in the boot cycle, but starts just fine later.  Alternatively set it's start-up to "Automatic (Delayed)". 


    That is more a work-around. Not a long-term solution.

    Boudewijn Plomp, BPMi Infrastructure & Security | Please remember, if you see a post that helped you please click "Vote as Helpful" and if it answered your question, please click "Mark as Answer".

    Tuesday, September 2, 2014 2:45 PM
  • Have exactly the same problem, 80070643 error when trying to install UR3 on DPM 2012 R2 server. I have two DPM servers, both 2008 R2 platform. One of them received an update without any issues, and second one fails to update no matter if from WSUS or from MS downloaded files.

    Log file error section looks exactly as Patrick N provided.

    Have anyone managed to workaround without reinstalling the DPM? Would highly appreciate.

    Thanks.

    Friday, September 12, 2014 2:37 PM