Message

Volume "%1" appears as disconnected and it is ignored by the service.  You may want to rescan disks.   Error: %2.
%3

Fields

Message

The COM Server with CLSID %1 and name "%2" cannot be started on machine "%3". Most likely the CPU is under heavy load.  Error: %4.
%5

Fields

Message

The COM Server with CLSID %1 and name "%2" cannot be started on machine "%3".  Error: %4.
%5

Fields

Message

The COM Server with CLSID %1 and name "%2" cannot be started on machine "%3" during Safe Mode. The Data Deduplication service cannot start while in safe mode.  Error: %4.
%5

Fields

Message

A critical component required by Data Deduplication is not registered. This might happen if an error occurred during Windows setup, or if the computer does not have the Windows Server 2012 or later version of Deduplication service installed. The error returned from CoCreateInstance on class with CLSID %1 and Name "%2" on machine "%3" is %4.
%5

Fields

Message

Data Deduplication service is shutting down due to idle timeout.
%1

Fields

Message

Data Deduplication service is shutting down due to shutdown event from the Service Control Manager.
%1

Fields

Message

Data Deduplication job of type "%1" on volume "%2" has completed with return code: %3
%4

Fields

Message

Data Deduplication error: Unexpected error calling routine %1.  hr = %2.
%3

Fields

Message

Data Deduplication error: Unexpected error.
%1

Fields

Message

Data Deduplication warning: %1
Error: %2.
%3

Fields

Message

Data Deduplication error: Unexpected COM error %1: %2.  Error code: %3.
%4

Fields

Message

Data Deduplication was unable to access the following file or volume: "%1".  This file or volume might be locked by another application right now, or you might need to give Local System access to it.
%2

Fields

Message

Data Deduplication encountered an unexpected error during volume scan of volumes mounted at "%1" ("%2"). To find out more information about the root cause for this error please consult the Application/System event log for other Deduplication service, VSS or VOLSNAP errors related with these volumes. Also, you might want to make sure that you can create shadow copies on these volumes by using the VSSADMIN command like this: VSSADMIN CREATE SHADOW /For=C:
%3

Fields

Message

Data Deduplication was unable to create or access the shadow copy for volumes mounted at "%1" ("%2"). Possible causes include an improper Shadow Copy configuration, insufficient disk space, or extreme memory, I/O or CPU load of the system. To find out more information about the root cause for this error please consult the Application/System event log for other Deduplication service, VSS or VOLSNAP errors related with these volumes. Also, you might want to make sure that you can create shadow copies on these volumes by using the VSSADMIN command like this: VSSADMIN CREATE SHADOW /For=C:
%3

Fields

Message

Data Deduplication was unable to access volumes mounted at "%1" ("%2"). Make sure that dismount or format operations do not happen while running deduplication.
%3

Fields

Message

Data Deduplication was unable to access a file or volume. Details:

%1
 The volume may be inaccessible for I/O operations or marked read-only. In case of a cluster volume, this may be a transient failure during failover.
%2

Fields

Message

Data Deduplication was unable to scan volume "%1" ("%2").
%3

Fields

Message

Data Deduplication detected a corruption on file "%1" at offset ("%2").  If this condition persists then please restore the data from a previous backup.  Corruption details: Structure=%3, Corruption type = %4, Additional data = %5
%6

Fields

Message

Data Deduplication encountered failure while reconciling chunk store on volume "%1". The error code was %2. Reconciliation is disabled for the current optimization job.
%3

Fields

Message

Data Deduplication encountered corrupted chunk container %1 while performing full garbage collection. The corrupted chunk container is skipped.
%2

Fields

Message

Data Deduplication could not initialize change log under %1. The error code was %2.
%3

Fields

Message

Data Deduplication service could not mark chunk container %1 as reconciled. The error code was %2.
%3

Fields

Message

A Data Deduplication configuration file is corrupted. The system or volume may need to be restored from backup.
%1

Fields

Message

Data Deduplication was unable to save one of the configuration stores on volume "%1" due to a disk-full error: If the disk is full, please clean it up (extend the volume or delete some files). If the disk is not full, but there is a hard quota on the volume root, please delete, disable or increase this quota.
%2

Fields

Message

Data Deduplication could not access global configuration since the cluster service is not running. Please start the cluster service and retry the operation.
%1

Fields

Message

Shadow copy "%1" was deleted during storage report generation.  Volume "%2" might be configured with inadequate shadow copy storage area. Data Deduplication could not process this volume.
%3

Fields

Message

Shadow copy creation failed for volume "%1" after retrying for %2 minutes because other shadow copies were being created.  Reschedule the Data Deduplication for a less busy time.
%3

Fields

Message

Volume "%1" is not supported for shadow copy.  It is possible that the volume was removed from the system.  Data Deduplication service could not process this volume.
%2

