Strange mixed error messages


Author
Message
lovelyjubbly
lovelyjubbly
Proficient Member
Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)
Group: Forum Members
Posts: 117, Visits: 452
I'm getting 2 different errors:

Monday

Monday, February 22, 2021 11:00:51
    Initializing
    Destination Drive:    Free Space 1.70 TB
    Free space threshold:    Delete oldest backup sets when free space is less than 5.00 GB
    
    Creating Volume Snapshot - Please Wait
    
    Failed:    Failed - 0x80042316 - IDispatch error #8470 - Retrying without VSS Writers
    
    ERROR: COM call "m_pVssObject->StartSnapshotSet(&m_latestSnapshotSetID)" failed.
    - Returned HRESULT = 0x80042316
    - Error text: VSS_E_SNAPSHOT_SET_IN_PROGRESS
    ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed.
    - Returned HRESULT = 0x80042301
    - Error text: VSS_E_BAD_STATE
    ERROR: COM call "m_pVssObject->StartSnapshotSet(&m_latestSnapshotSetID)" failed.
    - Returned HRESULT = 0x80042316
    - Error text: VSS_E_SNAPSHOT_SET_IN_PROGRESS
    Gathering Windows Events - Please Wait
    Backup aborted! - Failed To Create Volume Snapshot. Failed - 0x80042316 - IDispatch error #8470

Tuesday

   Backup aborted! - Unable to read from disk - Error Code 21 - The device is not ready.

Not sure what to do next?

Thanks.

Beardy
Beardy
Proficient Member
Proficient Member (259 reputation)Proficient Member (259 reputation)Proficient Member (259 reputation)Proficient Member (259 reputation)Proficient Member (259 reputation)Proficient Member (259 reputation)Proficient Member (259 reputation)Proficient Member (259 reputation)Proficient Member (259 reputation)Proficient Member (259 reputation)
Group: Forum Members
Posts: 206, Visits: 851
This KB article looks relevant to the first one. Which aside from a different backup software running can sometimes be down to Windows Update, or some other installer making a snapshot/restore point at the time Macrium also tries.  Which in the case where it's WU is purely an unlucky coincidence of timing.

The second is harder to know what to say about without more info about what was being backed up, however, it looks like something preventing the source being read.
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)
Group: Forum Members
Posts: 8.8K, Visits: 59K
When you see VSS errors, it's often helpful to review the VSS log, which is separate from the main job log.  It may contain more information.  But based on that error, you might be able to fix that with a simple restart.

Edited 23 February 2021 1:48 AM by jphughan
lovelyjubbly
lovelyjubbly
Proficient Member
Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)
Group: Forum Members
Posts: 117, Visits: 452
Thanks jphughan,

Monday's VSS:

(Gathering writer metadata...)
(Waiting for the asynchronous operation to finish...)
Initialize writer metadata ...
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
Discover directly excluded components ...
- Excluding writer '' since it has no selected components for restore.
- Excluding writer '' since it has no selected components for restore.
- Excluding writer 'MSSearch Service Writer' since it has no selected components for restore.
- Excluding writer 'BITS Writer' since it has no selected components for restore.
- Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore.
Discover components that reside outside the shadow set ...
Discover all excluded components ...
Discover excluded writers ...
Discover explicitly included components ...
Verifying explicitly specified writers/components ...
Select explicitly included components ...
* Writer 'Task Scheduler Writer':
 - Add component \TasksStore
* Writer 'VSS Metadata Store Writer':
 - Add component \WriterMetadataStore
* Writer 'Performance Counters Writer':
 - Add component \PerformanceCounters
* Writer 'WMI Writer':
 - Add component \WMI
* Writer 'Registry Writer':
 - Add component \Registry
* Writer 'COM+ REGDB Writer':
 - Add component \COM+ REGDB

ERROR: COM call "m_pVssObject->StartSnapshotSet(&m_latestSnapshotSetID)" failed.
- Returned HRESULT = 0x80042316
- Error text: VSS_E_SNAPSHOT_SET_IN_PROGRESS
Completing the backup (BackupComplete) ...

ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed.
- Returned HRESULT = 0x80042301
- Error text: VSS_E_BAD_STATE
- Setting the VSS context to: 0x00000010

