Volsnap

122 events across 2 channels

Event ID	Title	Channel
1	The shadow copy of volume {VolumeNameLength} could not create shadow copy …	System
2	The shadow copy of volume {VolumeNameLength} could not be created because volume …	System
3	The shadow copy of volume {VolumeNameLength} could not lock down the location of …	System
4	The shadow copy of volume {VolumeNameLength} could not be created due to …	System
5	The shadow copy of volume {VolumeNameLength} could not be created due to …	System
6	The shadow copy of volume {VolumeNameLength} could not create a new paged heap.	System
7	The shadow copy of volume {VolumeNameLength} failed to query the shadow copy …	System
8	The flush and hold writes operation on volume {VolumeNameLength} timed out while …	System
9	The flush and hold writes operation on volume {VolumeNameLength} timed out while …	System
10	The shadow copy of volume {VolumeNameLength} took too long to install.	System
13	The shadow copy of volume {VolumeNameLength} could not grow its shadow copy …	System
14	The shadow copies of volume {VolumeNameLength} were aborted because of an IO …	System
15	The shadow copies of volume {VolumeNameLength} were aborted because of …	System
16	The shadow copies of volume {VolumeNameLength} were aborted because volume …	System
17	An attempt to flush and hold writes on volume {VolumeNameLength} was attempted …	System
20	The shadow copies of volume {VolumeNameLength} were aborted because of a failed …	System
21	The flush and hold operation for volume {VolumeNameLength} was aborted because …	System
22	The shadow copy storage volume specified for shadow copies on volume …	System
23	There was insufficient disk space on volume {VolumeName} to create the shadow …	System
24	There was insufficient disk space on volume {VolumeName} to grow the shadow copy …	System
25	The shadow copies of volume {VolumeNameLength} were deleted because the shadow …	System
27	The shadow copies of volume {VolumeNameLength} were aborted during detection …	System
28	The shadow copy of volume {VolumeNameLength} could not be created due to a …	System
29	The shadow copies of volume {VolumeNameLength} were aborted during detection.	System
30	An unfinished create of a shadow copy of volume {VolumeNameLength} was deleted.	System
31	A control item for shadow copies of volume {VolumeNameLength} was lost during …	System
32	The shadow copies of volume {VolumeNameLength} were aborted because the shadow …	System
33	The oldest shadow copy of volume {VolumeNameLength} was deleted to keep disk …	System
35	The shadow copies of volume {VolumeNameLength} were aborted because the shadow …	System
36		System
38	There was a user imposed limit that prevented disk space on volume {VolumeName} …	System
39	When preparing a new volume shadow copy for volume {VolumeNameLength}; the …	System
40	The shadow copies of volume {VolumeNameLength} were aborted because volume …	System
41	When preparing a new volume shadow copy for volume {VolumeNameLength}; the …	System
48	When preparing a new volume shadow copy for volume {VolumeNameLength}; the …	System
58	The oldest shadow copy of volume {VolumeNameLength} was deleted to keep the …	System
59	The shadow copies of volume {VolumeNameLength} were aborted because the shadow …	System
60	The shadow copies of volume {VolumeNameLength} were aborted because volume …	System
61	The revert operation on volume {VolumeNameLength} encountered a bad sector …	System
62	The revert operation on volume {VolumeNameLength} stopped because of the loss of …	System
63	An error occurred while trying to delete a snapshot of {VolumeNameLength}.	System
64	Volume {VolumeNameLength} is being reverted to the state of a previous shadow …	System
65	The reverting of volume {VolumeNameLength} is being restarted.	System
66	The reverting of volume {VolumeNameLength} to the state of a previous shadow …	System
67	The shadow copy of volume {VolumeNameLength} being created failed to install.	System
80	Volume {VolumeNameLength} is offline for shadow copy protection.	System
81	Volume {VolumeNameLength} is offline for shadow copy protection.	System
82	Volume {VolumeNameLength} is offline for shadow copy protection.	System
83	Volume {VolumeNameLength} is offline for shadow copy protection.	System
84	Volume {VolumeNameLength} is offline for shadow copy protection.	System
85	Volume {VolumeNameLength} is offline for shadow copy protection.	System
86	Volume {VolumeNameLength} is offline for shadow copy protection.	System
87	Volume {VolumeNameLength} is offline for shadow copy protection.	System
88	Volume {VolumeNameLength} is offline for shadow copy protection.	System
89	Volume {VolumeNameLength} is offline for shadow copy protection.	System
90	Volume {VolumeNameLength} is offline for shadow copy protection.	System
91	Volume {VolumeNameLength} is offline for shadow copy protection.	System
92	Volume {VolumeNameLength} is offline for shadow copy protection.	System
93	Volume {VolumeNameLength} is offline for shadow copy protection.	System
94	Volume {VolumeNameLength} is offline for shadow copy protection.	System
1074135073	The oldest shadow copy of volume %2 was deleted to keep disk space usage for …	Unknown
1074135098	The oldest shadow copy of volume %2 was deleted to keep the total number of …	Unknown
1074135104	Volume %2 is being reverted to the state of a previous shadow copy.	Unknown
1074135105	The reverting of volume %2 is being restarted.	Unknown
1074135106	The reverting of volume %2 to the state of a previous shadow copy is complete.	Unknown
1074135135	The oldest shadow copy of volume %2 was deleted to allow shadow copies created …	Unknown
2147876888	There was insufficient disk space on volume %3 to grow the shadow copy storage …	Unknown
2147876894	An unfinished create of a shadow copy of volume %2 was deleted.	Unknown
2147876902	There was a user imposed limit that prevented disk space on volume %3 from being …	Unknown
2147876925	The revert operation on volume %2 encountered a bad sector error.	Unknown
2147876926	The revert operation on volume %2 stopped because of the loss of a volume.	Unknown
3221618689	The shadow copy of volume %2 could not create shadow copy storage on volume %3.	Unknown
3221618690	The shadow copy of volume %2 could not be created because volume %3, which is …	Unknown
3221618691	The shadow copy of volume %2 could not lock down the location of the shadow copy …	Unknown
3221618692	The shadow copy of volume %2 could not be created due to insufficient resources …	Unknown
3221618693	The shadow copy of volume %2 could not be created due to insufficient non-paged …	Unknown
3221618694	The shadow copy of volume %2 could not create a new paged heap.	Unknown
3221618695	The shadow copy of volume %2 failed to query the shadow copy storage mappings on …	Unknown
3221618696	The flush and hold writes operation on volume %2 timed out while waiting for a …	Unknown
3221618697	The flush and hold writes operation on volume %2 timed out while waiting for …	Unknown
3221618698	The shadow copy of volume %2 took too long to install.	Unknown
3221618701	The shadow copy of volume %2 could not grow its shadow copy storage on volume …	Unknown
3221618702	The shadow copies of volume %2 were aborted because of an IO failure on volume …	Unknown
3221618703	The shadow copies of volume %2 were aborted because of insufficient paged heap.	Unknown
3221618704	The shadow copies of volume %2 were aborted because volume %3, which contains …	Unknown
3221618705	An attempt to flush and hold writes on volume %2 was attempted while another …	Unknown
3221618708	The shadow copies of volume %2 were aborted because of a failed free space …	Unknown
3221618709	The flush and hold operation for volume %2 was aborted because of low available …	Unknown
3221618710	The shadow copy storage volume specified for shadow copies on volume %2 could …	Unknown
3221618711	There was insufficient disk space on volume %3 to create the shadow copy of …	Unknown
3221618713	The shadow copies of volume %2 were deleted because the shadow copy storage …	Unknown
3221618715	The shadow copies of volume %2 were aborted during detection because a critical …	Unknown
3221618716	The shadow copy of volume %2 could not be created due to a failure in creating …	Unknown
3221618717	The shadow copies of volume %2 were aborted during detection.	Unknown
3221618719	A control item for shadow copies of volume %2 was lost during detection.	Unknown
3221618720	The shadow copies of volume %2 were aborted because the shadow copy storage …	Unknown
3221618723	The shadow copies of volume %2 were aborted because the shadow copy storage …	Unknown
3221618724	The shadow copies of volume %2 were aborted because the shadow copy storage …	Unknown
3221618727	When preparing a new volume shadow copy for volume %2, the shadow copy storage …	Unknown
3221618728	The shadow copies of volume %2 were aborted because volume %3 has been …	Unknown
3221618729	When preparing a new volume shadow copy for volume %2, the shadow copy storage …	Unknown
3221618736	When preparing a new volume shadow copy for volume %2, the shadow copy storage …	Unknown
3221618747	The shadow copies of volume %2 were aborted because the shadow copy storage …	Unknown
3221618748	The shadow copies of volume %2 were aborted because volume %3, which contains …	Unknown
3221618751	An error occurred while trying to delete a snapshot of %2.	Unknown
3221618755	The shadow copy of volume %2 being created failed to install.	Unknown
3221618768	Volume %2 is offline for shadow copy protection.	Unknown
3221618769	Volume %2 is offline for shadow copy protection.	Unknown
3221618770	Volume %2 is offline for shadow copy protection.	Unknown
3221618771	Volume %2 is offline for shadow copy protection.	Unknown
3221618772	Volume %2 is offline for shadow copy protection.	Unknown
3221618773	Volume %2 is offline for shadow copy protection.	Unknown
3221618774	Volume %2 is offline for shadow copy protection.	Unknown
3221618775	Volume %2 is offline for shadow copy protection.	Unknown
3221618776	Volume %2 is offline for shadow copy protection.	Unknown
3221618777	Volume %2 is offline for shadow copy protection.	Unknown
3221618778	Volume %2 is offline for shadow copy protection.	Unknown
3221618779	Volume %2 is offline for shadow copy protection.	Unknown
3221618780	Volume %2 is offline for shadow copy protection.	Unknown
3221618781	Volume %2 is offline for shadow copy protection.	Unknown
3221618782	Volume %2 is offline for shadow copy protection.	Unknown
3221618784	The shadow copies of volume %2 were aborted because of an error when disabling …	Unknown

