none
An unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80110802) (0x80110802)) RRS feed

  • Question

  • Using DPM 2012 R2, I get the error, "An unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80110802) (0x80110802))" when running a consistency check for any virtual machine running that is running on a specific node of my Windows 2012 R2 Hyper-V cluster.  If I move the VM to another node, the job completes successfully. 
    Tuesday, January 24, 2017 3:25 PM

Answers

  • Update: I compared the following registry settings between two 'good' hosts and the 'bad' host.

    The 'bad' host had an extra key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent]  "NullProviderInstalled"=dword:00000001

    After backing up this registry section, I deleted the key, then restarted the DPMRA service and my VM backups are working again.


    Robin Williams



    • Edited by rocwilliams Wednesday, January 25, 2017 6:24 PM
    • Marked as answer by rocwilliams Wednesday, January 25, 2017 6:25 PM
    Wednesday, January 25, 2017 6:00 PM

All replies

  • Hi,

    Most likely you have a volume shadow copy (VSS) problem on the affected node.  Look in the application event log for any VSS errors.  You can also run:  vssadmin list providers and make sure the system provider gets listed.


    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, January 24, 2017 11:47 PM
    Moderator
  • The application event log shows no VSS errors and the system provider is listed:

    C:\Windows\system32>vssadmin list providers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.
    Provider name: 'Microsoft CSV Shadow Copy Helper Provider'
       Provider type: Software
       Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d}
       Version: 1.0.0.1
    Provider name: 'Microsoft CSV Shadow Copy Provider'
       Provider type: Software
       Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}
       Version: 1.0.0.1
    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


    Robin Williams

    Wednesday, January 25, 2017 3:25 PM
  • Hi,

    My first observation is that there are two "VSS Null Providers" missing in the above output.  Those providers get installed as part of DPM 2012 R2 UR3 or later on the nodes when protecting a Windows 2012 R2 hyper-V cluster.   Can you A) Verify you are running DPM 2012 R2 UR3 or later and B) if so are the null providers listed on the node where backups work.


    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.

    Wednesday, January 25, 2017 4:03 PM
    Moderator
  • Hi Mike,

    The host in question is running SCDPM 2012 R2 Rollup Update 11.  I checked VSS on two hosts in the same cluster where backups are working and get the exact same output as the host where backups are failing.


    Robin Williams

    Wednesday, January 25, 2017 4:48 PM
  • Update: I compared the following registry settings between two 'good' hosts and the 'bad' host.

    The 'bad' host had an extra key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent]  "NullProviderInstalled"=dword:00000001

    After backing up this registry section, I deleted the key, then restarted the DPMRA service and my VM backups are working again.


    Robin Williams



    • Edited by rocwilliams Wednesday, January 25, 2017 6:24 PM
    • Marked as answer by rocwilliams Wednesday, January 25, 2017 6:25 PM
    Wednesday, January 25, 2017 6:00 PM
  • Hi,

    The real issue is that the DPM installed VSS Null providers are missing.  Without the Null Providers, real VSS snapshots are used and that can lead to a host of problems (performance issues, backup failures).  I've never seen the VSS Null Providers missing before, so not why they are not installed when they should be.


    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.

    Wednesday, January 25, 2017 9:46 PM
    Moderator
  • OK. I'll see if I can get a window to uninstall and reinstall the agent sometime within the next week, then check again to see if anything changes. Thanks for the guidance!

    Robin Williams

    Thursday, January 26, 2017 4:20 PM
  • For future reference, I checked the providers from a host on a completely different cluster and found the NULL providers that are expected.  Current plan is to reinstall DPM cleanly on the hosts in the suspect cluster.

    C:\Users\rwilliams>vssadmin list providers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Provider name: 'Microsoft CSV Shadow Copy Helper Provider'
       Provider type: Software
       Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d}
       Version: 1.0.0.1
    Provider name: 'Microsoft CSV Shadow Copy Provider'
       Provider type: Software
       Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}
       Version: 1.0.0.1
    Provider name: 'VSS Null Provider'
       Provider type: Software
       Provider Id: {8202aeda-45bd-48c4-b38b-ea1b7017aec3}
       Version: 4.2.1553.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.1553.0

    Robin Williams

    Friday, January 27, 2017 6:41 PM