- Was able to reach out to COVE support and were able to pinpoint the reparse point causing the issue, So there's a service that's located on a substitute drive which is not a mountpoint, we changed the path of the service to the original path (removed the substitute drive from the path) on the registry and it fixed the issue.
Backup not working due to VSS issue
Our automated backup solutions which is Cove is failing to backup this server, when I checked the event logs I'm getting the following errors
This is Windows Server 2016 running on HYPER-V
Volume Shadow Copy Service error: Unexpected error calling routine GetVolumeNameForVolumeMountPoint is now failing on the volume, winerror 0x00001126. . hr = 0x80071126, The file or directory is not a reparse point. . Operation: PrepareForSnapshot Event Context: Execution Context: Writer Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Name: System Writer Writer Instance ID: {6ab1eb14-07fb-4edb-a839-5096deee558c}
C: - 101GB free out of 200GB
D: - 395GB free out of 800GB
Troubleshooting done:
- Tried to do the following troubleshooting:
Rebooted the server multiple times
Disabled the AV on the server
Run the following
sfc / scannow - Windows Resource Protection did not find any integrity violations
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /checkhealth
dism /online /cleanup-image /restorehealth - getting error 14, I already created the IRPStackSize on regedit with the value of 12
dism /online /cleanup-image /restorehealth /source:WIM:d:\sources\install.wim:2 /limitaccess - cannot find source
Any insights or directions that can help?
Thanks in Advance!
Windows for business | Windows Server | Storage high availability | Other
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.
-
Anonymous
2023-11-20T23:35:20+00:00
5 additional answers
Sort by: Most helpful
-
Anonymous
2023-11-14T09:04:51+00:00 Hi,
The error 0x00001126 ERROR_NOT_A_REPARSE_POINT means the file or directory is not a reparse point.
System Error Codes (4000-5999) (WinError.h) - Win32 apps | Microsoft Learn
It seems your backup application references a wrong path as the mount point of the volume. I think it's better to contact the software vendor to fix the issue.
Best Regards,
Ian Xue
-
Anonymous
2023-11-14T23:12:41+00:00 The problem is, this is a Windows issue - I tried running dir /al /s and run a fsutil query on those directory that showed up and the only reparse point that it can find is
C:>fsutil reparsepoint query C:\Windows\SYSVOL_DFSR\sysvol\xxx.loc
Reparse Tag Value : 0xa0000003
Tag value: Microsoft
Tag value: Name Surrogate
Tag value: Mount Point
Substitue Name offset: 0
Substitue Name length: 66
Print Name offset: 68
Print Name Length: 58
Substitute Name: ??\C:\WINDOWS\SYSVOL_DFSR\domain
Print Name: C:\WINDOWS\SYSVOL_DFSR\domain
Reparse Data Length: 0x00000088
Reparse Data:
0000: 00 00 42 00 44 00 3a 00 5c 00 3f 00 3f 00 5c 00 ..B.D.:..?.?..
0010: 43 00 3a 00 5c 00 57 00 49 00 4e 00 44 00 4f 00 C.:..W.I.N.D.O.
0020: 57 00 53 00 5c 00 53 00 59 00 53 00 56 00 4f 00 W.S..S.Y.S.V.O.
0030: 4c 00 5f 00 44 00 46 00 53 00 52 00 5c 00 64 00 L._.D.F.S.R..d.
0040: 6f 00 6d 00 61 00 69 00 6e 00 00 00 43 00 3a 00 o.m.a.i.n...C.:.
0050: 5c 00 57 00 49 00 4e 00 44 00 4f 00 57 00 53 00 .W.I.N.D.O.W.S.
0060: 5c 00 53 00 59 00 53 00 56 00 4f 00 4c 00 5f 00 .S.Y.S.V.O.L._.
0070: 44 00 46 00 53 00 52 00 5c 00 64 00 6f 00 6d 00 D.F.S.R..d.o.m.
0080: 61 00 69 00 6e 00 00 00 a.i.n...
-
Anonymous
2023-11-16T09:18:49+00:00 Hi,
Please run dir /al /s C:\ to check the reparse points on the C drive or other drives on your computer. If there are no mount points, VSS snapshots are not mounted correctly or they have been unmounted by the backup app.
-
Anonymous
2023-11-17T05:07:44+00:00 Theres no reparse point aside from the sysvol that I posted above , I already deleted the shadows using 'Vssadmin delete shadows /all', rebooted the server and its still throwing the same error on the event log