Event ID 1 — The shadow copy of volume {VolumeNameLength} could not create shadow copy storage on volume {VolumeName}.

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} could not create shadow copy storage on volume {VolumeName}.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 2 — The shadow copy of volume {VolumeNameLength} could not be created because volume {VolumeName}; which is specified as the location for shadow copy s...

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} could not be created because volume {VolumeName}; which is specified as the location for shadow copy storage; is not an NTFS volume or an error was encountered while trying to determine the file system type of this volume.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 3 — The shadow copy of volume {VolumeNameLength} could not lock down the location of the shadow copy storage on volume {VolumeName}.

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} could not lock down the location of the shadow copy storage on volume {VolumeName}.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 4 — The shadow copy of volume {VolumeNameLength} could not be created due to insufficient resources for worker threads.

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} could not be created due to insufficient resources for worker threads.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 5 — The shadow copy of volume {VolumeNameLength} could not be created due to insufficient non-paged memory pool for a bitmap structure.

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} could not be created due to insufficient non-paged memory pool for a bitmap structure.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 6 — The shadow copy of volume {VolumeNameLength} could not create a new paged heap.

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} could not create a new paged heap.  The system may be low on virtual memory.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 7 — The shadow copy of volume {VolumeNameLength} failed to query the shadow copy storage mappings on volume {VolumeName}.

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} failed to query the shadow copy storage mappings on volume {VolumeName}.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 8 — The flush and hold writes operation on volume {VolumeNameLength} timed out while waiting for a release writes command.

