The system cannot find the path specified

tommytiko · Joined: 15 Nov 2008 Posts: 20

I have frequently occurring problem with one or two profiles, whereby I get errors such as copied below, stating that the sytem cannot find various file paths, but I am able to find the file paths perfectly well in windows explorer. And I am getting VSS errors in the event viewer. Rebooting seems to fix the problem temporarily. Any ideas?

2016-03-20 12:34:20 : Copying file Z:\D drive\dtSearch files\autoarchive\history.ix <to> V:\Clones of Z\Z0 to V\D drive\dtSearch files\autoarchive\history.ix (177.21KB) (Overwriting) ... [Can not open "\D drive\dtSearch files\autoarchive\history.ix". The system cannot find the path specified.] [ERROR].

Immediately before the above error report in the log appears the following in relation to the VSS:

2016-03-20 12:33:57 : Initializing Volume Shadow Copy DLL ...
2016-03-20 12:33:57 : Creating Volume Shadow Copy for Z:\ ...
2016-03-20 12:33:57 : Gathering writer metadata...
2016-03-20 12:33:58 : Initializing writer metadata...
2016-03-20 12:33:58 : Listing writer metadata ...
2016-03-20 12:33:58 : Selecting VSS components ...
2016-03-20 12:33:58 : * Writer 'Microsoft Writer (Bootable State)' is excluded.
2016-03-20 12:33:58 : * Writer 'Microsoft Writer (Service State)' is excluded.
2016-03-20 12:33:58 : * Writer 'MSDEWriter' is excluded.
2016-03-20 12:33:58 : * Writer 'WMI Writer' is excluded.
2016-03-20 12:33:58 : Creating shadow set {cf6cc74e-67b2-40d8-8d0a-052b1d649cfe} ...
2016-03-20 12:33:58 : Adding volume \\?\Volume{8d8abd46-67a2-11e4-bef7-00241dc239ef}\ [Z:\] to the shadow set...
2016-03-20 12:34:01 : Creating the Volume Shadow Copy...
2016-03-20 12:34:06 : Volume Shadow Copy successfully created.
2016-03-20 12:34:20 : Done. Volume Shadow Copy is at

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

Hi, what errors are you getting in the Windows Event Viewer? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

tommytiko · Joined: 15 Nov 2008 Posts: 20

This and similar, all containing "GetVolumeNameForVolumeMountPointW":

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12289
Date: 20/03/2016
Time: 12:34:02
User: N/A
Computer: TOM-I7
Description:
Volume Shadow Copy Service error: Unexpected error GetVolumeNameForVolumeMountPointW( \\?\Volume{23404ed0-edd2-11e5-9f09-00241dc239ef}\, ...). hr = 0x80070003.

For more information, see Help and Support Center at
[the url for this is dissallowed by the forum].
Data:
0000: 53 50 52 44 49 46 46 43 SPRDIFFC
0008: 31 31 31 00 00 00 00 00 111.....
0010: 53 50 52 44 49 46 46 43 SPRDIFFC
0018: 39 36 00 00 00 00 00 00 96......

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

Thanks, have you tried to search for the error on Google? Any good results? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

tommytiko · Joined: 15 Nov 2008 Posts: 20

Yes, I have googled the error, but with no meaningful result so far.

I discovered that a scheduled task was writing to the folder being cloned while the cloning process was taking place, and having rearranged the schedules so that this no longer occurs, I seem to have shaken off the VSS error, but am still getting errors in VV. The error report now reads:

