Mini Kabibi Habibi

Current Path : C:/Windows/System32/en-US/
Upload File :
Current File : C:/Windows/System32/en-US/vsstrace.dll.mui

MZ����@���	�!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!~

��f@ �z8.rdata�@@.rsrc� |@@�Q؍
T88�Q؍$��8.rdata8x.rdata$zzzdbg p.rsrc$01p$Xv.rsrc$02 DL��M|ObJ��%YU�@���SN���Q؍`�0�H�����0�
H�`�x����������� �9 �:8�;P�?h�x��y������������		 	0	@	P	`	p	�	�	�	�	�	�	�	�			 	0	@	Ph$�� %���%~�H'�T*���+���,��@/��3D�X7���8���:��;���=4��=>��=�A���Af�,D���G�N�����MUI���+G�����e�d�!�[�l�!�&�?5��H����MUIen-US
Operation:Context:Error-specific details:Failure:Error
Unknown errorPA Executing Asynchronous OperationCancel Asynchronous OperationQuery Asyncronous OperationInitialize For BackupInitialize For RestoreLoad XML documentWriter Getting Backup StatePAWriter Getting Restore StatePrepareForBackup eventAbort BackupInstantiating VSS serverGather writers' statusBackupComplete EventPreRestore EventPostRestore EventWriter Getting Backup Document*Writer Modifying Modifying Backup DocumentWriter Getting XML ContentWriter Exposing its StateWriter Exposing its MetadataProcessing Writer DataGathering Writer DataInitializing WriterAborting WriterMonitoring Freeze TimeoutPrepareForSnapshot EventFreeze Event
Thaw EventPostSnapshot EventBackupShutdown EventSubscribing Writer/Adding Express Writers from metadata repositoryPASet Snapshot ContextStart a Shadow Copy Set!Add a Volume to a Shadow Copy SetTake a Shadow CopyDelete Shadow CopiesQuery Shadow CopiesBreak a Shadow Copy setPrepare for Fast RecoveryPerform Fast RecoveryImport Shadow CopiesGet Shadow Copy Properties(Check If Volume Is Supported by ProviderExpose a Shadow CopyUnexpose a Shadow CopyRevert a Shadow Copy*Prepare a Volume to Add to Shadow Copy Set(Checking whether volume is shadow copiedRegistering ProviderUnregistering Provider&Creating instance of hardware providerProcessing BeginPrepareSnapshotProcessing EndPrepareSnapshotsProcessing PreCommitSnapshotsProcessing PostCommitSnapshots"Processing PreFinalCommitSnapshots#Processing PostFinalCommitSnapshotsProcessing AbortSnapshots'Processing a shadow-copy volume removal#Removing auto-release shadow copies+Notifying hardware provider to free a driveRemoving dynamic disksPALocating shadow-copy LUNs#Listing the system's hidden volumesPerforming a PNP rescanFinalizing shadow-copy import'Obtaining provider management interface(Query volumes supported by this provider'Query shadow copies on the given volume!Obtain the minimum diff-area size)Automatically choosing a diff-area volumeAdding a diff-area associationChanging diff-area maximum size"Query volumes usable as diff areasQuery diff area for this volumeQuery diff areas on this volume%Query diff areas for this shadow copy Upgrading diff-area associationsQuerying revert statusCommitting shadow copiesLoading providerUnloading provider-Obtain a callable interface for this provider9List interfaces for all providers supporting this contextOnIdentify eventPrepareForBackup eventPrepareForSnapshot eventOnFreeze eventOnThaw eventOnPostSnapshot event
OnAbort eventOnBackupComplete eventOnBackupShutdown eventOnPreRestore eventOnPostRestore event
Current StateWriter Instance IDWriter Class IdWriter NameWriter Instance NameComponent Logical PathComponent Name	File Path	File NameProvider IDVolume NameWriter Instance NameExecution ContextSnapshot ContextSnapshot IDClass ID
Provider NameProvider VersionDiff-area volumeDiff-area maximum sizeServer Name
Database Name
Instance NameCommand LinePA
Process IDFile Share NamePA%Setting volume protection level to %d Getting volume protection status Clearing volume protection faultDeleting unused diff area files0Break a Shadow Copy set using BreakSnapshotSetExSnapshot Set IDDevicePerform TxF RecoveryNoneExposing DisksExamining Detected DiskExposing Volumes Examining Detected Hidden VolumeExposing Recovered VolumesExamining Detected VolumeBreak input flagsBreak with LUN mask)Break with signature change and reinstallDeleting VolumePAAdding snapshot to recovery setHardware Shadow Copy Resync'Exposing volumes after Resync operation"Examine arrived volume post-resync6Correcting disk MBR signatures or GPT IDs after resyncFail to get the post-resync IDFail to find the pre-resync ID.Desired ID conflicts with a pre-resync Disk IDPAFail to revert the disk IDCould not find original disk ID,The desired ID already exists on the machineAdding destination volumeCannot refresh properties%Exposing disks after Resync operation'Restarting disks after Resync operationFailed to restart disk Disk found to be unusable 3Offlining destination disks before Resync operation0Enumerating clustered disk resources for Resync Failed Maintenance Mode &Logging Security Audits for LUN ResyncDisk number		##p!#!#�#�#��#�#��#�#�h#�/#�x6#�6#��!�#�
$�`"$�$��>XThe asynchronous operation is pending.