Fields

Message

The volume "%1" has been deleted or removed from the system.
%2

Fields

Message

Shadow copy creation failed for volume "%1" with error %2.  The volume might be configured with inadequate shadow copy storage area.  File Serve Deduplication service could not process this volume.
%3

Fields

Message

The file system on volume "%1" is potentially corrupted.  Please run the CHKDSK utility to verify and fix the file system.
%2

Fields

Message

Data Deduplication detected an insecure internal folder. To secure the folder, reinstall deduplication on the volume again.
%1

Fields

Message

Data Deduplication could not find a chunk store on the volume.
%1

Fields

Message

Data Deduplication detected multiple chunk store folders. To recover, reinstall deduplication on the volume.
%1

Fields

Message

Data Deduplication detected conflicting chunk store folders: "%1" and "%2".
%3

Fields

Message

The data is invalid.
%1

Fields

Message

Data Deduplication scheduler failed to initialize with error "%1".
%2

Fields

Message

Data Deduplication failed to validate job type "%1" on volume "%2" with error "%3".
%4

Fields

Message

Data Deduplication failed to start job type "%1" on volume "%2" with error "%3".
%4

Fields

Message

Data Deduplication detected job type "%1" on volume "%2" uses too much memory. %3 MB is assigned. %4 MB is used.
%5

Fields

Message

Data Deduplication detected job type "%1" on volume "%2" memory usage has dropped to desirable level.
%3

Fields

Message

Data Deduplication cancelled job type "%1" on volume "%2". It uses too much memory than the amount assigned to it.
%3

Fields

Message

Data Deduplication cancelled job type "%1" on volume "%2". Memory resource is running low on the machine or in the job.
%3

Fields

Message

Data Deduplication job type "%1" on volume "%2" failed to report completion to the service with error: %3.
%4

Fields

Message

Data Deduplication detected a container cannot be compacted or updated because it has reached the maximum generation.
%1

Fields

Message

Data Deduplication corruption log "%1" is corrupted.
%2

Fields

Message

Data Deduplication corruption log "%1" has reached maximum allowed size "%2". Please run scrubbing job to process corruption log. No more corruptions will be reported until the log is processed.
%3

Fields

Message

Data Deduplication corruption log "%1" has reached maximum allowed size "%2". No more corruptions will be reported until the log is processed.
%3

Fields

Message

Data Deduplication scheduler failed to uninitialize with error "%1".
%2

Fields

Message

Data Deduplication detected a new container could not be created in a chunk store because it ran out of available container Id.
%1

Fields

Message

Data Deduplication full garbage collection phase 1 (cleaning file related metadata) on volume "%1" failed with error: %2.  The job will continue with phase 2 execution (data chunk cleanup).
%3

Fields

Message

Data Deduplication full garbage collection could not achieve maximum space reclamation because delete logs for data container %1 could not be cleaned up.
%2

Fields

Message

Some files could not be deduplicated because of FSRM Quota violations on volume %1. Files skipped are likely compressed or sparse files in folders which are at quota or close to their quota limit. Please consider increasing the quota limit for folders that are at their quota limit or close to it.
%2

Fields

Message

Data Deduplication failed to dedup file %1 "%2" due to fatal error %3
%4

Fields

Message

Data Deduplication encountered corruption while accessing a file in chunk store.
%1

Fields

Message

Data Deduplication encountered corruption while accessing a file in chunk store. Please run scrubbing job for diagnosis and repair.
%1

Fields

Message

Data Deduplication encountered checksum (CRC) mismatch error while accessing a file in chunk store. Please run scrubbing job for diagnosis and repair.
%1

Fields

Message

Data Deduplication is unable to access file %1 because the file is in use.
%2

Fields

Message

Data Deduplication encountered checksum (CRC) mismatch error while accessing a file in chunk store.
%1

Fields

Message

Data Deduplication cannot run the job on volume %1 because the dedup store version compatiblity check failed with error %2.
%3

Fields

Message

Data Deduplication has disabled the volume %1 because it has discovered too many corruptions. Please run deep scrubbing on the volume.
%2

Fields

Message

Data Deduplication has detected a corrupt corruption metadata file on the store at %1. Please run deep scrubbing on the volume.
%2

Fields

Message

Volume "%1" cannot be enabled for Data Deduplication. Data Deduplication does not support volumes larger than 64TB. Error: %2.
%3

Fields

Message

Data Deduplication cannot be enabled on SIS volume "%1". Error: %2.
%3

Fields

Message

File-system is configured for case-sensitive file/folder names. Data Deduplication does not support case-sensitive file-system mode.
%1

Fields

Message

Data Deduplication changed scrubbing job to read-only due to insufficient disk space.
%1

Fields

Message

Data Deduplication has disabled the volume %1 because there are missing or corrupt containers. Please run deep scrubbing on the volume.
%2