Provider: Volsnap
Channel: System

Message

The flush and hold writes operation on volume {VolumeNameLength} timed out while waiting for a release writes command.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 9 — The flush and hold writes operation on volume {VolumeNameLength} timed out while waiting for file system cleanup.

Provider: Volsnap
Channel: System

Message

The flush and hold writes operation on volume {VolumeNameLength} timed out while waiting for file system cleanup.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 10 — The shadow copy of volume {VolumeNameLength} took too long to install.

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} took too long to install.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 13 — The shadow copy of volume {VolumeNameLength} could not grow its shadow copy storage on volume {VolumeName}.

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} could not grow its shadow copy storage on volume {VolumeName}.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 14 — The shadow copies of volume {VolumeNameLength} were aborted because of an IO failure on volume {VolumeName}.

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted because of an IO failure on volume {VolumeName}.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 15 — The shadow copies of volume {VolumeNameLength} were aborted because of insufficient paged heap.

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted because of insufficient paged heap.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 16 — The shadow copies of volume {VolumeNameLength} were aborted because volume {VolumeName}; which contains shadow copy storage for this shadow copy; w...

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted because volume {VolumeName}; which contains shadow copy storage for this shadow copy; was force dismounted.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 17 — An attempt to flush and hold writes on volume {VolumeNameLength} was attempted while another flush and hold was already in progress.

