Author |
Message |
wjwj Guest
|
Posted: Sun Oct 14, 2012 10:32 am Post subject: Bug in checking archive |
|
|
Hi,
I found ViceVersa on Tucows a few weeks ago and today purchased a licence. As far as I remember the Tucows version was 2502, now I use 2510 (64-bit).
Unfortunately it seems that the archiving function is buggy. I get tons of "The system cannot find the path specified"-errors when ViceVersa is checking the archive folder.
I backup on a network share, so it says "\\backupserver\backups\archive\filename.ext*.* : The system cannot find the path specified." When looking manually on the network share there "\\backupserver\backups\archive\filename.ext_(date_DEL_T).ext" exists.
It seems that this error occures for every single file in my archive.
Could you please provide info on how to resolve this. It seems that it worked in 2502 evaluation version, now I have to press enter ~100 times or to kill ViceVersa in task manager.
Thanks! |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8759
|
Posted: Tue Oct 16, 2012 2:59 am Post subject: |
|
|
Hi, thank you for purchasing ViceVersa. The error is strange, what type of drive is on the network? If you write to support @ tgrmn.com we can send you the build you were using before to check if that is working OK. thanks _________________ --
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
Back to top |
|
|
Guest
|
Posted: Wed Oct 17, 2012 8:20 pm Post subject: |
|
|
I'd like to thank you for your response. I provided the requested information yesterday via e-mail (around this time) and wrote another mail including some screenshots today. The error is persistent in build 2511. |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8759
|
|
Back to top |
|
|
wjwj Guest
|
Posted: Sat Nov 10, 2012 5:38 pm Post subject: |
|
|
Just to give an update. This error was NOT related with ViceVersa, it acutally was/is a bug on my NAS. The NAS incorrectly handles paths on encrypted shares. In total contrast to the UNC path standard it handles paths case sensitive and this causes the problems with ViceVersa. |
|
Back to top |
|
|
|