Fields

Message

Data Deduplication encountered a disk-full error.
%1

Fields

Message

Data Deduplication job cannot run on volume "%1" due to insufficient disk space.
%2

Fields

Message

Data Deduplication job cannot run on offline volume "%1".
%2

Fields

Message

Data Deduplication recovered a corrupt or missing file.
%1

Fields

Message

Data Deduplication encountered a corrupted metadata file. To correct the problem, schedule or manually run a Garbage Collection job on the affected volume with the -Full option.
%1

Fields

Message

Data Deduplication encountered chunk %1 with corrupted header while updating container. The corrupted chunk is replicated to the new container %2.
%3

Fields

Message

Data Deduplication encountered chunk %1 with transient header corruption while updating container. The corrupted chunk is NOT replicated to the new container %2.
%3

Fields

Message

Data Deduplication failed to read chunk container redirection table from file %1 with error %2.
%3

Fields

Message

Data Deduplication failed to initialize reparse point index table for deep scrubbing from file %1 with error %2.
%3

Fields

Message

Data Deduplication failed to deep scrub container file %1 on volume %2 with error %3.
%4

Fields

Message

Data Deduplication failed to load stream map log for deep scrubbing from file %1 with error %2.
%3

Fields

Message

Data Deduplication found a duplicate local chunk id %1 in container file %2.
%3

Fields

Message

Data Deduplication job type "%1" on volume "%2" was cancelled manually.
%3

Fields

Message

Scheduled data Deduplication job type "%1" on volume "%2" was cancelled.
%3

Fields

Message

The Data Deduplication chunk store statistics file on volume "%1" is corrupted and will be reset. Statistics will be updated by a subsequent job and can be updated manually by running the Update-DedupStatus cmdlet.
%2

Fields

Message

The Data Deduplication volume statistics file on volume "%1" is corrupted and will be reset. Statistics will be updated by a subsequent job and can be updated manually by running the Update-DedupStatus cmdlet.
%2

Fields

Message

Data Deduplication failed to append to deep scrubbing log file %1 with error %2.
%3

Fields

Message

Data Deduplication encountered a failure during deep scrubbing on store %1 with error %2.
%3

Fields

Message

Data Deduplication cancelled job type "%1" on volume "%2". The job violated Csv dedup job placement policy.
%3

Fields

Message

Data Deduplication cancelled job type "%1" on volume "%2". The csv job monitor has been uninitialized.
%3

Fields

Message

Data Deduplication encountered a IO device error while accessing a file on the volume. This is likely a hardware fault in the storage subsystem.
%1

Fields

Message

Data Deduplication encountered an unexpected error. If this is a cluster, verify Data Deduplication is enabled on all nodes of the cluster.
%1

Fields

Message

Attempted to disable data access for data deduplicated CSV volume "%1" without maintenance mode. Data access can only be disabled for a CSV volume when in maintenance mode. Place volume into maintenance mode and retry.
%2

Fields

Message

Data Deduplication service could not unoptimize file "%5%6%7". Error %8, "%9".

Fields

Message

Data Deduplication service failed to unoptimize too many files %3. Some files are not reported.

Fields

Message

Data Deduplication service has finished unoptimization on volume %3 with no errors.

Fields

Message

Data Deduplication service has finished unoptimization on volume %3 with %4 errors.

Fields

Message

%1 job has started.

Volume: %4 (%3)
Available memory: %5 MB
Available cores: %6
Instances: %7
Readers per instance: %8
Priority: %9
IoThrottle: %10

Fields

Message

%1 job has started.

Volume: %4 (%3)
Available memory: %5 MB
Available cores: %6
Priority: %7
Full: %8
Volume free space (MB): %9

Fields

Message

%1 job has started.

Volume: %4 (%3)
Available memory: %5 MB
Priority: %6
Full: %7
Read-only: %8

Fields

Message

%1 job has started.

Volume: %4 (%3)
Available memory: %5 MB
Priority: %6

Fields

Message

%1 job has started.

Volume: %4 (%3)
Available memory: %5 MB
Priority: %6

Fields

Message

%1 job has completed.

Volume: %4 (%3)
Error code: %5
Error message: %6
Savings rate (percent): %7
Saved space (MB): %8
Volume used space (MB): %9
Volume free space (MB): %10
Optimized file count: %11
In-policy file count: %12
Job processed space (MB): %13
Job elapsed time (seconds): %18
Job throughput (MB/second): %19
Churn processing throughput (MB/second): %20

Fields

Message

%1 job has completed.

Full: %2
Volume: %5 (%4)
Error code: %6
Error message: %7
Freed up space (MB): %8
Volume free space (MB): %9
Job elapsed time (seconds): %10
Job throughput (MB/second): %11

Fields

Message