Provider: Volsnap
Channel: System

Message

An attempt to flush and hold writes on volume {VolumeNameLength} was attempted while another flush and hold was already in progress.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 20 — The shadow copies of volume {VolumeNameLength} were aborted because of a failed free space computation.

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted because of a failed free space computation.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 21 — The flush and hold operation for volume {VolumeNameLength} was aborted because of low available system memory.

Provider: Volsnap
Channel: System

Message

The flush and hold operation for volume {VolumeNameLength} was aborted because of low available system memory.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 22 — The shadow copy storage volume specified for shadow copies on volume {VolumeNameLength} could not be added.

Provider: Volsnap
Channel: System

Message

The shadow copy storage volume specified for shadow copies on volume {VolumeNameLength} could not be added.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 23 — There was insufficient disk space on volume {VolumeName} to create the shadow copy of volume {VolumeNameLength}.

Provider: Volsnap
Channel: System

Message

There was insufficient disk space on volume {VolumeName} to create the shadow copy of volume {VolumeNameLength}.  Shadow copy storage creation failed.

Fields

Name	Description
`VolumeName`	—
`VolumeNameLength`	—

Event ID 24 — There was insufficient disk space on volume {VolumeName} to grow the shadow copy storage for shadow copies of {VolumeNameLength}.

Provider: Volsnap
Channel: System

Message

There was insufficient disk space on volume {VolumeName} to grow the shadow copy storage for shadow copies of {VolumeNameLength}.  As a result of this failure all shadow copies of volume {VolumeNameLength} are at risk of being deleted.

Fields

Name	Description
`VolumeName`	—
`VolumeNameLength`	—

Event ID 25 — The shadow copies of volume {VolumeNameLength} were deleted because the shadow copy storage could not grow in time.

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 27 — The shadow copies of volume {VolumeNameLength} were aborted during detection because a critical control file could not be opened.

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted during detection because a critical control file could not be opened.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 28 — The shadow copy of volume {VolumeNameLength} could not be created due to a failure in creating the necessary on disk structures.

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} could not be created due to a failure in creating the necessary on disk structures.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 29 — The shadow copies of volume {VolumeNameLength} were aborted during detection.

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted during detection.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 30 — An unfinished create of a shadow copy of volume {VolumeNameLength} was deleted.

Provider: Volsnap
Channel: System

Message

An unfinished create of a shadow copy of volume {VolumeNameLength} was deleted.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 31 — A control item for shadow copies of volume {VolumeNameLength} was lost during detection.

Provider: Volsnap
Channel: System

Message

A control item for shadow copies of volume {VolumeNameLength} was lost during detection.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 32 — The shadow copies of volume {VolumeNameLength} were aborted because the shadow copy storage volume was not present.

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted because the shadow copy storage volume was not present.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 33 — The oldest shadow copy of volume {VolumeNameLength} was deleted to keep disk space usage for shadow copies of volume {VolumeNameLength} below the u...

Provider: Volsnap
Channel: System

Message

The oldest shadow copy of volume {VolumeNameLength} was deleted to keep disk space usage for shadow copies of volume {VolumeNameLength} below the user defined limit.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 35 — The shadow copies of volume {VolumeNameLength} were aborted because the shadow copy storage failed to grow.

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted because the shadow copy storage failed to grow.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 36 —

Provider: volsnap
Channel: System
Level: 2
Samples: 1

Fields

Name	Description
`Data`	—
`Binary`	—

Example Event

system:
  provider: volsnap
  guid: ''
  event_source_name: ''
  event_id: 36
  version: 0
  level: 2
  task: 0
  opcode: 0
  keywords: 36028797018963968
  time_created: '2012-03-21T04:21:17.758144Z'
  event_record_id: 12919
  correlation: {}
  execution:
    process_id: 0
    thread_id: 0
  channel: System
  computer: WKS-WIN764BITB.shieldbase.local
  security:
    user_id: ''
event_data:
  Data:
  - \Device\HarddiskVolumeShadowCopy2
  - 'C:'
  Binary: 000000000200300000000000240006C0020000000000000000000000000000000000000000000000

