File could not be accessed error.

[CJM]

I am syncing a drive that I have been doing for many months. Lately however some of the files are getting the following error:

[Can not read data from “”. The file could not be accessed.] [ERROR]. Skipped.

I have full Windows permissions to all the files. This file names are not very long or have any special characters in them. The files are not in use since Vice Versa would tell you with a different error message. What else could be causing this error on these files?

[TGRMN Software]

What type of drives are these? I assume you are using VV PRO 1.3.1
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[CJM]

I am using the current version of 1.3.1 Pro.

The drives are mapped drives coming through a VPN network. I've been doing this setup for over 1 year, but only in the last month or so has this been a problem. I don't think the VPN is cutting out since VV will continue copying other files without any errors.

I'm thinking of uploading to an online storage sever at work, and then pulling the files from that server to my home computer instead of using the VPN. Can anyone recommend a online storage provider?

Thank you.

[RDS]

I am having the same problem and have noticed that it only occurs on larger file sizes over 6Mb.

[Mark]

We've been experiencing the same problem using the same version over the last several months with a few differences. Our jobs compare and sync data base files from server to laptop(s). Copying data to laptops with a Win2K OS work fine. However, files over 1GB in size will not copy to our laptops having an XP OS. We've changed the sync and compare methods many different times in an effort to get the files across without success. Deleting the file on the target and running a sync method of Replication(Augment) is the only method that is successful no matter whether a scheduled task or a 'run now' task. What might we try to solve this problem. VV had worked flawlessly until this most recent problem. Any ideas?
_________________
Mark

[TGRMN Software]

Did you try to make the copy buffer smaller and to switch on "Flush buffer wevery write" ? These settings are in the advanced sync settings.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[Mark]

Update - We've been testing the latest suggestion without any kind of consistent success. FYI - as an addendum to your suggestion we also increased the buffer size in our testing with the same failure results. So, we've begun using Xcopy to get our database files copied and continue to use Vice Versa for other copy jobs. While we're still getting inexplicable errors we've not been able to determine if they might be network stability issues or if they're due to problems with Vice Versa. Question - along with flushing out the buffer after writing would it actually we wiser to decrease buffer size in order to slow down the amount of data being copied rather than increase it if we're continuing to see the same error message?

Thanks for your help, Mark
_________________
Mark

[TGRMN Software]

If increasing the buffer size does not help, I suggest to leave to the default value.

BTW did you try the new Viceversa PRO 2 ? Same results ?
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[anafletcher88]

Has anyone used longpath tool? I need reviews for it.