Enum VssError
The VssError enumeration represents error- and success codes that may be returned by some Vss methods.
Namespace: Alphaleonis.Win32.Vss
Assembly: AlphaVSS.Common.dll
Syntax
public enum VssError : uint
Fields
Name | Description |
---|---|
AsrCriticalDisksTooSmall | There is not enough disk space on the system to perform the restore operation. Add another disk or replace one of the existing disks and retry the restore operation. |
AsrDatadiskRdisk0 | A data disk is currently set as active in BIOS. Set some other disk as active or use the DiskPart utility to clean the data disk, and then retry the restore operation. |
AsrDiskAssignmentFailed | There are too few disks on this computer or one or more of the disks is too small. Add or change disks so they match the disks in the backup, and try the restore again. |
AsrDiskRecreationFailed | Windows cannot create a disk on this computer needed to restore from the backup. Make sure the disks are properly connected, or add or change disks, and try the restore again. |
AsrMissingDynamicDisk | The backup failed due to a missing disk for a dynamic volume. Please ensure the disk is online and retry the backup. |
AsrNoArcPath | The computer needs to be restarted to finish preparing a hard disk for restore. To continue, restart your computer and run the restore again. |
AsrRdisk0TooSmall | The disk that is set as active in BIOS is too small to recover the original system disk. Replace the disk with a larger one and retry the restore operation. |
AsrSharedCriticalDiskError | Automated System Recovery failed the shadow copy, because a selected critical volume is located on a cluster shared disk. This is an unsupported configuration. |
AsyncCanceled | The asynchronous operation was cancelled. |
AsyncFinished | The asynchronous operation was completed successfully. |
AsyncPending | The asynchronous operation is still running. |
BadState | A method call was made when the object was in an incorrect state for that method. |
BreakFailFromProvider | At least one of the providers in this Shadow Copy Set failed the break operation for a snapshot. |
BreakRevertIdFailed | The shadow copy set break operation failed because the disk/partition identities could not be reverted. The target identity already exists on the machine or cluster and must be masked before this operation can succeed. |
FlushWritesTimeout | The system was unable to flush I/O writes. This can be a transient problem. It is recommended to wait ten minutes and try again, up to three times. |
HoldWritesTimeout | The system was unable to hold I/O writes. This can be a transient problem. It is recommended to wait ten minutes and try again, up to three times. |
InsufficientStorage | The system or provider has insufficient storage space. If possible delete any old or unnecessary persistent shadow copies and try again. |
InvalidXmlDocument | The given XML document is invalid. It is either incorrectly-formed XML or it does not match the schema. |
LegacyProvider | This version of the hardware provider does not support this operation. |
MaximumDiffareaAssociationsReached | Maximum number of shadow copy storage associations already reached. |
MaximumNumberOfRemoteMachinesReached | The maximum number of remote machines for this operation has been reached. |
MaximumNumberOfSnapshotsReached | The volume has been added to the maximum number of shadow copy sets. The specified volume was not added to the shadow copy set. |
MaximumNumberOfVolumesReached | The maximum number of volumes has been added to the shadow copy set. The specified volume was not added to the shadow copy set. |
NoSnapshotsImported | No shadow copies were successfully imported. |
ObjectAlreadyExists | The object already exists. |
ObjectNotFound | The specified object was not found. |
ProviderAlreadyRegistered | The provider has already been registered. |
ProviderInUse | The shadow copy provider is currently in use and cannot be unregistered. |
ProviderNotRegistered | The specified identifier does not correspond to a registered provider. |
ProviderVeto | The provider was unable to perform the request at this time. This can be a transient problem. It is recommended to wait ten minutes and try again, up to three times. |
RebootRequired | The provider encountered an error that requires the user to restart the computer. Windows Server 2003 and Windows XP:This value is not supported until Windows Vista. |
RemoteServerUnavailable | The remote server is unavailable. |
RemoteServerUnsupported | The remote server is running a version of the Volume Shadow Copy Service that does not support remote shadow-copy creation. |
RevertInProgress | A revert is currently in progress for the specified volume. Another revert cannot be initiated until the current revert completes. |
RevertVolumeLost | The volume being reverted was lost during revert. |
SnapshotSetInProgress | Another shadow copy creation is already in progress. Please wait a few moments and try again. |
SomeSnapshotsNotImportedError | Some shadow copies were not succesfully imported. |
SomeSnapshotsNotImportedSuccess | Some shadow copies were not succesfully imported. |
Success | Indication of a successful operation. |
TransactionFreezeTimeout | The system was unable to freeze the Distributed Transaction Coordinator (DTC) or the Kernel Transaction Manager (KTM). Windows Server 2003 and Windows XP:This value is not supported until Windows Vista. |
TransactionThawTimeout | The system was unable to thaw the Distributed Transaction Coordinator (DTC) or the Kernel Transaction Manager (KTM). Windows Server 2003 and Windows XP:This value is not supported until Windows Vista. |
Unexpected | Unexpected error. The error code is logged in the error log file. |
UnexpectedProviderError | The provider returned an unexpected error code. This can be a transient problem. It is recommended to wait ten minutes and try again, up to three times. |
UnexpectedWriterError | VSS encountered problems while sending events to writers. |
UnsupportedContext | The shadow copy provider does not support the specified shadow copy type. |
VolumeInUse | The specified shadow copy storage association is in use and so can't be deleted. |
VolumeNotSupported | No VSS provider indicates that it supports the specified volume. |
VolumeNotSupportedByProvider | The volume is not supported by the specified provider. |
WriterAlreadySubscribed | The writer has already sucessfully called the Subscribe function. It cannot call subscribe multiple times. |
WriterErrorInconsistentSnapshot | The shadow copy contains only a subset of the volumes needed by the writer to correctly back up the application component. |
WriterErrorNonRetryable | The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. |
WriterErrorRecoveryFailed | The writer experienced an error while trying to recover the shadow-copy volume. |
WriterErrorRetryable | The writer failed due to an error that would likely not occur if the entire backup, restore, or shadow copy creation process was restarted. The recommended way to handle this error code is to wait ten minutes and then repeat the operation, up to three times. |
WriterInfrastructureError | An error was detected in the Volume Shadow Copy Service (VSS). The problem occurred while trying to contact VSS writers. Please verify that the Event System service and the VSS service are running and check for associated errors in the event logs. |
WriterNotResponding | A writer did not respond to a GatherWriterStatus call. The writer may either have terminated or it may be stuck. Check the system and application event logs for more information. |
WriterOutOfResources | The writer ran out of memory or other system resources. The recommended way to handle this error code is to wait ten minutes and then repeat the operation, up to three times. |
WriterStatusNotAvailable | The writer status is not available for one or more writers. A writer may have reached the maximum number of available backup and restore sessions. Windows Vista, Windows Server 2003, and Windows XP: This value is not supported. |
WriterTimeout | The writer operation failed because of a time-out between the Freeze and Thaw events. The recommended way to handle this error code is to wait ten minutes and then repeat the operation, up to three times. |