Event ID 38 — There was a user imposed limit that prevented disk space on volume {VolumeName} from being used to grow the shadow copy storage for shadow copies o...

Provider: Volsnap
Channel: System

Message

There was a user imposed limit that prevented disk space on volume {VolumeName} from being used to grow the shadow copy storage for shadow copies of {VolumeNameLength}.  As a result of this failure all shadow copies of volume {VolumeNameLength} are at risk of being deleted.

Fields

Name	Description
`VolumeName`	—
`VolumeNameLength`	—

Event ID 39 — When preparing a new volume shadow copy for volume {VolumeNameLength}; the shadow copy storage on volume {VolumeName} could not be located in non-c...

Provider: Volsnap
Channel: System

Message

When preparing a new volume shadow copy for volume {VolumeNameLength}; the shadow copy storage on volume {VolumeName} could not be located in non-critical space.  Consider using a shadow copy storage volume that does not have any shadow copies.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 40 — The shadow copies of volume {VolumeNameLength} were aborted because volume {VolumeName} has been dismounted.

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted because volume {VolumeName} has been dismounted.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 41 — When preparing a new volume shadow copy for volume {VolumeNameLength}; the shadow copy storage on volume {VolumeName} did not have sufficiently lar...

Provider: Volsnap
Channel: System

Message

When preparing a new volume shadow copy for volume {VolumeNameLength}; the shadow copy storage on volume {VolumeName} did not have sufficiently large contiguous blocks.  Consider deleting unnecessary files on the shadow copy storage volume or use a different shadow copy storage volume.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 48 — When preparing a new volume shadow copy for volume {VolumeNameLength}; the shadow copy storage on volume {VolumeName} did not have sufficiently lar...

Provider: Volsnap
Channel: System

Message

When preparing a new volume shadow copy for volume {VolumeNameLength}; the shadow copy storage on volume {VolumeName} did not have sufficiently large contiguous blocks.  A shadow copy create computation is in progress to find more contiguous blocks.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 58 — The oldest shadow copy of volume {VolumeNameLength} was deleted to keep the total number of shadow copies of volume {VolumeNameLength} below a limit.

Provider: Volsnap
Channel: System

Message

The oldest shadow copy of volume {VolumeNameLength} was deleted to keep the total number of shadow copies of volume {VolumeNameLength} below a limit.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 59 — The shadow copies of volume {VolumeNameLength} were aborted because the shadow copy storage volume was not present in time during a previous session.

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted because the shadow copy storage volume was not present in time during a previous session.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 60 — The shadow copies of volume {VolumeNameLength} were aborted because volume {VolumeName}; which contains shadow copy storage for this shadow copy; h...

Provider: Volsnap
Channel: System

Message

The shadow copies of volume {VolumeNameLength} were aborted because volume {VolumeName}; which contains shadow copy storage for this shadow copy; has been taken offline.

Fields

Name	Description
`VolumeNameLength`	—
`VolumeName`	—

Event ID 61 — The revert operation on volume {VolumeNameLength} encountered a bad sector error.

Provider: Volsnap
Channel: System

Message

The revert operation on volume {VolumeNameLength} encountered a bad sector error.  Please validate the data on this volume.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 62 — The revert operation on volume {VolumeNameLength} stopped because of the loss of a volume.

Provider: Volsnap
Channel: System

Message

The revert operation on volume {VolumeNameLength} stopped because of the loss of a volume.  When the volume is re-introduced; the revert will continue.  You may have to reboot to trigger the revert.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 63 — An error occurred while trying to delete a snapshot of {VolumeNameLength}.

Provider: Volsnap
Channel: System

Message

An error occurred while trying to delete a snapshot of {VolumeNameLength}.  The delete will be retried at a later time.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 64 — Volume {VolumeNameLength} is being reverted to the state of a previous shadow copy.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is being reverted to the state of a previous shadow copy.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 65 — The reverting of volume {VolumeNameLength} is being restarted.

Provider: Volsnap
Channel: System

Message

The reverting of volume {VolumeNameLength} is being restarted.  This is most likely because of a system shutdown or a system crash.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 66 — The reverting of volume {VolumeNameLength} to the state of a previous shadow copy is complete.

Provider: Volsnap
Channel: System

Message

The reverting of volume {VolumeNameLength} to the state of a previous shadow copy is complete.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 67 — The shadow copy of volume {VolumeNameLength} being created failed to install.