2016-03-22 05:05:59 : ---- Start copying ----
2016-03-22 05:05:59 : -- Copying to target...
2016-03-22 05:05:59 : Initializing Volume Shadow Copy DLL ...
2016-03-22 05:05:59 : Creating Volume Shadow Copy for Z:\ ...
2016-03-22 05:05:59 : Gathering writer metadata...
2016-03-22 05:06:01 : Initializing writer metadata...
2016-03-22 05:06:02 : Listing writer metadata ...
2016-03-22 05:06:02 : Selecting VSS components ...
2016-03-22 05:06:02 : * Writer 'WMI Writer' is excluded.
2016-03-22 05:06:02 : * Writer 'Microsoft Writer (Bootable State)' is excluded.
2016-03-22 05:06:02 : * Writer 'Microsoft Writer (Service State)' is excluded.
2016-03-22 05:06:02 : * Writer 'MSDEWriter' is excluded.
2016-03-22 05:06:02 : Creating shadow set {7333f523-d7cf-4ad7-9eb5-e577aa633773} ...
2016-03-22 05:06:02 : Adding volume \\?\Volume{8d8abd46-67a2-11e4-bef7-00241dc239ef}\ [Z:\] to the shadow set...
2016-03-22 05:06:09 : Creating the Volume Shadow Copy...
2016-03-22 05:06:47 : Volume Shadow Copy successfully created.
2016-03-22 05:07:30 : * SNAPSHOT ID = {e9078972-04a4-43ce-b86a-41b7bba469f1} ...
2016-03-22 05:07:30 : - Shadow copy set: {7333f523-d7cf-4ad7-9eb5-e577aa633773}
2016-03-22 05:07:30 : - Original count of shadow copies = 1
2016-03-22 05:07:30 : - Original volume name: \\?\Volume{8d8abd46-67a2-11e4-bef7-00241dc239ef}\ [Z:\]
2016-03-22 05:07:30 : - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
2016-03-22 05:07:30 : - Originating machine: (null)
2016-03-22 05:07:30 : - Service machine: (null)
2016-03-22 05:07:30 : - Not Exposed
2016-03-22 05:07:30 : - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
2016-03-22 05:07:30 : - Attributes: Auto_Release
2016-03-22 05:07:30 : Done. Volume Shadow Copy is at \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
2016-03-22 05:07:30 : Copying file Z:\D drive\dtSearch files\autoarchive\history.ix <to> V:\Clones of Z\Z0 to V\D drive\dtSearch files\autoarchive\history.ix (184.72KB) (Overwriting) ... [Can not open "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\D drive\dtSearch files\autoarchive\history.ix". The system cannot find the path specified.] [ERROR].
2016-03-22 05:07:30 : Copying file Z:\D drive\dtSearch files\autoarchive\index_d_1.ix <to> V:\Clones of Z\Z0 to V\D drive\dtSearch files\autoarchive\index_d_1.ix (128.00KB) (Overwriting) ... [Can not open "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\D drive\dtSearch files\autoarchive\index_d_1.ix". The system cannot find the path specified.] [ERROR].
2016-03-22 05:07:30 : Copying file Z:\D drive\dtSearch files\autoarchive\index_i_50.ix <to> V:\Clones of Z\Z0 to V\D drive\dtSearch files\autoarchive\index_i_50.ix (7.40KB) [Can not open "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\D drive\dtSearch files\autoarchive\index_i_50.ix". The system cannot find the path specified.] [ERROR].

[and several other file paths that could not be copied, apparently for the same reason - the system cannot find the path specified]

Happily, I have found so far that I can re-run the profile that generated the errors at a later time and the profile has so far re-run without error, whereas the error had always be persistent before, so that only a reboot would fix it.

tommytiko · Joined: 15 Nov 2008 Posts: 20

I have now eliminated the VSS errors and the problem of another program running at the same time which I thought may have been interfering. But I still get persistent errors with the system being unable to find the path specificed, and it would appear from the logs that it is unable to find the shadow copy volume - the log states that the volume is at [blank}. And it appears always to be the same files that are the subject of the error report that the system the system cannot find the path specified. I have also tried splitting up the profiles in case they simply contained too many files, and also checking that there are no excessively long file paths. And I am using the latest version of VV on xp sp3. This is a persistent problem that I have put up with for a long time. Any ideas? It does not seem to be the files themselves, as I find that a different synchronisation program is able to sync them perfectly well, after which VV will complete its sync without reporting any error, since it has not had to copy any files over.

Here is another report:

