Symptoms
If the backup fails with Exit Code -311, check the <Unixtime>.log in the installation path's logs folder. If you find an error about VSS Writer, it means the snapshot couldn't be created.
Error sample
—- log excerpt —-
01/19/2018 01:22:39.330 VssStart()
01/19/2018 01:22:39.373 Using Common Provider
01/19/2018 01:23:20.701 COM Error(0x80042316): m_pVssObject->StartSnapshotSet(&m_latestSnapshotSetID)
01/19/2018 01:23:20.832 [07/19/2017 10:23:20.701] OUTPUT: – Error text: VSS_E_SNAPSHOT_SET_IN_PROGRESS
01/19/2018 01:23:20.833 {IDS_STRING3025}Could not start VSS Level=ERROR [0]
——————
This error (COM Error 0x80042316) means VSS_E_SNAPSHOT_SET_IN_PROGRESS. It indicates that a shadow copy is already in progress, and VSS cannot be used. This is a significant VSS error.
VSS_E_BAD_STATE ( 0x80042301 )
The backup components object is either not set up, called during a restore, or not in the correct sequence.
E_OUTOFMEMORY ( 0x8007000E )
Not enough memory or available system resources.
VSS_E_PROVIDER_VETO ( 0x80042306 )
The provider encountered an anticipated error, and the details are logged in the event log.
VSS_E_PROVIDER_IN_USE ( 0x80042307 )
The provider is in use.
VSS_E_OBJECT_NOT_FOUND ( 0x80042308 )
pwszVolumeName does not correspond to an existing volume or remote file share.
VSS_E_VOLUME_NOT_SUPPORTED ( 0x8004230c )
VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER ( 0x8004230e )
The volume or remote file share is not supported by the specified provider.
VSS_E_OBJECT_ALREADY_EXISTS ( 0x8004230d )
The object is a duplicate. A component with the same logical path and component name already exists.
VSS_E_UNEXPECTED_PROVIDER_ERROR ( 0x8004230f )
The provider gave an unexpected error code, which is only returned through the QueryStatus method on the IVssAsync interface in the ppAsync parameter.
VSS_E_INVALID_XML_DOCUMENT ( 0x80042311 )
The XML document is not valid. Check the event log for details.
VSS_E_MAXIMUM_NUMBER_OF_VOLUMES_REACHED ( 0x80042312 )
The maximum allowed volumes or remote file shares are already in the shadow copy set, and the specified one couldn't be added.
VSS_E_FLUSH_WRITES_TIMEOUT ( 0x80042313 )
The system couldn't flush I/O writes, possibly a temporary issue. It's advised to wait for ten minutes and retry, up to three times.
VSS_E_HOLD_WRITES_TIMEOUT ( 0x80042314 )
The system couldn't hold I/O writes, possibly a temporary issue. It's advised to wait for ten minutes and retry, up to three times.
VSS_E_UNEXPECTED_WRITER_ERROR ( 0x80042315 )
An unexpected error happened while communicating with writers. The error code is recorded in the error log file.
VSS_E_SNAPSHOT_SET_IN_PROGRESS ( 0x80042316 )
Another shadow copy creation is already underway. This happens when adding a CSV volume to a snapshot set from multiple nodes simultaneously or when adding a scale-out share to the snapshot set from multiple SMB client nodes simultaneously.
VSS_E_MAXIMUM_NUMBER_OF_SNAPSHOTS_REACHED ( 0x80042317 )
The maximum volumes or remote file shares allowed in the shadow copy set have been reached. The specified volume or remote file share couldn't be added to the shadow copy set.
VSS_E_WRITER_INFRASTRUCTURE ( 0x80042318 )
The writer infrastructure is not functioning correctly. Ensure that the Event Service and VSS are running, and check for related errors in the error log.
VSS_E_WRITER_NOT_RESPONDING ( 0x80042319 )
The writer is not responding.
VSS_E_UNSUPPORTED_CONTEXT ( 0x8004231b )
The context specified by lContext is not supported.
VSS_E_VOLUME_IN_USE ( 0x8004231d )
The volume couldn't be locked because the bForceDismount parameter was set to FALSE.
VSS_E_MAXIMUM_DIFFAREA_ASSOCIATIONS_REACHED ( 0x8004231e )
The volume couldn't be locked because the bForceDismount parameter was set to FALSE.
VSS_E_INSUFFICIENT_STORAGE ( 0x8004231f )
Insufficient storage space in the system or provider. Delete old or unnecessary persistent shadow copies and retry. This error code is only returned through the QueryStatus method on the IVssAsync interface in the ppAsync parameter.
VSS_E_REBOOT_REQUIRED ( 0x80042327 )
The provider encountered an error that requires the user to restart the computer.
Workarounds
For a VSS error, investigate the cause from the Windows event log, and so on.
Target Product
– ActiveImage Protector 3.5 / 2016 /2018 Windows
– ActiveImage Protector 4 / 5
(13451126405273)
Comments
0 comments
Article is closed for comments.