Provider: Volsnap
Channel: System

Message

The shadow copy of volume {VolumeNameLength} being created failed to install.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 80 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  The shadow copy storage is not present.  This volume will go online and its shadow copies will become available once the shadow copy storage is introduced in the system.  Revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 81 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  An IO error occurred during shadow copy discovery.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 82 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  A shadow copy meta data corruption was detected.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 83 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  A memory allocation failed.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 84 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  A memory mapping failed.  Consider increasing the size of the page file.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 85 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  A read failure occurred during a shadow copy on write operation.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 86 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  A read or write failure to shadow copy storage occurred.  Please ensure that the shadow copy storage is still present in the system.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 87 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  The shadow copy storage has been exhausted.  Please try clearing the protection fault or restart the computer followed by an increase of the shadow copy storage or a removal of unneeded shadow copies.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 88 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  The shadow copy storage was exhausted before conditions permitted it to grow.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 89 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  The shadow copy storage could not be increased as needed.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 90 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 91 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  An error occurred when doing a file system operation.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 92 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  A read or write error occurred.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 93 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  The shadow copy storage was made inaccessible or removed from the system.  Please ensure that the shadow copy storage is present.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 94 — Volume {VolumeNameLength} is offline for shadow copy protection.

Provider: Volsnap
Channel: System

Message

Volume {VolumeNameLength} is offline for shadow copy protection.  An application attempted to write to the shadow copy meta data.  If this program was run intentionally then turn off protection mode for this volume in order to allow the application (which may be FORMAT) to run.  Please try clearing the protection fault or restart the computer.  If all else fails; revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`VolumeNameLength`	—

Event ID 1074135073 — The oldest shadow copy of volume %2 was deleted to keep disk space usage for shadow copies of volume %2 below the user defined limit.

Provider: Volsnap
Channel: Unknown

Message

The oldest shadow copy of volume %2 was deleted to keep disk space usage for shadow copies of volume %2 below the user defined limit.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 1074135098 — The oldest shadow copy of volume %2 was deleted to keep the total number of shadow copies of volume %2 below a limit.

Provider: Volsnap
Channel: Unknown

Message

The oldest shadow copy of volume %2 was deleted to keep the total number of shadow copies of volume %2 below a limit.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 1074135104 — Volume %2 is being reverted to the state of a previous shadow copy.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is being reverted to the state of a previous shadow copy.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 1074135105 — The reverting of volume %2 is being restarted.

Provider: Volsnap
Channel: Unknown

Message

The reverting of volume %2 is being restarted.  This is most likely because of a system shutdown or a system crash.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 1074135106 — The reverting of volume %2 to the state of a previous shadow copy is complete.

Provider: Volsnap
Channel: Unknown

Message

The reverting of volume %2 to the state of a previous shadow copy is complete.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 1074135135 — The oldest shadow copy of volume %2 was deleted to allow shadow copies created afterward and marked for delete to be deleted.

Provider: Volsnap
Channel: Unknown

Message

The oldest shadow copy of volume %2 was deleted to allow shadow copies created afterward and marked for delete to be deleted.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 2147876888 — There was insufficient disk space on volume %3 to grow the shadow copy storage for shadow copies of %2.

Provider: Volsnap
Channel: Unknown

Message

There was insufficient disk space on volume %3 to grow the shadow copy storage for shadow copies of %2.  As a result of this failure all shadow copies of volume %2 are at risk of being deleted.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 2147876894 — An unfinished create of a shadow copy of volume %2 was deleted.

Provider: Volsnap
Channel: Unknown

Message

An unfinished create of a shadow copy of volume %2 was deleted.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 2147876902 — There was a user imposed limit that prevented disk space on volume %3 from being used to grow the shadow copy storage for shadow copies of %2.

Provider: Volsnap
Channel: Unknown

Message

There was a user imposed limit that prevented disk space on volume %3 from being used to grow the shadow copy storage for shadow copies of %2.  As a result of this failure all shadow copies of volume %2 are at risk of being deleted.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 2147876925 — The revert operation on volume %2 encountered a bad sector error.

Provider: Volsnap
Channel: Unknown

Message

The revert operation on volume %2 encountered a bad sector error.  Please validate the data on this volume.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 2147876926 — The revert operation on volume %2 stopped because of the loss of a volume.