%1 job has completed.

Volume: %4 (%3)
Error code: %5
Error message: %6

Fields

Message

%1 job has completed.

Full: %2
Read-only: %3
Volume: %6 (%5)
Error code: %7
Error message: %8
Total corruption count: %9
Fixable corruption count: %10

When corruptions are found, check more details in Scrubbing event channel.

Fields

Message

%1 job has completed.

Volume: %4 (%3)
Error code: %5
Error message: %6
Unoptimized file count: %7
Job processed space (MB): %8
Job elapsed time (seconds): %9
Job throughput (MB/second): %10

Fields

Message

%1 job has been queued.

Volume: %4 (%3)
System memory percent: %5 
Priority: %6
Schedule mode: %7

Fields

Message

%1 job has been queued.

Volume: %4 (%3)
System memory percent: %5 
Priority: %6
Schedule mode: %7

Fields

Message

%1 job has been queued.

Volume: %4 (%3)
System memory percent: %5 
Priority: %6
Schedule mode: %7

Fields

Message

%1 job has been queued.

Volume: %4 (%3)
System memory percent: %5 
Priority: %6
Schedule mode: %7

Fields

Message

%1 job has been queued.

Volume: %4 (%3)
System memory percent: %5 
Priority: %6
Schedule mode: %7

Fields

Message

Restore of deduplicated file "%1" failed with the following error: %2, "%3".

Fields

Message

Priority %1 job has started.

Volume: %4 (%3)
File ID: %11
Available memory: %5 MB
Available cores: %6
Instances: %7
Readers per instance: %8
Priority: %9
IoThrottle: %10

Fields

Message

%1 job has started.

Volume: %4 (%3)
Available memory: %5 MB
Available threads: %6
Priority: %7

Fields

Message

%1 job has completed.

Volume: %4 (%3)
Error code: %5
Error message: %6
Savings rate (percent): %7
Saved space (MB): %8
Volume used space (MB): %9
Volume free space (MB): %10
Optimized file count: %11
Chunk lookup count: %12
Inserted chunk count: %13
Inserted chunks logical data (MB): %14
Inserted chunks physical data (MB): %15
Committed stream count: %16
Committed stream entry count: %17
Committed stream logical data (MB): %18
Retrieved chunks physical data (MB): %19
Retrieved stream logical data (MB): %20
DataPort time (seconds): %21
Job elapsed time (seconds): %22
Ingress throughput (MB/second): %23
Egress throughput (MB/second): %24

Fields

Message

%1 job has been queued.

Volume: %4 (%3)
System memory percent: %5 
Priority: %6
Schedule mode: %7

Fields

Message

Data Deduplication detected a non-clustered volume specified for the chunk index cache volume in a clustered deployment. The configuration is not recommended because it may result in job failures after failover.

Volume: %3 (%2)

Fields

Message

DataPort status update.  

Volume: %2
Savings rate (percent): %3
Saved space (MB): %4
Volume used space (MB): %5
Volume free space (MB): %6
Optimized file count: %7
Chunk lookup count: %8
Inserted chunk count: %9
Inserted chunks logical data (MB): %10
Inserted chunks physical data (MB): %11
Committed stream count: %12
Committed stream entry count: %13
Committed stream logical data (MB): %14
Retrieved chunks physical data (MB): %15
Retrieved stream logical data (MB): %16
DataPort time (seconds): %17
Job elapsed time (seconds): %18
Ingress throughput (MB/second): %19
Egress throughput (MB/second): %20

Fields

Message

Data Deduplication detected job type "%1" on volume "%2" working set is low. Ratio to commit size is %3.
%4

Fields

Message

Data Deduplication detected job type "%1" on volume "%2" working set has recovered to desirable level.
%3

Fields

Message

Data Deduplication detected job type "%1" on volume "%2" page fault rate is high. The rate is %3 page faults per second.
%4

Fields

Message

Data Deduplication detected job type "%1" on volume "%2" page fault rate has lowered to desirable level. The rate is %3 page faults per second.
%4

Fields

Message

Data Deduplication failed to dedup file "%1" with file ID %2 due to non-fatal error %3
%4.

Note: You can retrieve the file name by running the command FSUTIL FILE QUERYFILENAMEBYID on the file in question.

Fields

Message

Data Deduplication was unable to access a file or volume. Details:

%1
 The volume may be inaccessible for I/O operations or marked read-only. In case of a cluster volume, this may be a transient failure during failover.
%2

Fields

Message

Data Deduplication could not find a chunk store on the volume.
%1

Fields

Message

Data Deduplication detected multiple chunk store folders. To recover, reinstall deduplication on the volume.
%1

Fields

Message

The data is invalid.
%1

Fields

Message

Data Deduplication detected a container cannot be compacted or updated because it has reached the maximum generation.
%1

Fields