'ResB w& y y, wLogMessages1011121314151617181920212223242526272829303132333435363738394041424344Path {0} is not on {1}.{0} failed with error {1} for path {2}.5The provider [{0}] returned an unexpected error code.6The caller is out of memory or other system resources.7Couldnt find snapshot provider for provider type [{0}].7One of the parameter values is not valid for operation.>ProviderId [{0}] does not correspond to a registered provider.@Unexpected error. The error code is logged in the error log fileC{0} does not correspond to an existing volume or remote file share.EWriter[ {0} ] status is {1}, msg[ {2}]: The writer is not responding.HCouldnt fetch snapshot providers.Please check the logs for more details.HExpected provider error. The provider logged the error in the event log.NThe specified volume is nested too deeply to participate in the VSS operation.QThe caller does not have sufficient backup privileges or is not an administrator.QThe provider encountered an error that requires the user to restart the computer.QThe volume or remote file share is not supported by the specified provider [{0}].TVolume(s) {0} required for selected component {1} of writer {2} is/are not included.[No VSS provider indicates that it supports the specified volume or remote file share [{0}].jThe object [{0}] is a duplicate. A component with the same logical path and component name already exists.tThe system was unable to thaw the Distributed Transaction Coordinator (DTC) or the Kernel Transaction Manager (KTM).vThe system was unable to freeze the Distributed Transaction Coordinator (DTC) or the Kernel Transaction Manager (KTM).}The XML document is not valid. Check the event log for details. For more information, see Event and Error Handling Under VSS.܈The system or provider has insufficient storage space. If possible delete any old or unnecessary persistent shadow copies and try again.ܒ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.ܓ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.ܞBackup type of VM is OFFLINE and configuration parameter [allowOfflineBackup] is not set. To backup this VM, set [allowOfflineBackup] configuration parameter.ܢWriter[ {0} ] status is {1}, msg[ {2}]: The shadow copy contains only a subset of the volumes needed by the writer to correctly back up the application component.ܨThe backup components object is not initialized, this method has been called during a restore operation, or this method has not been called within the correct sequence.ܩThe volume or remote file share has been added to the maximum number of shadow copy sets. The specified volume or remote file share was not added to the shadow copy set.ܫThe maximum number of volumes or remote file shares have been added to the shadow copy set. The specified volume or remote file share was not added to the shadow copy set.ܲThe writer infrastructure is not operating properly. Check that the Event Service and VSS have been started, and check for errors associated with those services in the error log.ܷThe creation of a shadow copy is in progress, and only one shadow copy creation operation can be in progress at one time. Either wait to try again or return with a failure error code.ܺWriter[ {0} ] status is {1}, msg[ {2}]: 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.String To CLSID conversion failed. Either class string was improperly formatted, or CLSID corresponding to the class string was not found in the registry, or registry could not be opened for reading.Writer[ {0} ] status is {1}, msg[ {2}]: The writer operation failed because of an error that might recur if another shadow copy is created. For more information, see Event and Error Handling Under VSS.Writer[ {0} ] status is {1}, msg[ {2}]: 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.Writer[ {0} ] status is {1}, msg[ {2}]: 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.*Writer[ {0} ] status is {1}, msg[ {2}]: 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.,,/258;>ADGJMPSVY\_behknqtwz}x{~x# : O'   F 0"z g,LbcA PI