Windows / Modules / VSSVC.exe

VSSVC.exe

Associated Error Codes

Below lists error codes and symbolic names found for this module.

CodeFound inDescription
0x11011Volume Shadow Copy Service initialization error: the control dispatcher cannot be started [%1]. %2
0x21011Volume Shadow Copy Service initialization error: the control handler cannot be registered [%1]. %2
0x31011Volume Shadow Copy Service initialization error: the COM library cannot be initialized [%1]. %2
0x41011Volume Shadow Copy Service initialization error: the COM security cannot be initialized [%1]. %2
0x51011Volume Shadow Copy Service initialization error: could not retrieve backup/restore privilege [%1]. %2
0x61011Volume Shadow Copy Service initialization error: the COM classes cannot be registered [%1]. %2
0x71011Volume Shadow Copy Service initialization error: [%1]. %2
0x81011Unexpected error when changing the SCM status of the Volume Shadow Copy Service: [%1, %2]. %3
0x91011Volume Shadow Copy Service information: Service starting at request of process '%1'. [%2] %3
0xa1011Volume Shadow Copy Service information: Volume '%1' appears as disconnected and it is ignored by the service. You may want to rescan disks. [%2] %3
0xb1011Volume Shadow Copy Service information: The COM Server with CLSID %1 and name %2 cannot be started. Most likely the CPU is under heavy load. [%3] %4
0xc1011Volume Shadow Copy Service information: The COM Server with CLSID %1 and name %2 cannot be started. Most likely the server is in the process of shutting down or the system is out of memory. [%3] %4
0xd1011Volume Shadow Copy Service information: The COM Server with CLSID %1 and name %2 cannot be started. [%3] %4
0xe1011Volume Shadow Copy Service information: A database of hardware snapshots was created. %1
0xf1011The user name %1 specified in registry (%2) does not map to a real user name. The entry is ignored. It must have a valid username as name, be of type REG_DWORD, and value either '0' or '1'. %3
0x101011The value with name %1 specified in registry (%2) is not of type REG_DWORD. The entry is ignored. It must have a valid username as name, be of type REG_DWORD, and value either '0' or '1'. Value '0' denies the username from running any VSS writer. Value '1' is used to allow it. %3
0x111011The value with name %1 specified in registry (%2) of value (%3) cannot be interpreted. The entry is ignored. It must have a valid username as name, be of type REG_DWORD, and value either '0' or '1'. Value '0' denies the username from running any VSS writer. Value '1' is used to allow it. %4
0x121011Volume Shadow Copy Service error: The COM Server with CLSID %1 and name %2 cannot be started during Safe Mode. The Volume Shadow Copy service cannot start while in safe mode. [%3] %4
0x131011Volume Shadow Copy Service error: The EventSystem service is disabled or is attempting to start during Safe Mode. The Volume Shadow Copy service cannot start while in safe mode. If not in safe mode, make sure that EventSystem service is enabled. CLSID:%1 Name:%2 [%3] %4
0x141011Volume Shadow Copy Service error: The Volume Shadow Copy infrastructure cannot be used during Safe Mode. %1
0x151011Volume Shadow Copy Service error: Writers will not receive events since the COM+ database is corrupted. This might happened if an error occurred during Windows setup. The error returned from CoCreateInstance on class with CLSID %1 and Name %2 is [%3] %4
0x161011Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID %1 and Name %2 is [%3]. %4
0x171011The value specified in registry (%1) has no name. The entry is ignored. It must have a valid username as name, be of type REG_DWORD, and value either '0' or '1'. Value '0' denies the username from running any VSS writer. Value '1' is used to allow it. %2
0x181011Volume Shadow Copy Service Warning: The Volume Shadow Copy Service is shutting down and is experiencing delay while waiting for in-progress calls to complete. %1
0x191011Volume Shadow Copy Service Warning: The Microsoft Shadow Copy Provider is shutting down and is experiencing delay while waiting for in-progress calls to complete. %1
0x1a1011This machine is a Domain Controller with the Active Directory service (NTDS) stopped. Backup cannot be performed, nor can shadow copies be managed in this case. Either the NTDS must be started (net start ntds), or reboot in DSRM to enumerate shadow copies/providers/writers only. %1
0x1b1011This machine is a Domain Controller but the Active Directory (NTDS) service is stopped. Restore cannot be performed while NTDS is stopped. Either the NTDS must be started (net start ntds), or reboot in DSRM. %1
0x1c1011The given type for the ApplicationsBlockingRevert key (%1) is incorrect. It must be a REG_MULTI_SZ containing a sequence of null-terminated volume GUID strings specifying volumes blocked from revert, followed by an extra null termination. %2
0x1d1011This machine is a Domain Controller in Directory Service Restore Mode (DSRM). Backup cannot be performed in this case, please reboot out of DSRM. %1
0x1e1011Fail to acquire Security Audit privilege. Security Audits for shadow copy creation and import will not be logged. %1
0x1f1011Volume Shadow Copy Service Warning: A writer with name %1 and ID %2 waited %3 seconds for in-progress calls to complete before shutting down. %4
0x201011Volume Shadow Copy Service error: The VSS Coordinator class is not registered. This may be caused due to a setup failure or as a result of an application's installer or uninstaller. %1
0x211011Volume Shadow Copy Service error: The VSS management class is not registered. This may be caused due to a setup failure or as a result of an application's installer or uninstaller. %1
0x221011Volume Shadow Copy Service error: The VSS event class is not registered. This will prevent any VSS writers from receiving events. This may be caused due to a setup failure or as a result of an application's installer or uninstaller. %1
0x241011Volume Shadow Copy Service error: The MSXML classes are not registered. This may be caused due to a setup failure or as a result of an application's installer or uninstaller. %1
0x251011Volume Shadow Copy Service error: The Microsoft Shadow Copy Provider class is not registered.. This may be caused due to a setup failure or as a result of an application's installer or uninstaller. %1
0x261011Volume Shadow Copy Service error: Either the COM+ Event System service (EventSystem) or the COM+ System Application service (COMSysApp) is disabled. Enable the service and try again. %1
0x271011Volume Shadow Copy Service error: The Volume Shadow Copy service (VSS) is disabled. Enable the service and try again. %1
0x281011Volume Shadow Copy Service error: The Microsoft Software Shadow Copy Provider (SWPRV) service is disabled. Enable the service and try again. %1
0x2c1011Volume Shadow Copy Service information: Disk '%1' appears as disconnected and it is rejected by the service. You may want to rescan disks. [%2] %3
0x2d1011Volume Shadow Copy Service information: Volume '%1' appears as disconnected and it is ignored by the service. You may want to rescan disks. [%2] %3
0xfa11011Volume Shadow Copy Service error: Cannot find diff areas for creating shadow copies. Add at least one NTFS drive to the system with enough free space. The free space needed is at least %1 Mb for each volume to be shadow copied. %2
0xfa21011Volume Shadow Copy Service error: Cannot create multiple shadow copies on the same volume (%1) %2
0xfa31011Volume Shadow Copy Service warning: Writer received a Freeze event more than two minutes ago. The writer is still waiting for either an Abort or a Thaw event. %1
0xfa41011Volume Shadow Copy Service warning: The sector size of the diff area volume %1 cannot be larger than the sector size of the original volume %2 %3
0x10011011Volume Shadow Copy Service error: The COM+ Admin catalog instance cannot be created [%1]. %2
0x10021011Volume Shadow Copy Service error: Cannot install the event class %1 into the COM+ application '%2' [%3]. %4
0x10031011Volume Shadow Copy Service error: Cannot install the component %1 into the COM+ application '%2' [%3]. %4
0x10041011Volume Shadow Copy Service error: Cannot create service '%1' for the COM+ application '%2' [%3]. %4
0x10051011Volume Shadow Copy Service error: Cannot obtain the collection '%1' from the COM+ catalog [%2]. %3
0x10061011Volume Shadow Copy Service error: Cannot populate the COM+ collection '%1' [%2]. %3
0x10071011Volume Shadow Copy Service error: Cannot get the COM+ collection key [%1]. %2
0x10081011Volume Shadow Copy Service error: Cannot get the COM+ collection '%1' from parent [%2]. %3
0x10091011Volume Shadow Copy Service error: Cannot save the changes for the COM+ collection [%1]. %2
0x100a1011Volume Shadow Copy Service error: Cannot create a subscription (%1,%2,%3) [%4]. %5
0x100b1011Volume Shadow Copy Service error: Cannot attach to the subscription with name (%1) [%2]. %3
0x100c1011Volume Shadow Copy Service error: Cannot remove the subscription with index %1 [%2]. %3
0x100d1011Volume Shadow Copy Service error: Cannot insert the new object into the COM+ catalog [%1]. %2
0x100e1011Volume Shadow Copy Service error: Cannot attach the catalog object to the COM+ application [%1]. %2
0x100f1011Volume Shadow Copy Service error: Cannot attach to the subscription with name (%1) [%2]. %3
0x10101011Volume Shadow Copy Service error: Error getting current directory [%1]. %2
0x10111011Volume Shadow Copy Service error: Error Removing COM+ application (%1) [%2]. %3
0x177f1011Jetwriter error: a call to Jet function %1 failed with status = %2. %3
0x17801011Express Writer error: failed while adding express writers from directory %1. %2
0x1b591011VssAdmin: %1: %2 Command-line: '%3'. %4
0x20011011Volume Shadow Copy Service error: Unexpected error calling routine %1. hr = %2. %3
0x20021011Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = %1. This is often caused by incorrect security settings in either the writer or requestor process. %2
0x20031011Volume Shadow Copy Service error: Internally transferred WRITER_COMPONENTS document is invalid. %1
0x20041011Volume Shadow Copy Service error: No volumes in the shadow copy set. %1
0x20051011Volume Shadow Copy Service error: ERROR_INSUFFICIENT_BUFFER expected error. Actual Error was [%1]. %2
0x20061011Volume Shadow Copy Service error: Unexpected error. Final buffer for call to GetTokenInformation was size = %1, original size was %2. %3
0x20071011Volume Shadow Copy Service error: Unexpected error performing QueryInterface from IXMLDOMNode to IXMLDOMElement. hr = %1. %2
0x20081011Volume Shadow Copy Service error: An unexpected error was encountered examining the XML document. The document is missing the %1 element. %2
0x20091011Volume Shadow Copy Service error: An unexpected error was encountered examining the XML document. The document is missing the %1 attribute. %2
0x200a1011Volume Shadow Copy Service error: An unexpected error was encountered when QueryInterface for IDispatch was called. hr = %1 attribute. %2
0x200b1011Volume Shadow Copy Service error: An unexpected error was encountered cloning a document. The cloned document has no children. %1
0x200c1011Volume Shadow Copy Service error: An invalid XML document was returned from writer %1. %2
0x200d1011Volume Shadow Copy Service error: An error occured calling QueryInterface from IVssCoordinator to IVssShim. hr = %1.
0x200e1011Volume Shadow Copy Service error: There are two writers with the identical instance id %1. %2
0x200f1011Volume Shadow Copy Service error: An unexpected error was encountered when calling QueryInterface for IVssAsync. hr = %1. %2
0x20101011Volume Shadow Copy Service error: The backup components document is NULL. %1
0x20111011Volume Shadow Copy Service error: The thread handle for the asynchronous thread is NULL. %1
0x20121011Volume Shadow Copy Service error: Unexpected error %1 was returned from WaitForSingleObject. %2
0x20131011Volume Shadow Copy Service error: Writer with name %1 and ID %2 attempted to subscribe in safe mode. %3
0x20141011Volume Shadow Copy Service: Writer with name %1 and ID %2 attempted to subscribe during setup. %3
0x20151011Volume Shadow Copy Service error: The process that hosts the writer with name %1 and ID %2 does not run under a user with sufficient access rights. Consider running this process under a local account which is either Local System, Administrator, Network Service, or Local Service. %3
0x20161011Volume Shadow Copy Service error: The shadow copy writer could not communicate with the Shadow Copy publisher. The shadow copy publisher (for example the backup application) might have terminated during the shadow copy process. hr = %1. %2
0x20171011Volume Shadow Copy Service error: A component was added to the backup document that does not exist in any writer's metadata. Ensure that only actual writer components are added to the backup document. %1
0x20181011Volume Shadow Copy Service error: Internally transferred WRITER_METADATA document is invalid. %1
0x20191011Volume Shadow Copy Service error: VSS only supports multiple instances of writer with class id %1 if the writer either does not require restore events or supplies an instance name. %2
0x201a1011Two instances of writer with class id %1 attempted to register with the same instance name %2. %3
0x201b1011Ran out of time while expanding file specification %1\%2. This was being done for the %3 subscriber. %4
0x201c1011Ran out of time while deleting files. %1
0x201d1011The Backup Components XML document was rejected. In this case the reason could be that it is not a Backup Components Document from a transportable shadow copy. %1
0x201e1011Shadow copy has been created. User SID: %1 User name: %2 Process ID: %3 Process image name: %4 Shadow Set ID: %5 Shadow ID: %6 Provider ID: %7 Original Machine: %8 Original Volume: %9 Shadow device name: %10
0x201f1011Hardware shadow copy imported. User SID: %1 User name: %2 Process ID: %3 Process image name: %4 Shadow Set ID: %5 Shadow ID: %6 Provider ID: %7 Original Machine: %8 Original Volume: %9 Shadow device name: %10
0x20201011The VSS service is shutting down due to idle timeout. %1
0x20211011The VSS service is shutting down due to shutdown event from the Service Control Manager. %1
0x20221011Ran out of time while expanding file specifications. Shadow copy optimization is partial. %1
0x20231011The user name %1 specified in registry (%2) is not valid, winerror %3. The entry is ignored. It must have a valid username as name, be of type REG_DWORD, and value either '0' or '1'. %4
0x20241011Fail to parse XML file. Reason %1 Line %2 Position %3 Errorcode %4 Problem text %5 %6
0x20251011A VSS writer has rejected an event with error %1. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. %2
0x20261011Volume Shadow Copy Service error: Failed resolving account %1 with status %2. Check connection to domain controller and VssAccessControl registry key. %3
0x30011011Volume Shadow Copy Service error: Unexpected error %1. hr = %2. %3
0x30021011Volume Shadow Copy Service warning: %1. hr = %2. %3
0x30031011Volume Shadow Copy Service error: Error on creating/using the COM+ Writers publisher interface: %1 [%2]. %3
0x30041011Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID %1 [%2]. %3
0x30051011Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider %1. Routine details %2 [hr = %3]. %4
0x30061011Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider %1. Routine returned E_INVALIDARG. Routine details %2. %3
0x30071011Volume Shadow Copy Service error: Wrong type %1 (should be %2) for the Registry value %3 under the key %4. %5
0x30081011Volume Shadow Copy Service error: The system may be low on resources. Unexpected error at background thread creation (_beginthreadex returns %1, errno = %2). %3
0x30091011Volume Shadow Copy Service error: The I/O writes cannot be flushed during the shadow copy creation period on volume %1. The volume index in the shadow copy set is %2. Error details: Open[%3], Flush[%4], Release[%5], OnRun[%6]. %7
0x300a1011Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume %1. The volume index in the shadow copy set is %2. Error details: Open[%3], Flush[%4], Release[%5], OnRun[%6]. %7
0x300b1011Volume Shadow Copy Service error: One of the shadow copy providers returned an invalid number of committed shadow copies. The expected number of committed shadow copies is %1. The detected number of committed shadow copies is %2. %3
0x300c1011Volume Shadow Copy Service error: Writer %1 called CVssWriter::Initialize during Setup. %2
0x300d1011Volume Shadow Copy Service error: Writer %1 did not respond to a GatherWriterStatus call. %2
0x300e1011Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. Check to see that the Event Service and Volume Shadow Copy Service are operating properly. %1
0x300f1011An error occurred calling CoSetProxyBlanket. hr = %1 %2
0x30101011An error occurred trying to QI the IVssWriter event object for IMultiInterfaceEventControl. hr = %1 %2
0x30111011Volume Shadow Copy Service error: Volume/disk not connected or not found. Error context: %1. %2
0x30121011Database of hardware shadow copy sets is not valid. Contents are ignored. %1
0x30131011Cannot save database of hardware shadow copy sets: hr = %1. %2
0x30141011Volume %1 appears to be invalid or dismounted during shadow copy creation. %2
0x30151011VSS Assert Failure: %1 %2
0x30161011Volume Shadow Copy Service error: The shadow copy could not be committed - operation timed out. Error context: %1. %2
0x30171011Volume Shadow Copy Service error: Unexpected error %1: %2 hr = %3. %4
0x30181011Database of remote shadow copy sets is not valid. Contents are ignored. %1
0x30191011New database of remote shadow copy sets was created by the Volume Shadow Copy Service. %1
0x301a1011Cannot save database of remote shadow copy sets: hr = %1. %2
0x301b1011Database of remote shadow copies is not valid. Contents are ignored. %1
0x301c1011New database of remote shadow copies was created by the Volume Shadow Copy Service. %2
0x301d1011Cannot save database of remote shadow copies: hr = %1. %2
0x301e1011Failed to query machine %1 for shadow copies: hr = %2. Machine is skipped. %3
0x301f1011Failed to connect to remote machine %1 for shadow copies management. Remote machine is unavailable: hr = %2. Make sure that this remote machine and the local machine are both on the network. %3
0x30201011Failed to connect to remote machine %1 for shadow copies management. Remote machine denies access: hr = %2. Make sure that the account running your local Volume Shadow Copy service is authorized for shadow copy management on the remote machine. %3
0x30211011Failed to connect to remote machine %1 for shadow copies management. Remote machine is unsupported: hr = %2. This error indicates that the remote machine does not support shadow copies for shares. A common cause for this error is that the remote machine is running a Windows version which doesn't support this capability. %3
0x30221011Revert operation for volume %1 has begun. Volume is being reverted to the shadow copy with id %2. %3
0x30231011Volume Shadow Copy Warning: A timeout was encountered while trying to freeze the Kernel Transaction Manager. This means that one or more Resource Managers failed to commit within %1 seconds. Check the System event log for more information. %2
0x30241011Volume Shadow Copy Warning: A timeout was encountered while trying to thaw the Kernel Transaction Manager. This means that the shadow-copy creation process took longer than %1 seconds. %2
0x30251011Volume Shadow Copy Warning: A timeout was encountered while trying to freeze the Distributed Transaction Manager. This means that one or more Transaction Managers failed to commit within %1 seconds. Check the event logs for more information. %2
0x30261011Volume Shadow Copy Warning: A timeout was encountered while trying to thaw the Distributed Transaction Manager. This means that the shadow-copy creation process took longer than %1 seconds. %2
0x30271011Volume Shadow Copy Warning: A timeout occured while trying to take the cluster resource %1 offline. This means that taking the resource offline took longer than %2 seconds. %3
0x30281011Volume Shadow Copy Warning: A timeout occurred while trying to bring the cluster resource %1 online. This means that bringing the resource offline took longer than %2 seconds. %3
0x30291011Volume Shadow Copy Warning: A plug-and-play devnode could not be found for the volume while attempting to restart or remove the associated device. The function GetHiddenVolumeDevinfo failed with %1. The operation will be continue, however some state associated with this volume may not be cleaned up. %2
0x302a1011Volume Shadow Copy Warning: The hardware shadow-copy volume %1 disappeared unexpectedly. Check for any event logs reported by Plug And Play, by the hardware provider, or by volsnap. %2
0x302b1011Volume Shadow Copy: Attempt to dismount the volume failed with %1. Check the system event log for more information. %2
0x302c1011Volume Shadow Copy Warning: The provider has reported an invalid Storage Device ID structure. %1
0x302d1011Volume Shadow Copy Warning: The provider has reported a storage identifier that is not supported by VSS. Codeset: %1 Type: %2 Size: %3 NextOffset: %4 Association: %5 This identifier will be skipped by VSS. %6
0x30311011Volume Shadow Copy Error: After restarting the device %1, Plug and Play reports that a reboot is required. This is an unexpected situation. %3
0x30321011Volume Shadow Copy Error: VSS spent more than %1 seconds trying to open and flush all the volumes in the shadow- copy set. This caused volume %2 to timeout waiting for the hold-writes phase of shadow-copy creation. Trying again when disk activity is lower may solve this problem. %3
0x30331011Volume Shadow Copy Warning: VSS spent %1 seconds trying to open and flush the volume %2. This might cause timeouts while flushing other volumes in the shadow-copy set, causing the shadow-copy creation to fail. Trying again when disk activity is lower may solve this problem. %3
0x30341011Volume Shadow Copy Error: VSS waited more than %1 seconds for all volumes to be flushed. This caused volume %2 to timeout while waiting for the release-writes phase of shadow copy creation. Trying again when disk activity is lower may solve this problem. %3
0x30351011Volume Shadow Copy Warning: VSS spent %1 seconds trying to flush and hold the volume %2. This might cause problems when other volumes in the shadow-copy set timeout waiting for the release-writes phase, and it can cause the shadow-copy creation to fail. Trying again when disk activity is lower may solve this problem. %3
0x30361011Volume Shadow Copy Error: An error %1 was encountered while trying to initialize the Registry Writer. This may cause future shadow-copy creations to fail. %2
0x30371011Volume Shadow Copy Error: An error %1 was encountered while Registry Writer was attempting to initialize itself. This may case a shadow-copy creation to fail. Check the Application event log for any related errors. %2
0x30381011Volume Shadow Copy Error: An error %1 was encountered while Registry Writer was preparing the registry for a shadow copy. Check the Application and System event logs for any related errors. %2
0x30391011Volume Shadow Copy Error: The Registry Writer experienced an out-of-space condition while preparing the registry for a Shadow Copy. Check the Application and System event logs for any related errors. %1
0x303a1011Volume Shadow Copy Error: An error %1 was encountered while trying to initialize the Registry Writer. This may cause future shadow-copy creations to fail. %2
0x303b1011Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. The Registry Writer failed to respond to a query from VSS. Check to see that the Event Service and Volume Shadow Copy Service are operating properly, and please check the Application event log for any other events. %1
0x303c1011Volume Shadow Copy Service warning: VSS was denied access to the root of volume %1. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly. Check security on the volume, and try the operation again. %2
0x303d1011Volume Shadow Copy Service warning: The writer spent too much time processing it's Freeze notification. This can cause this writer as well as other writers on the system time to time out and fail shadow-copy creation. %1
0x303e1011When snapshot volume %1 was restarted in the system, the restart failed. The volume is no longer found in the system. Try a rescan from Diskmgmt.msc and see if the volume appears. If not, try restarting the disk device then rescan. %2
0x30401011Fail to revert the signature of %1 . %2
0x30411011Failed to set the mount point %1 for volume %2, winerror %3 %4
0x30421011Failed to set the share %1 after break, netstatus %2. %3
0x30431011Cannot request the shadow copy volume to be made readwrite if mask is requested. %1
0x30441011Cannot force signature revert if no signature revert is requested. %1
0x30451011The BreaksnapshotSetEx method failed because the disk signature of one or more shadow copy LUNs could not be reverted to those of the original LUNs. If one or more original LUNs are not masked on the computer, this can cause a disk signature collision. Disk signatures of dynamic disks cannot be reverted. %1
0x30461011The requester specified the VSS_ONLUNSTATECHANGE_DO_MASK_LUNS flag when calling the BreakSnaphsotSetEx method, but the hardware provider for this shadow copy does not implement the IVssHardwareSnapshotProviderEx interface. %1
0x30491011Provider %1 failed BreakSnapshotSetEx for Snapshot Set %2 with %3. %4
0x304a1011A Shadow Copy LUN was not detected in the system and did not arrive. LUN ID %1 Version %2 Device Type %3 Device TypeModifier %4 Command Queueing %5 Bus Type %6 Vendor Id %7 Product Id %8 Product Revision %9 Serial Number %10 Storage Identifiers %11 %12
0x304b1011An expected hidden volume arrival did not complete because this LUN was not detected. LUN ID %1 Version %2 Device Type %3 Device TypeModifier %4 Command Queueing %5 Bus Type %6 Vendor Id %7 Product Id %8 Product Revision %9 Serial Number %10 Storage Identifiers %11 %12
0x304c1011An expected volume arrival did not complete because this LUN was not detected. LUN ID %1 Version %2 Device Type %3 Device TypeModifier %4 Command Queueing %5 Bus Type %6 Vendor Id %7 Product Id %8 Product Revision %9 Serial Number %10 Storage Identifiers %11 %12
0x304e1011An unhandled exception was encountered while processing a VSS writer event callback method. The VSS writer infrastructure is in an unstable state. Restart the service or application that hosts the writer. Writer name: %1 Writer id: %2 Writer instance: %3 Process command line: %4 Process ID: %5 Writer operation: %6 Writer state: %7 Exception code: %8 Exception location: %9
0x30521011The hardware provider for this shadow copy does not support LUN resynchronization. %1
0x30551011The Volume Shadow Copy Service was unable to load the provider with identifier %1. Reinstall the provider and retry the operation. If the provider still fails to load, please contact the vendor responsible for that provider. %2
0x30561011The destination LUN could not be resynchronized from the source volume because it did not report a unique SCSI storage storage identifier of type 1, 2, 3, or 8 and association 0. Retry the operation with a different destination LUN. %1
0x30571011The resynchronization operation failed because the MBR signature or GPT ID of one or more of the destination LUNs could not be changed. If the affected destination LUNs have incorrect signatures, this might cause associated disk cluster resources to remain offline. %1
0x30591011The following destination LUN could not be restarted after the LUN resynchronization operation. Retry the operation. LUN ID %1 Version %2 Device Type %3 Device TypeModifier %4 Command Queueing %5 Bus Type %6 Vendor Id %7 Product Id %8 Product Revision %9 Serial Number %10 Storage Identifiers %11 %12
0x305a1011The LUN resynchronization operation failed because the destination disk could not be found or because another application holds an exclusive handle to the destination LUN. Make sure that all applications have released their handles to the LUN and retry the operation. %1
0x305d1011The LUN resynchronization operation failed because the Volume Shadow Copy Service was unable to enumerate the cluster resources. The Cluster service returned the following error %1. Check the system event log for events related to the Cluster service. %2
0x305f1011The LUN resynchronization operation failed because one or more destination LUNs could not be placed in maintenance mode. Check the system event log for events related to the Cluster service. %1
0x30601011The LUN resynchronization operation failed because one or more destination LUNs could not be removed from maintenance mode. Check the system event log for events to the Cluster service. %1
0x30621011The LUN resynchronization operation failed because volume %1 on destination disk %2 is not included in the recovery set. Include the missing volume and a corresponding shadow copy to the recovery set, or force the resynchronization by using the VSS_RECOVERY_NO_VOLUME_CHECK flag. %3
0x30631011Resynchronization of a Shadow Copy to a destination disk has completed. User SID: %1 User name: %2 Process ID: %3 Process image name: %4 Provider ID: %5 Source Shadow Copy: %6 Pre-Resync Volume: %7 Pre-Resync Disk no: %8 Post-Resync Volume: %9 Post-Resync Disk no: %10
0x30651011The LUN resynchronization operation failed before calling the hardware provider. As a result, some destination LUNs may be offline. To retry the resynchronization, bring the destination LUNs online and retry the operation. %1
0x30661011The LUN resynchronization operation failed during a call to the hardware provider. The destination LUNs are in an unknown state, and their contents should be discarded. To retry the resynchronization, repair the destination LUNs if needed, bring them online, and retry the operation. %1
0x30671011The LUN resynchronization operation failed after calling the hardware provider. The data on the destination LUNs is probably intact. However, the LUNs may have incorrect disk signatures. To retry the resynchronization, recreate the destination LUNs and retry the operation. %1
0xa0011011ASR Warning: Failed to collect disk information for ASR Backup. Reason: Unable to obtain disk information for device %1 (Win32 error code %2).
0xa0021011ASR Error: Fail to exclude disk #%1. Reason: The disk contains a critical volume.
0xa0031011ASR Error: Fail to exclude dynamic pack. Reason: Some, but not all, dynamic disks in the pack have been marked excluded.
0xa0041011ASR Error: Fail to include critical Virtual Hard Disk (VHD) #%1. Reason: The specified VHD is hosted on another VHD.
0xa0051011ASR Error: Fail to include critical dynamic pack. Reason: The dynamic pack consists of a Virtual Hard Disk (VHD) #%1.
0xb0011011Select to include disk #%1 (of signature %2) for ASR restore.
0xb0021011Select to include disk #%1 (raw disk) for ASR restore.
0xb0031011Select this volume (%1) if it is a critical volume. Critical volumes are those which ASR must restore.
0xb0041011This is the path to the boot BCD store and the boot managers. All the files in this directory need to be backed up.
0xb0051011Disk #%1 is a virtual disk.
0x202711Volume Shadow Copy Service information: Snapshot creation initiated for Snapshot Set %1. Process command line: %2 Process Caller Stack: Process[0]: %3 Process[1]: %4 Process[2]: %5
199 entries