Hi. I get "error code 32. The process cannot access the file because it is being used by another process. (CopyFileEx)"
I'm running FreeFileSync 6.8 on windows 7 sp1 64-bit. Its a mirror operation from 1 NAS to another NAS. It doesn't happen on all files, just some. Obviously, I need a perfect mirror if my backup is going to work. I'm running it from Task scheduler as a batch file with highest privileges.
Is there a fix?
Here is the full boring error: (using FreeFileSync6.8 Build Aug. 1 2014 Unicode x64.)
[11:56:10 PM] Info: Creating file "Y:\Public\My backups\Dell2014July.tib"
[12:02:11 AM] Info: Cannot read file "Z:\My backups\Dell2014July.tib".
Error Code 32: The process cannot access the file because it is being used by another process. (CopyFileEx)
Cannot access the Volume Shadow Copy Service.
Error calling "backupComp->AddToSnapshotSet": VSS_E_OBJECT_NOT_FOUND Volume: "\\?\UNC\192.168.1.4\Public\"
=> Automatic retry in 70 seconds...
yeah, even the retries fail the same way...
Error Code 32: The process cannot access the file because it is being used by another process. (CopyFileEx)
- Posts: 5
- Joined: 23 Aug 2014
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
"Translated" the error message is:
"\?\UNC\192.168.1.4\Public\" does not correspond to an existing volume or remote file share.
Does this make sense in your scenario?
"\?\UNC\192.168.1.4\Public\" does not correspond to an existing volume or remote file share.
Does this make sense in your scenario?
- Posts: 5
- Joined: 23 Aug 2014
Yes. That makes sense. I don't know what the "\?\UNC\" part means but "\192.168.1.4\Public\" is my Y:-drive. (which does exist).
- Posts: 5
- Joined: 23 Aug 2014
sorry - "\192.168.1.4\" is my Z-drive
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
MSDN says:
Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server
2008, Windows XP, and Windows Server 2003: Remote file shares
are not supported until Windows 8 and Windows Server 2012.
If pwszVolumeName is a UNC share path, the server name
portion must be in hostname or fully qualified domain
name format. UNC share names with IP addresses must be normalized
So the issue is probably that Shadow Copies are simply not supported. You could still test hostname or FQDN syntax instead of "192.168.1.4", which seems to be the biggest obstacle.
Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server
2008, Windows XP, and Windows Server 2003: Remote file shares
are not supported until Windows 8 and Windows Server 2012.
If pwszVolumeName is a UNC share path, the server name
portion must be in hostname or fully qualified domain
name format. UNC share names with IP addresses must be normalized
So the issue is probably that Shadow Copies are simply not supported. You could still test hostname or FQDN syntax instead of "192.168.1.4", which seems to be the biggest obstacle.
- Posts: 5
- Joined: 23 Aug 2014
Not supported? Aren't network drives the "latest" thing to use for home backups? I can't be the only one doing this.
Well, thank you for your quick replies - I appreciate it.
Well, thank you for your quick replies - I appreciate it.
- Posts: 5
- Joined: 23 Aug 2014
Follow up: I want to link this thread as it describes the same problem (I think). thx.
BUG: Starting FreeFileSync.exe from another process yields Error Code 32
viewtopic.php?t=1716
BUG: Starting FreeFileSync.exe from another process yields Error Code 32
viewtopic.php?t=1716