Provider: Volsnap
Channel: Unknown

Message

The revert operation on volume %2 stopped because of the loss of a volume.  When the volume is re-introduced, the revert will continue.  You may have to reboot to trigger the revert.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618689 — The shadow copy of volume %2 could not create shadow copy storage on volume %3.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 could not create shadow copy storage on volume %3.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618690 — The shadow copy of volume %2 could not be created because volume %3, which is specified as the location for shadow copy storage, is not an NTFS vol...

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 could not be created because volume %3, which is specified as the location for shadow copy storage, is not an NTFS volume or an error was encountered while trying to determine the file system type of this volume.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618691 — The shadow copy of volume %2 could not lock down the location of the shadow copy storage on volume %3.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 could not lock down the location of the shadow copy storage on volume %3.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618692 — The shadow copy of volume %2 could not be created due to insufficient resources for worker threads.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 could not be created due to insufficient resources for worker threads.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618693 — The shadow copy of volume %2 could not be created due to insufficient non-paged memory pool for a bitmap structure.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 could not be created due to insufficient non-paged memory pool for a bitmap structure.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618694 — The shadow copy of volume %2 could not create a new paged heap.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 could not create a new paged heap.  The system may be low on virtual memory.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618695 — The shadow copy of volume %2 failed to query the shadow copy storage mappings on volume %3.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 failed to query the shadow copy storage mappings on volume %3.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618696 — The flush and hold writes operation on volume %2 timed out while waiting for a release writes command.

Provider: Volsnap
Channel: Unknown

Message

The flush and hold writes operation on volume %2 timed out while waiting for a release writes command.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618697 — The flush and hold writes operation on volume %2 timed out while waiting for file system cleanup.

Provider: Volsnap
Channel: Unknown

Message

The flush and hold writes operation on volume %2 timed out while waiting for file system cleanup.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618698 — The shadow copy of volume %2 took too long to install.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 took too long to install.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618701 — The shadow copy of volume %2 could not grow its shadow copy storage on volume %3.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 could not grow its shadow copy storage on volume %3.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618702 — The shadow copies of volume %2 were aborted because of an IO failure on volume %3.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because of an IO failure on volume %3.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618703 — The shadow copies of volume %2 were aborted because of insufficient paged heap.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because of insufficient paged heap.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618704 — The shadow copies of volume %2 were aborted because volume %3, which contains shadow copy storage for this shadow copy, was force dismounted.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because volume %3, which contains shadow copy storage for this shadow copy, was force dismounted.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618705 — An attempt to flush and hold writes on volume %2 was attempted while another flush and hold was already in progress.

Provider: Volsnap
Channel: Unknown

Message

An attempt to flush and hold writes on volume %2 was attempted while another flush and hold was already in progress.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618708 — The shadow copies of volume %2 were aborted because of a failed free space computation.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because of a failed free space computation.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618709 — The flush and hold operation for volume %2 was aborted because of low available system memory.

Provider: Volsnap
Channel: Unknown

Message

The flush and hold operation for volume %2 was aborted because of low available system memory.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618710 — The shadow copy storage volume specified for shadow copies on volume %2 could not be added.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy storage volume specified for shadow copies on volume %2 could not be added.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618711 — There was insufficient disk space on volume %3 to create the shadow copy of volume %2.

Provider: Volsnap
Channel: Unknown

Message

There was insufficient disk space on volume %3 to create the shadow copy of volume %2.  Shadow copy storage creation failed.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618713 — The shadow copies of volume %2 were deleted because the shadow copy storage could not grow in time.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618715 — The shadow copies of volume %2 were aborted during detection because a critical control file could not be opened.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted during detection because a critical control file could not be opened.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618716 — The shadow copy of volume %2 could not be created due to a failure in creating the necessary on disk structures.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 could not be created due to a failure in creating the necessary on disk structures.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618717 — The shadow copies of volume %2 were aborted during detection.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted during detection.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618719 — A control item for shadow copies of volume %2 was lost during detection.

Provider: Volsnap
Channel: Unknown

Message