ERROR: COM call "m_pVssObject->StartSnapshotSet(&m_latestSnapshotSetID)" failed.
- Returned HRESULT = 0x80042316
- Error text: VSS_E_SNAPSHOT_SET_IN_PROGRESS

Tuesday's VSS

(Gathering writer metadata...)
jphughan - 23 February 2021 1:46 AM
When you see VSS errors, it's often helpful to review the VSS log, which is separate from the main job log.  It may contain more information.  But based on that error, you might be able to fix that with a simple restart.


(Waiting for the asynchronous operation to finish...)
Initialize writer metadata ...
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
Discover directly excluded components ...
- Excluding writer '' since it has no selected components for restore.
- Excluding writer '' since it has no selected components for restore.
- Excluding writer 'MSSearch Service Writer' since it has no selected components for restore.
- Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore.
Discover components that reside outside the shadow set ...
Discover all excluded components ...
Discover excluded writers ...
Discover explicitly included components ...
Verifying explicitly specified writers/components ...
Select explicitly included components ...
* Writer 'Task Scheduler Writer':
 - Add component \TasksStore
* Writer 'VSS Metadata Store Writer':
 - Add component \WriterMetadataStore
* Writer 'Performance Counters Writer':
 - Add component \PerformanceCounters
* Writer 'WMI Writer':
 - Add component \WMI
* Writer 'Registry Writer':
 - Add component \Registry
* Writer 'COM+ REGDB Writer':
 - Add component \COM+ REGDB
Creating shadow set {452569d4-96f8-4876-8346-251d9ea5b14f} ...
- Adding volume \\?\Volume{b48b3027-a444-436e-a8de-136bdf7ea0b5}\ [C:\] to the shadow set...
Preparing for backup ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Creating the shadow (DoSnapshotSet) ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Shadow copy set successfully created.
Saving the backup components document ...

List of created shadow copies:


Querying all shadow copies with the SnapshotSetID {452569d4-96f8-4876-8346-251d9ea5b14f} ...

* SNAPSHOT ID = {53cc6861-b9ce-46b0-b091-2b5ba5e0da61} ...
 - Shadow copy Set: {452569d4-96f8-4876-8346-251d9ea5b14f}
 - Original count of shadow copies = 1
 - Original Volume name: \\?\Volume{b48b3027-a444-436e-a8de-136bdf7ea0b5}\ [C:\]
 - Creation Time: 2/23/2021 11:00:49 AM
 - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy102
 - Originating machine: dianalat
 - Service machine: dianalat
 - Not Exposed
 - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
 - Attributes: Auto_Release Differential



jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)
Group: Forum Members
Posts: 8.8K, Visits: 59K
Seeing as today is Monday (at least in the US), I'm not sure what day the Tuesday log refers to, but did you try just restarting?

lovelyjubbly
lovelyjubbly
Proficient Member
Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)
Group: Forum Members
Posts: 117, Visits: 452
jphughan - 23 February 2021 1:57 AM
Seeing as today is Monday (at least in the US), I'm not sure what day the Tuesday log refers to, but did you try just restarting?

We're downunder, so Tuesday already here Smile
Restarting the computer?
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)Macrium Evangelist (13K reputation)
Group: Forum Members
Posts: 8.8K, Visits: 59K
Yes, restarting the computer.  And if that doesn't work, try the Fix VSS Problems utility built into Reflect, found under the Other Tasks menu.

lovelyjubbly
lovelyjubbly
Proficient Member
Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)
Group: Forum Members
Posts: 117, Visits: 452
Just spoken to the user, and after the Monday error, she restarted with all the windows updates installing.

Which is what Beardy said, thank you.

So I'll need to look at the second error now, I'll check Macrium and see if there are any updates available.



lovelyjubbly
lovelyjubbly
Proficient Member
Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)Proficient Member (204 reputation)
Group: Forum Members
Posts: 117, Visits: 452
Ran Macrium upgrade from 7.2 to 7.3, then ran Full backup which went well.

Lets see what happens today during scheduled backup.

Edited 23 February 2021 8:39 PM by lovelyjubbly
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search