> Changing Global Settings to use Transacational File Copy appears to have
resolved the copy failure
This must be about a different error message than the intial one. Turning
transactional copy off may skip problems when renaming the .ffs_tmp to its
real name. The first error message was during file copy.
Windows Error Code 58
-
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
- Posts: 16
- Joined: 23 Mar 2012
Yes. I was facing Error 33 when copying pst files, because they appear to be
locked occasionally by Outlook Instant Search. I found that pushing "Retry"
would allow the batch process to resume and complete, but the file which was
initially locked did not get copied (there are several pst files in the
Outlook folder). Selecting Transactional File Copy under Global Settings
appears to enable FreeFileSync to copy the originally-locked pst file on
Retry.
locked occasionally by Outlook Instant Search. I found that pushing "Retry"
would allow the batch process to resume and complete, but the file which was
initially locked did not get copied (there are several pst files in the
Outlook folder). Selecting Transactional File Copy under Global Settings
appears to enable FreeFileSync to copy the originally-locked pst file on
Retry.
-
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
If "transactional copy" is active, FFS first copies the file to a temporary,
then renames it. If it is inactive, FFS copies directly to the target file. So
the difference between the two is only the rename operation, (which is also
known to create "access denied" errors in some cases). I do not see how
changing this setting could avoid "error code 33", since this error happens
during the file copy phase and not during file renaming later. So the problem
is probably not fixed yet.
then renames it. If it is inactive, FFS copies directly to the target file. So
the difference between the two is only the rename operation, (which is also
known to create "access denied" errors in some cases). I do not see how
changing this setting could avoid "error code 33", since this error happens
during the file copy phase and not during file renaming later. So the problem
is probably not fixed yet.
- Posts: 16
- Joined: 23 Mar 2012
Understood. Unfortunately, my last few posts addressed two separate (but
related) issues, and I think that caused some confusion. The workaround which
I am using for Error 33 is to automate the "Retry" button. So far, that is
working. The other issue is that -- on Retry -- files which were locked when
the initial batch was attempted may not be copied. There is no more Error 33
at that point. But it seems that enabling Transactional File Copy makes
FreeFileSync copy the previously-locked file. At any rate, that is my
preliminary report on a small sample of trials. If anything new develops, I
will post it.
related) issues, and I think that caused some confusion. The workaround which
I am using for Error 33 is to automate the "Retry" button. So far, that is
working. The other issue is that -- on Retry -- files which were locked when
the initial batch was attempted may not be copied. There is no more Error 33
at that point. But it seems that enabling Transactional File Copy makes
FreeFileSync copy the previously-locked file. At any rate, that is my
preliminary report on a small sample of trials. If anything new develops, I
will post it.