A control item for shadow copies of volume %2 was lost during detection.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618720 — The shadow copies of volume %2 were aborted because the shadow copy storage volume was not present.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because the shadow copy storage volume was not present.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618723 — The shadow copies of volume %2 were aborted because the shadow copy storage failed to grow.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because the shadow copy storage failed to grow.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618724 — The shadow copies of volume %2 were aborted because the shadow copy storage could not grow due to a user imposed limit.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because the shadow copy storage could not grow due to a user imposed limit.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618727 — When preparing a new volume shadow copy for volume %2, the shadow copy storage on volume %3 could not be located in non-critical space.

Provider: Volsnap
Channel: Unknown

Message

When preparing a new volume shadow copy for volume %2, the shadow copy storage on volume %3 could not be located in non-critical space.  Consider using a shadow copy storage volume that does not have any shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618728 — The shadow copies of volume %2 were aborted because volume %3 has been dismounted.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because volume %3 has been dismounted.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618729 — When preparing a new volume shadow copy for volume %2, the shadow copy storage on volume %3 did not have sufficiently large contiguous blocks.

Provider: Volsnap
Channel: Unknown

Message

When preparing a new volume shadow copy for volume %2, the shadow copy storage on volume %3 did not have sufficiently large contiguous blocks.  Consider deleting unnecessary files on the shadow copy storage volume or use a different shadow copy storage volume.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618736 — When preparing a new volume shadow copy for volume %2, the shadow copy storage on volume %3 did not have sufficiently large contiguous blocks.

Provider: Volsnap
Channel: Unknown

Message

When preparing a new volume shadow copy for volume %2, the shadow copy storage on volume %3 did not have sufficiently large contiguous blocks.  A shadow copy create computation is in progress to find more contiguous blocks.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618747 — The shadow copies of volume %2 were aborted because the shadow copy storage volume was not present in time during a previous session.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because the shadow copy storage volume was not present in time during a previous session.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618748 — The shadow copies of volume %2 were aborted because volume %3, which contains shadow copy storage for this shadow copy, has been taken offline.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because volume %3, which contains shadow copy storage for this shadow copy, has been taken offline.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`DiffAreaVolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618751 — An error occurred while trying to delete a snapshot of %2.

Provider: Volsnap
Channel: Unknown

Message

An error occurred while trying to delete a snapshot of %2.  The delete will be retried at a later time.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618755 — The shadow copy of volume %2 being created failed to install.

Provider: Volsnap
Channel: Unknown

Message

The shadow copy of volume %2 being created failed to install.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618768 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  The shadow copy storage is not present.  This volume will go online and its shadow copies will become available once the shadow copy storage is introduced in the system.  Revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618769 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  An IO error occurred during shadow copy discovery.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618770 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  A shadow copy meta data corruption was detected.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618771 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  A memory allocation failed.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618772 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  A memory mapping failed.  Consider increasing the size of the page file.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618773 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  A read failure occurred during a shadow copy on write operation.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618774 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  A read or write failure to shadow copy storage occurred.  Please ensure that the shadow copy storage is still present in the system.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618775 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  The shadow copy storage has been exhausted.  Please try clearing the protection fault or restart the computer followed by an increase of the shadow copy storage or a removal of unneeded shadow copies.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618776 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  The shadow copy storage was exhausted before conditions permitted it to grow.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618777 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  The shadow copy storage could not be increased as needed.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618778 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618779 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  An error occurred when doing a file system operation.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618780 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  A read or write error occurred.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618781 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  The shadow copy storage was made inaccessible or removed from the system.  Please ensure that the shadow copy storage is present.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618782 — Volume %2 is offline for shadow copy protection.

Provider: Volsnap
Channel: Unknown

Message

Volume %2 is offline for shadow copy protection.  An application attempted to write to the shadow copy meta data.  If this program was run intentionally then turn off protection mode for this volume in order to allow the application (which may be FORMAT) to run.  Please try clearing the protection fault or restart the computer.  If all else fails, revert out of shadow copy protection mode to reclaim the use of the volume while losing the shadow copies.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—

Event ID 3221618784 — The shadow copies of volume %2 were aborted because of an error when disabling BypassIO.

Provider: Volsnap
Channel: Unknown

Message

The shadow copies of volume %2 were aborted because of an error when disabling BypassIO.

Fields

Name	Description
`DeviceName`	—
`VolumeName`	—
`NTSTATUS`	—
`SourceTag`	—
`SourceFileID`	—
`SourceLine`	—
`binary`	—