\The asynchronous operation has completed.

hThe asynchronous operation has been cancelled.

pSome shadow copies were not successfully imported.

�A function call was made when the object was in an incorrect state

for that function

A Volume Shadow Copy Service component encountered an unexpected error.

Check the Application event log for more information.

\The provider has already been registered.

�The volume shadow copy provider is not registered in the system.

�The shadow copy provider had an error. Check the System and Application event logs for more information.

�The shadow copy provider is currently in use and cannot be unregistered.

PThe specified object was not found.

tShadow copying the specified volume is not supported.

@The object already exists.

�The given shadow copy provider does not support shadow copying the specified volume.

�The shadow copy provider had an unexpected error while trying to process the specified operation.

The given XML document is invalid.  It is either incorrectly-formed XML or it does not match the

schema.  This error code is deprecated.

�The given XML document is invalid.  It is either incorrectly-formed XML or it does not match the

schema.

�The maximum number of volumes for this operation has been reached.

�The shadow copy provider timed out while flushing data to the volume being shadow copied. This is probably due to excessive activity on the volume. Try again later when the volume is not being used so heavily.

�The shadow copy provider timed out while holding writes to the volume being shadow copied. This is probably due to excessive activity on the volume by an application or a system service. Try again later when activity on the volume is reduced.

|VSS encountered problems while sending events to writers.

�Another shadow copy creation is already in progress. Wait a few moments and try again.

�The specified volume has already reached its maximum number of shadow copies.

�An error was detected in the Volume Shadow Copy Service (VSS). The problem occurred while trying to contact VSS writers.

Verify that the Event System service and the VSS service are running and check for associated errors in the event logs.

tA 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.

�The writer has already successfully called the Subscribe function.  It cannot call

Subscribe multiple times.

�The shadow copy provider does not support the specified shadow copy type.

�The specified shadow copy storage association is in use and so can't be deleted.

�Maximum number of shadow copy storage associations already reached.

�Insufficient storage available to create either the shadow copy storage file or other shadow copy data.

dNo shadow copies were successfully imported.

pSome shadow copies were not successfully imported.

�The maximum number of remote machines for this operation has been reached.

LThe remote server is unavailable.

The remote server is running a version of the Volume Shadow Copy Service that does not

support remote shadow-copy creation.

A revert is currently in progress for the specified volume.  Another revert

cannot be initiated until the current revert completes.

lThe volume being reverted was lost during revert.

tA reboot is required after completing this operation.

|A timeout occurred while freezing a transaction manager.

�Too much time elapsed between freezing a transaction manager and thawing

the transaction manager.

The requested operation would overwrite a volume that is not explicitly selected. For more information, check the Application event log.

�The shadow copy ID was not found in the backup components document for the shadow copy set.

�The specified volume is nested too deeply to participate in the VSS operation.

�The volume being backed up is not mounted on the local host.

�A timeout occurred while preparing a cluster shared volume for backup.

\The requested operation is not supported.

�The writer experienced a partial failure. Check the component level error state for more information.

