Receiving error > "E000101F6: Error 0x101f6: Unable to create volume snapshot<?xml version."
Hi guys...
I've struck a problem with ATI 2019 & the later update...18100.
It's been running very slowly lately but now have the following error...
12/06/2022 02:28:44:647 AM +10:00 3672 E000101F6: Error 0x101f6: Unable to create volume snapshot<?xml version="1.0" encoding="UTF-8" ?>
I tried 3 times but no go.
I even tried un-installing & re-installing both the "normal" & mandatory updated version.
Nope...No joy.
(I have one FULL & two INCREMENTAL set for the 4th, 11th, 18th & 25th of each month then one FULL etc.etc..)
I checked the Advanced options & saw that you could use ACRONIS' & not Window's VSS in case of any errors.
(Not sure of the exact names.)
I'm running it now....so will see how we go.
FWIW...The timer states..."2 1/2 hours to go." Really?
Never used to take that long.
Ta muchly.
Regards, Rajah..
ps. I tried to find this file (dated 2016) to modify but could not find the said file. There is only one SCRIPT entry saved.
It is also possible to disable VSS usage for a particular backup task without touching Windows VSS service itself:1) Open the folder where your backups settings are saved: C:\ProgramData\Acronis\TrueImageHome\Scripts
2) Each file there stores settings for particular backup job.
Open files one-by-one in Notepad, or open latest modified file (if you have just modified your task),
until you find the one that has backup name on 5th line, e.g. MyBackups
3) click Edit - Replace and replace use_vss="true" with use_vss="false"
4) Save changes and close the file.
5) NOTE....You have to do this every time you change or modify your back-up tasks etc.
Is there any way to fix the error?
Hi Steve,
Nice to "see" you again.
You'll be glad to know that the above "use of ACRONIS & not Window's VSS" worked without fail.
It ran for more than 3 hours though. Never took that long before with any version.
I shall try the VSS Doctor tool & report back.
Regs, Rajah..
Hi once more,
Well Steve, here's the report...
2022-06-12 06:04:16 GMT+10:00
AcronisVSSDoctor-net35, 1.1.53.0, v2.0.50727
Microsoft Windows NT 6.1.7601 Service Pack 1, 2.0.50727.8806===========================================================
VSS Services Configuration and StatusStatus: OK
Description: All VSS-related services are configured correctlyServices:
Name: swprv
Title: Microsoft Software Shadow Copy Provider
Status: Stopped
ReferenceStatus:
NeedToFixStatus: False
StartMode: Manual
ReferenceStartMode: Manual
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:Name: VSS
Title: Volume Shadow Copy
Status: Stopped
ReferenceStatus:
NeedToFixStatus: False
StartMode: Manual
ReferenceStartMode: Manual
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:Name: EventSystem
Title: COM+ Event System
Status: Running
ReferenceStatus: Running
NeedToFixStatus: False
StartMode: Auto
ReferenceStartMode: Auto
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:
===========================================================
VSS Access Control ConfigurationStatus: OK
Description: Known VSS access control entries are configured correctlyAccessControls:
UserName: NT Authority\NetworkService
EntryExists: True
UserExists: True
IsActive: True
IsOk: True
StatusDescription:
===========================================================
VSS Components AvailabilityStatus: OK
Description: VSS components are accessible
===========================================================
VSS Writers StatusStatus: Error
Description: An error occurred when performing a checkError occurred:
System.ComponentModel.Win32Exception: This program is blocked by group policy. For more information, contact your system administrator
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Acronis.Utilities.VSSDoctor.Interop.ProcessLauncher.Execute(String executable, String args)
at Acronis.Utilities.VSSDoctor.Interop.VssAdminWrapper.Invoke(String args)
at Acronis.Utilities.VSSDoctor.Collectors.WritersStatusCollector.Collect()
at Acronis.Utilities.VSSDoctor.Launching.Launcher.CollectData(Func`1 cancellationChecker)===========================================================
VSS Shadow Storages StatusStatus: Warn
Description: Some VSS shadow storages are misconfiguredStorages:
ForVolume: C:\
OnVolume: C:\
Used: 62 GB
Allocated: 62 GB
Maximum: 69 GB
Minimum: 320 MB
VolumeSize: 465 GB
Available: 272 GB
TargetMaximum: UNBOUNDED
MaximumGreaterThenMinimum: True
MaximumIsEnough: False
MaximumIsNotReached: False
AvailableIsEnoughForMaximum: True
IsOk: False
Description: Maximum storage size is almost reached
===========================================================
Disk Free Space AvailableStatus: OK
Description: All disks have enough free spaceVolumes:
Name: C:\
DeviceId: \\?\Volume{519f2e98-a380-11df-bbbe-806e6f6e6963}\
Size: 465 GB
Available: 272 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: TrueName: D:\
DeviceId: \\?\Volume{c3c20323-9f1e-11e0-ab60-eb045ef7e0eb}\
Size: 156 GB
Available: 155 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: TrueName: F:\
DeviceId: \\?\Volume{8dbd4ac0-5190-11e6-8646-0040f4756418}\
Size: 309 GB
Available: 309 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: True
===========================================================
Disk I/O LoadStatus: Warn
Description: Some disks may be overloaded. VSS may behave incorrectly under such conditions. Stop heavy operations or wait until completion.Disks:
Name: 0 C:
DiskBytesPersec: 802685
DiskReadBytesPersec: 6554
DiskReadsPersec: 0
DiskTransfersPersec: 169
DiskWriteBytesPersec: 796131
DiskWritesPersec: 168
PercentDiskReadTime: 0
PercentDiskTime: 11
PercentDiskWriteTime: 11
PercentIdleTime: 86
IsOk: FalseName: 1 D: F:
DiskBytesPersec: 0
DiskReadBytesPersec: 0
DiskReadsPersec: 0
DiskTransfersPersec: 0
DiskWriteBytesPersec: 0
DiskWritesPersec: 0
PercentDiskReadTime: 0
PercentDiskTime: 0
PercentDiskWriteTime: 0
PercentIdleTime: 98
IsOk: True
===========================================================
NTFS Volume Access Control ConfigurationStatus: OK
Description: All volumes have correct access control configurationVolumes:
Name: C:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" accessName: D:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" accessName: F:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access
===========================================================
Event LogStatus: Warn
Description: Some VSS-related errors or warnings occurred during the previous dayEvents:
Timestamp: 12/06/2022 2:28:40 AM
Type: Error
Source: volsnap
Message: The shadow copies of volume D: were aborted because of an IO failure on volume D:.
InstanceId: -1073348594
SearchLink: google dot com/#newwindow=1&q=volsnap+event+id+3221618702Timestamp: 12/06/2022 1:01:02 AM
Type: Error
Source: volsnap
Message: The shadow copies of volume F: were aborted because of an IO failure on volume F:.
InstanceId: -1073348594
SearchLink: google dot com/#newwindow=1&q=volsnap+event+id+3221618702
Q?....Why the h#%& is it picking up my D & F HDD's?
By "previous day"...That is just last night at 11.30 PM on the 11th. Had to try 3 times this early AM on the 12th.
My back ups all go to my external G drive.
&...What's with the Group Policy reference?
I'm running WIN 7 Home.....hence no access to the Group Policy options.
(I had to modify both the entries for https google dot com (above ^ ^^ ) coz the forum dis allowed live links or whatever.)
PLUS...Don't forget that I changed the options in ATI ADVANCED options section.
I now have all 3 version 14's & one FULL version 15 on my external "G" HDD.
Weird goingzon. :)
Rajah, couple of immediate thoughts!
First, allow the tool to fix any issues it can, i.e. VSS shadow storages.
Next, do a full Windows restart and re-run the tool to see if the VSS writer issue is resolved or not?
The reference to I/O failures on drives D: and F: would suggest doing a CHKDSK on those volumes to ensure that there are no latent issues.
Beyond the above, then I would suggest running the System File Checker tool (SFC /SCANNOW) from an Administrator level command prompt to see if this finds & fixes any issues caused by corrupt system files etc.
Hi Steve,
re; The VSS Shadow Storage result...
I still get the Group Policy message. Not able to proceed any further with it.
(I just performed a full format of both the "D" & "F", HDD's before restarting the PC. All it did was to reduce the "USED" space/s a tad.)
Nothing bad was found on either HDD.
Results of the last run...
2022-06-13 01:11:42 GMT+10:00
AcronisVSSDoctor-net35, 1.1.53.0, v2.0.50727
Microsoft Windows NT 6.1.7601 Service Pack 1, 2.0.50727.8806===========================================================
VSS Services Configuration and StatusStatus: OK
Description: All VSS-related services are configured correctlyServices:
Name: swprv
Title: Microsoft Software Shadow Copy Provider
Status: Stopped
ReferenceStatus:
NeedToFixStatus: False
StartMode: Manual
ReferenceStartMode: Manual
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:Name: VSS
Title: Volume Shadow Copy
Status: Stopped
ReferenceStatus:
NeedToFixStatus: False
StartMode: Manual
ReferenceStartMode: Manual
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:Name: EventSystem
Title: COM+ Event System
Status: Running
ReferenceStatus: Running
NeedToFixStatus: False
StartMode: Auto
ReferenceStartMode: Auto
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:
===========================================================
VSS Access Control ConfigurationStatus: OK
Description: Known VSS access control entries are configured correctlyAccessControls:
UserName: NT Authority\NetworkService
EntryExists: True
UserExists: True
IsActive: True
IsOk: True
StatusDescription:
===========================================================
VSS Components AvailabilityStatus: OK
Description: VSS components are accessible
===========================================================
VSS Writers StatusStatus: Error
Description: An error occurred when performing a checkError occurred:
System.ComponentModel.Win32Exception: This program is blocked by group policy. For more information, contact your system administrator
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Acronis.Utilities.VSSDoctor.Interop.ProcessLauncher.Execute(String executable, String args)
at Acronis.Utilities.VSSDoctor.Interop.VssAdminWrapper.Invoke(String args)
at Acronis.Utilities.VSSDoctor.Collectors.WritersStatusCollector.Collect()
at Acronis.Utilities.VSSDoctor.Launching.Launcher.CollectData(Func`1 cancellationChecker)===========================================================
VSS Shadow Storages StatusStatus: Warn
Description: Some VSS shadow storages are misconfiguredStorages:
ForVolume: C:\
OnVolume: C:\
Used: 62 GB
Allocated: 62 GB
Maximum: 69 GB
Minimum: 320 MB
VolumeSize: 465 GB
Available: 271 GB
TargetMaximum: UNBOUNDED
MaximumGreaterThenMinimum: True
MaximumIsEnough: False
MaximumIsNotReached: False
AvailableIsEnoughForMaximum: True
IsOk: False
Description: Maximum storage size is almost reached
===========================================================
Disk Free Space AvailableStatus: OK
Description: All disks have enough free spaceVolumes:
Name: C:\
DeviceId: \\?\Volume{519f2e98-a380-11df-bbbe-806e6f6e6963}\
Size: 465 GB
Available: 271 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: TrueName: D:\
DeviceId: \\?\Volume{c3c20323-9f1e-11e0-ab60-eb045ef7e0eb}\
Size: 156 GB
Available: 156 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: TrueName: F:\
DeviceId: \\?\Volume{8dbd4ac0-5190-11e6-8646-0040f4756418}\
Size: 309 GB
Available: 309 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: True
===========================================================
Disk I/O LoadStatus: Warn
Description: Some disks may be overloaded. VSS may behave incorrectly under such conditions. Stop heavy operations or wait until completion.Disks:
Name: 0 C:
DiskBytesPersec: 687762
DiskReadBytesPersec: 6670
DiskReadsPersec: 0
DiskTransfersPersec: 156
DiskWriteBytesPersec: 681092
DiskWritesPersec: 156
PercentDiskReadTime: 1
PercentDiskTime: 14
PercentDiskWriteTime: 13
PercentIdleTime: 82
IsOk: FalseName: 1 D: F:
DiskBytesPersec: 0
DiskReadBytesPersec: 0
DiskReadsPersec: 0
DiskTransfersPersec: 0
DiskWriteBytesPersec: 0
DiskWritesPersec: 0
PercentDiskReadTime: 0
PercentDiskTime: 0
PercentDiskWriteTime: 0
PercentIdleTime: 98
IsOk: True
===========================================================
NTFS Volume Access Control ConfigurationStatus: Warn
Description: Some volumes have incorrect access control configurationVolumes:
Name: C:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" accessName: D:\
SystemHasAccess: False
SystemSid: S-1-5-18
IsOk: False
Description: "SYSTEM" account has no "Full Control" accessName: F:\
SystemHasAccess: False
SystemSid: S-1-5-18
IsOk: False
Description: "SYSTEM" account has no "Full Control" access
===========================================================
Event LogStatus: Warn
Description: Some VSS-related errors or warnings occurred during the previous dayEvents:
Timestamp: 12/06/2022 2:28:40 AM
Type: Error
Source: volsnap
Message: The shadow copies of volume D: were aborted because of an IO failure on volume D:.
InstanceId: -1073348594
SearchLink: https google dot com/#newwindow=1&q=volsnap+event+id+3221618702
Will try the latter tests now...
Hi Steve,
Results are as follows...
The CHKDSK Scan of both "F" & "D" HDD's = nil errors found.
But, the SFC /SCANNOW of my "C" drive found some errors that it could not repair.
The log file is huge. Well over 1.x Meg.
Had trouble finding the latest dated result & could not understand a thing.
The VSS tool appears to give confusing info. though.
Where to now?
Hi Steve,
Thanks. Will do some reading. Pity that it's a tad old.
:)
Rajah, if your Win 7 PC is up to date on Windows Updates, then you can use the following command to check & repair system files (from an Admin command prompt).
DISM /Online /Cleanup-Image /ScanHealth
Hi Steve,
I haven't updated WIN7 for months as I cannot receive any more updates.
Windows refuses to do so & I ain't about to pay for them.
-------------------------------------------
I just finished running the Window's repair procedure (about 3 hours.....), & re-ran the VSS test.
It found & repaired a quite a lot of the data files...plus others...but it could not produce a log file. (#50 error or something.)
Results are as follows...
2022-06-13 06:01:48 GMT+10:00
AcronisVSSDoctor-net35, 1.1.53.0, v2.0.50727
Microsoft Windows NT 6.1.7601 Service Pack 1, 2.0.50727.8806===========================================================
VSS Services Configuration and StatusStatus: OK
Description: All VSS-related services are configured correctlyServices:
Name: swprv
Title: Microsoft Software Shadow Copy Provider
Status: Stopped
ReferenceStatus:
NeedToFixStatus: False
StartMode: Manual
ReferenceStartMode: Manual
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:Name: VSS
Title: Volume Shadow Copy
Status: Stopped
ReferenceStatus:
NeedToFixStatus: False
StartMode: Manual
ReferenceStartMode: Manual
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:Name: EventSystem
Title: COM+ Event System
Status: Running
ReferenceStatus: Running
NeedToFixStatus: False
StartMode: Auto
ReferenceStartMode: Auto
NeedToFixStartMode: False
IsOk: True
ExpectationDescription:
Exception:
===========================================================
VSS Access Control ConfigurationStatus: OK
Description: Known VSS access control entries are configured correctlyAccessControls:
UserName: NT Authority\NetworkService
EntryExists: True
UserExists: True
IsActive: True
IsOk: True
StatusDescription:
===========================================================
VSS Components AvailabilityStatus: OK
Description: VSS components are accessible
===========================================================
VSS Writers StatusStatus: Error
Description: An error occurred when performing a checkError occurred:
System.ComponentModel.Win32Exception: This program is blocked by group policy. For more information, contact your system administrator
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Acronis.Utilities.VSSDoctor.Interop.ProcessLauncher.Execute(String executable, String args)
at Acronis.Utilities.VSSDoctor.Interop.VssAdminWrapper.Invoke(String args)
at Acronis.Utilities.VSSDoctor.Collectors.WritersStatusCollector.Collect()
at Acronis.Utilities.VSSDoctor.Launching.Launcher.CollectData(Func`1 cancellationChecker)===========================================================
VSS Shadow Storages StatusStatus: Warn
Description: Some VSS shadow storages are misconfiguredStorages:
ForVolume: C:\
OnVolume: C:\
Used: 60 GB
Allocated: 62 GB
Maximum: 69 GB
Minimum: 320 MB
VolumeSize: 465 GB
Available: 271 GB
TargetMaximum: UNBOUNDED
MaximumGreaterThenMinimum: True
MaximumIsEnough: False
MaximumIsNotReached: False
AvailableIsEnoughForMaximum: True
IsOk: False
Description: Maximum storage size is almost reached
===========================================================
Disk Free Space AvailableStatus: OK
Description: All disks have enough free spaceVolumes:
Name: C:\
DeviceId: \\?\Volume{519f2e98-a380-11df-bbbe-806e6f6e6963}\
Size: 465 GB
Available: 271 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: TrueName: D:\
DeviceId: \\?\Volume{c3c20323-9f1e-11e0-ab60-eb045ef7e0eb}\
Size: 156 GB
Available: 156 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: TrueName: F:\
DeviceId: \\?\Volume{8dbd4ac0-5190-11e6-8646-0040f4756418}\
Size: 309 GB
Available: 309 GB
Minimum: 320 MB
IsOk: True
Description:
IsMounted: True
===========================================================
Disk I/O LoadStatus: OK
Description: All disks are currently not overloadedDisks:
Name: 0 C:
DiskBytesPersec: 63229
DiskReadBytesPersec: 6720
DiskReadsPersec: 0
DiskTransfersPersec: 13
DiskWriteBytesPersec: 56509
DiskWritesPersec: 13
PercentDiskReadTime: 0
PercentDiskTime: 2
PercentDiskWriteTime: 1
PercentIdleTime: 97
IsOk: TrueName: 1 D: F:
DiskBytesPersec: 0
DiskReadBytesPersec: 0
DiskReadsPersec: 0
DiskTransfersPersec: 0
DiskWriteBytesPersec: 0
DiskWritesPersec: 0
PercentDiskReadTime: 0
PercentDiskTime: 0
PercentDiskWriteTime: 0
PercentIdleTime: 98
IsOk: True
===========================================================
NTFS Volume Access Control ConfigurationStatus: OK
Description: All volumes have correct access control configurationVolumes:
Name: C:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" accessName: D:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" accessName: F:\
SystemHasAccess: True
SystemSid: S-1-5-18
IsOk: True
Description: "SYSTEM" account has "Full Control" access
===========================================================
Event LogStatus: Warn
Description: Some VSS-related errors or warnings occurred during the previous dayEvents:
Timestamp: 13/06/2022 5:38:12 AM
Type: Error
Source: Ntfs
Message: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Spare1.
InstanceId: -1073479625
SearchLink: https google dot com/#newwindow=1&q=Ntfs+event+id+3221487671Timestamp: 13/06/2022 5:38:12 AM
Type: Error
Source: Ntfs
Message: The default transaction resource manager on volume Spare1 encountered a non-retryable error and could not start. The data contains the error code.
InstanceId: -1073479543
SearchLink: https google dot com/#newwindow=1&q=Ntfs+event+id+3221487753
Both the Writer's Status & the VSS Shadow Storages Status cannot be "fixed", coz of the Group Policy. re; Writer's Status.
Status: Warn
Description: Some VSS shadow storages are misconfigured
Both Spare1 & Spare2 HDD's are clean with no errors found.
I'm going to try changing the ADVANCED options in ATI to VSS...NO WRITER (or whatever it's called)
& do an out-of-sequence back-up.
Thanks for the assistance.
Well....That all went well enough.
No errors & was a fairly quick INCREMENTAL B/Up as well.
So....Where to from here?
Still can't fathom the conflicting messages though.
Do I worry about the VSS errors?
What caused them in the 1st place?
Never had any before. Maybe due to the "mandated" update changed something?
Anyway, thanks for the help & for any more ideas you may have, Steve.
Regs, Rajah..
Rajah, I guess that there are only two real options available to you at this point.
Forget VSS and use the older Acronis Snapshot feature.
Do an in place repair install of Windows 7 to try to sort out the VSS issues.
One other option would be to revert back to an earlier point in time where the VSS issues didn't exist, assuming that you have a backup to do so? If doing this, then perhaps would be safest to do the restore to a spare disk drive rather than the original.
Is there a reason why you are still running Windows 7 and haven't upgraded to 10? (The free upgrade from 7 to 10 is still working!).
Hi Steve,
You asked...
"Is there a reason why you are still running Windows 7 and haven't upgraded to 10? (The free upgrade from 7 to 10 is still working!)."
I tried to upgrade a long time ago but struck a few glitches/bumps in the road.
Was going to lose a few of my long time programs & my stand-alone (very old), CANON scanner was not supported.
Besides which...my PC specs didn't match up with their minimum specs.
So, I decided to stay with WIN7 & run "0patch."
Seems to work O.K.
I can't do a System Restore or use an Acronis back-up.
Only keep 3 current & 1 or 2 previous weeklies.
ATI seems to be functioning fine with the VSS Writer option turned off, so I'll call it a day.
Spent many hours on it already.
Got my moderators job to do over at the mozillaZine fora.
Thanks again, Steve.
Stay safe.
Regs, Rajah..