none
Error with client sync - VSS Provider is in a bad state RRS feed

  • Question

  • I'm having trouble with several client computers not synchronizing with the DPM server. This has been happening for awhile and I can't figure out what's causing it.  The error shown in the DPM client is:

    "The VSS application writer or the VSS Provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation." 

    The output from VSSADMIN LIST WRITERS doesn't show any errors with any of the writers and neither the system nor the application logs show any errors at the time of the synchronization error. 


    I looked in the DPMRACurr.errlog around the synchronization start time and this is what it shows:

    Failed: Hr: = [0x80042316] : Encountered Failure: : lVal : m_apVssBackupComponents->StartSnapshotSet(&snapshotSetId)
    Failed: Hr: = [0x80042316] : Encountered Failure: : lVal : hrTemp
    Failed: Hr: = [0x80042316] : Encountered Failure: : lVal : pTransition->Execute(pEvent)
    Failed: Hr: = [0x80042316] : Encountered Failure: : lVal : m_pCurrentState->SendEvent(pEvent, pNextState)
    CreateSnapshotSubTask: this:[0000000001A0CE50], Component: DisconnectedClient
    CVssBaseRequestor: constructor [00000000019C5B00]
    CVssSnapshotRequestor::CVssSnapshotRequestor [00000000019C5B00]
    CreateSnapshotSubTask: this:[0000000001A0CE50], m_pVssRequestor = [27024128] 
    CVssBaseRequestor::Initialize [00000000019C5B00]
    CVssSnapshotRequestor::InitializeSnapshotCreation [00000000019C5B00]
    Failed to read registry entry NullProviderInstalled
    Null Provider installation is set to 0
    m_fIsSnapshotLessBackup 0
    Using AUTO-RELEASE Snapshot
    snapshotContext 16
    CVssSnapshotRequestor::StartPrepareForBackup [00000000019C5B00] m_snapshotInfo.snapshotContext 16
    CVssSnapshotRequestor::AddVolumeForSnapshot [00000000019C5B00]
    ssLocalVolumeGuid = [\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\], ssClusterVolGuid=[\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\]
    CVssSnapshotRequestor::AddVolumeForSnapshot [00000000019C5B00]
    CVssSnapshotRequestor: AddVolumeForSnapshot - Marked volume c:\ to be snapshot
    CVssSnapshotRequestor::AddVolumeForSnapshot [00000000019C5B00]
    ssLocalVolumeGuid = [\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\], ssClusterVolGuid=[\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\]
    CVssSnapshotRequestor::AddVolumeForSnapshot [00000000019C5B00]
    CVssSnapshotRequestor::AddVolumeForSnapshot [00000000019C5B00]
    ssLocalVolumeGuid = [\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\], ssClusterVolGuid=[\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\]
    CVssSnapshotRequestor::AddVolumeForSnapshot [00000000019C5B00]
    CVssSnapshotRequestor::AddVolumeForSnapshot [00000000019C5B00]
    ssLocalVolumeGuid = [\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\], ssClusterVolGuid=[\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\]
    CVssSnapshotRequestor::AddVolumeForSnapshot [00000000019C5B00]
    CVssSnapshotRequestor::AddVolumeForSnapshot [00000000019C5B00]
    ssLocalVolumeGuid = [\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\], ssClusterVolGuid=[\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\]
    CVssSnapshotRequestor::AddVolumeForSnapshot [00000000019C5B00]
    CUsnJournal::GetVolumeHandle Volume Path = \\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}
    CUsnJournal::GetVolumeHandle Volume Path = \\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}, Volume Handle = 824
    CUsnJournalHelper::GetNextUsnInternal(vol:824)
    UsnJournalID    = 0x01D29BBC33B8DDE8
    FirstUsn        = 0x0000000090900000
    NextUsn         = 0x00000000A702F0E8
    LowestValidUsn  = 0x0000000000000000
    MaxUsn          = 0x7FFFFFFFFFFF0000
    MaximumSize     = 0x0000000012C00000
    AllocationDelta = 0x0000000004B00000
    CVssSnapshotRequestor::StartPrepareForBackup [00000000019C5B00]
    <VSS_CONTEXT><COMPONENTS></COMPONENTS>
    <SNAPSHOT_CONTEXT>          SelectComponent = 1,          PartialFileSupport = 0,          BootableState = 0,          BackupType = 1,          SnapshotContext = 16,          SnapshotAttributes = VSS_CTX_FILE_SHARE_BACKUP          </SNAPSHOT_CONTEXT>
    <SnapShotVolumes><Volume>              <Name>\\?\Volume{86f9943f-eb1f-4e7f-be34-9727f42a88e9}\</Name>              <SnapshotPath>(null)</SnapshotPath>              <MountPoint>c:\</MountPoint>              <MountPointArray></MountPointArray>              <SnapshotId>{00000000-0000-0000-0000-000000000000}</SnapshotId>              <ProviderId>{00000000-0000-0000-0000-000000000000}</ProviderId>              <IsHardwareProvider>0</IsHardwareProvider>              </Volume></SnapShotVolumes>
    </VSS_CONTEXT>


    I don't see anything here that's telling me there was an error, but the client reports the synchronization failed and no restore point gets created. When I look at the task scheduler it looks like ScheduledDPMClientBackup is still running. If I end the task and reboot, Windows hangs up like it's trying to close something. When I'm able to log back in to Windows, if I do a manual sync (before the scheduled task runs) the client will sync without a problem. What could be getting hung up? What can I check to find out?

    This has been happening on this client for over a month now. The machine is a Surface Pro 3 running Windows 10 Enterprise.

    Monday, June 26, 2017 6:05 PM