2016-03-31 10:16:37 : ---- Start Execution ----
2016-03-31 10:16:37 : ---- Backup (Mirror Source to Target) (Source: Z:\J drive\ Target: V:\Clones of Z\Z1 to V\J\) ----
2016-03-31 10:16:37 : ---- Start copying ----
2016-03-31 10:16:37 : -- Copying to target...
2016-03-31 10:16:37 : Initializing Volume Shadow Copy DLL ...
2016-03-31 10:16:37 : Creating Volume Shadow Copy for Z:\ ...
2016-03-31 10:16:37 : Gathering writer metadata...
2016-03-31 10:16:38 : Initializing writer metadata...
2016-03-31 10:16:38 : Listing writer metadata ...
2016-03-31 10:16:38 : Selecting VSS components ...
2016-03-31 10:16:38 : * Writer 'Microsoft Writer (Service State)' is excluded.
2016-03-31 10:16:38 : * Writer 'Microsoft Writer (Bootable State)' is excluded.
2016-03-31 10:16:38 : * Writer 'MSDEWriter' is excluded.
2016-03-31 10:16:38 : * Writer 'WMI Writer' is excluded.
2016-03-31 10:16:38 : Creating shadow set {e14de76d-9f91-41ea-9b25-b63e3a061a96} ...
2016-03-31 10:16:38 : Adding volume \\?\Volume{8d8abd46-67a2-11e4-bef7-00241dc239ef}\ [Z:\] to the shadow set...
2016-03-31 10:16:40 : Creating the Volume Shadow Copy...
2016-03-31 10:16:45 : Volume Shadow Copy successfully created.
2016-03-31 10:16:56 : Done. Volume Shadow Copy is at
2016-03-31 10:16:56 : Copying file Z:\J drive\autoarchive\Autoarchive.pst <to> V:\Clones of Z\Z1 to V\J\autoarchive\Autoarchive.pst (9.95MB) (Overwriting) ... [Can not open "\J drive\autoarchive\Autoarchive.pst". The system cannot find the path specified.] [ERROR].
2016-03-31 10:16:56 : Copying file Z:\J drive\current\CURRENT.pst <to> V:\Clones of Z\Z1 to V\J\current\CURRENT.pst (2.39GB) (Overwriting) ... [Can not open "\J drive\current\CURRENT.pst". The system cannot find the path specified.] [ERROR].
2016-03-31 10:16:56 : Copying file Z:\J drive\current\PKI EMAIL.pst <to> V:\Clones of Z\Z1 to V\J\current\PKI EMAIL.pst (347.56MB) (Overwriting) ... [Can not open "\J drive\current\PKI EMAIL.pst". The system cannot find the path specified.] [ERROR].
2016-03-31 10:16:56 : -- Done: 0 (0) Err: 3 (2.74GB) Skipped: 0 (0) Tot: 3 (2.74GB) --
2016-03-31 10:16:56 : -- Average Transfer Rate: 0/Sec -- Elapsed Time: 0 sec
2016-03-31 10:16:56 : - Deleting shadow copy set {e14de76d-9f91-41ea-9b25-b63e3a061a96} ...
2016-03-31 10:16:56 : Re-comparing ...
2016-03-31 10:16:56 : ---- Copying finished ----
2016-03-31 10:16:56 : ---- End ----
2016-03-31 10:16:56 : - Execution Summary -
2016-03-31 10:16:56 : - Added Files - Source: 0 (0) - Target: 0 (0)
2016-03-31 10:16:56 : - Updated Files - Source: 0 (0) - Target: 0 (0)
2016-03-31 10:16:56 : - Deleted Files - Source: 0 (0) - Target: 0 (0)
2016-03-31 10:16:56 : -- Errors (Updating) - Source: 0 (0) - Target: 3 (2.74GB) [ERROR]

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

OK, something is still wrong with VSS on this machine because the log says:
Volume Shadow Copy is at .......
Here there should be the location of the Volume Shadow Copy.
After that it fails because the location is blank.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

tommytiko · Joined: 15 Nov 2008 Posts: 20

I am not noticing any problems with other VSS based products. And the same files are cloned without difficulty by Beyond Compare and GoodSync. So I wonder whheter the problem is to do with the interaction of VV and the VSS. It seems that the volume shadow copy is being created, but for some reason VV cannot find it. However, if it is the VSS, how may I fix it? I have tried re-registering the VSS in case of that, and I note that a reboot fixes the problem. The problem affects the backup of files that are not open and therefore do not need the vss to be backed up. I have tried setting the VSS to automatic and also starting it before running the profile, but neither of those rather shot in the dark approaches makes any difference. The best improvement I have found so far is to deselect the VSS in the profile properties, which even in the absence of the current problem does not seem to enable the copying of locked .pst files, and it prevents the profile from running even when there are no open files, so it is perhaps no great loss. Having deselected the VSS, the backup runs fine, including when there are open files other than .pst files. I am not sure what use the election to use the VSS is in that case, but in case it has use, do you have any other ideas?