The shadow-copy set only contains only a subset of the

volumes needed to correctly backup the selected components

of the writer.

�A resource allocation failed while processing this operation.

�The writer's timeout expired between the Freeze and Thaw events.

�The writer experienced a transient error.  If the backup process is retried,

the error may not reoccur.

�The writer experienced a non-transient error.  If the backup process is retried,

the error is likely to reoccur.

�The writer experienced an error while trying to recover the shadow-copy volume.

�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.

�This version of the hardware provider does not support this operation.

hAn expected disk did not arrive in the system.

�An expected hidden volume did not arrive in the system. Check the Application event log for more information.

�An expected volume did not arrive in the system. Check the Application event log for more information.

�The autorecovery operation failed to complete on the shadow copy.

�An error occurred in processing the dynamic disks involved in the operation.

$The given Backup Components Document is for a non-transportable shadow copy. This operation can only be done on transportable shadow copies.

(The MBR signature or GPT ID for one or more disks could not be set to the intended value. Check the Application event log for more information.

The LUN resynchronization operation could not be started because another resynchronization operation is already in progress.

�The clustered disks could not be enumerated or could not be put into cluster maintenance mode. Check the System event log for cluster related events and the Application event log for VSS related events.

\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.

hWindows 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.

$The computer needs to be restarted to finish preparing a hard disk for restore. To continue, restart your computer and run the restore again.

�The backup failed due to a missing disk for a dynamic volume. Ensure the disk is online and retry the backup.

HAutomated System Recovery failed the shadow copy, because a selected critical volume is located on a cluster shared disk. This is an unsupported configuration.

XA 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.

DThe 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.

�Failed to find enough suitable disks for recreating all critical disks. The number of available disks should be same or greater than the number of critical disks at time of backup, and each one of the disks must be of same or greater size.

8Writer status is not available for one or more writers.  A writer may have reached the limit to the number of available backup-restore session states.

$A critical dynamic disk is a Virtual Hard Disk (VHD). This is an unsupported configuration. Check the Application event log for more details.

�A critical volume selected for backup exists on a disk which cannot be backed up by ASR.

No disk that can be used for recovering the system disk can be found.

Try the following:

1) A probable system disk may have been excluded by mistake.

    a.  Review the list of disks that you have excluded from the recovery

        for a likely disk.

    b.  Type LIST DISK command in the DISKPART command interpreter. The

        probable system disk is usually the first disk listed in the results.

    c.  If possible, remove the disk from the exclusion list and then retry

       the recovery.

2) A USB disk may have been assigned as a system disk.

    a.  Detach all USB disks from the computer.

    b.  Reboot into Windows Recovery Environment (Win RE),

        then reattach USB disks and retry the recovery.

3) An invalid disk may have been assigned as system disk.

    a.  Physically detach the disk from your computer. Then boot

        into Win RE to retry the recovery.

@Windows did not find any fixed disk that can be used to recreate volumes present in backup. Ensure disks are online, and disk drivers are installed to access the disk(s). 'diskpart.exe' tool with list disks command can be used to see the list of available fixed disks on the system.

Windows did not find any disk which it can use for recreating volumes present in backup. Offline disks, cluster shared disks or disks explicitly excluded by user will not be used by Windows. Ensure that disks are online and no disks are excluded by mistake.

�Restore failed because a disk which was critical at backup is excluded. To continue you need to either remove the disk from exclusion list or detach it from machine or clean it using DiskPart utility, and then retry restore. If you cannot clean or detach it then change the disk signature using DiskPart command UNIQUEID DISK ID.

 System partition (partition marked "active") is hidden or contains an unrecognized file system. Backup does not support this configuration.

�A timeout occurred while preparing a file share shadowcopy for backup.

�4VS_VERSION_INFO��
aJ
aJ?6StringFileInfo040904B0LCompanyNameMicrosoft Corporation�6FileDescriptionMicrosoft� Volume Shadow Copy Service Tracing Libraryh$FileVersion10.0.19041.1 (WinBuild.160101.0800):
InternalNamevsstrace.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.JOriginalFilenamevsstrace.dll.muij%ProductNameMicrosoft� Windows� Operating System>
ProductVersion10.0.19041.1DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD