Hi!
I use to sync my folders with Toucan 2 in mirror mode.
I have a network folder in my work PC that i sync every day with my usb key.
I want the folder on the usb key to be up-to-date, so i use the mirror function with "Network Folder" > "USB Key.
Options are:
- Function: Mirror
- File checks: File size & Modified time (but i don't really know what are the best options)
- Other: Retain timestamp & attributes
I was able to perfectly do the operation with Toucan 2 but now i get a "The source path must not be empty" with 3.0.1 or 3.0.2pre. Note that the preview function correctly highlight the files that need to be updated !
Here's a log:
17:58:58 Toucan 3.0.1
Date : 2010-07-19
Nom de l'ordinateur : P463131
Système d'exploitation : Windows XP (build 2600, Service Pack 3)
17:58:58 The source path must not be empty
Écoulé : 00:00:01
Any idea ?
Thanks,
you have any sort of variable in your source path?
I didn't used any script function or variable to do that (or maybe i miss the question ?).
I had the same message since Version 3.0 release. Fortunately I keep the older version.
Córdoba, Argentina
and I found out how to recreate it.
Mirror job (any name), nothing selected in "File Checks", nothing selected in "Other".
No rules selected.
Paths are:
Source: C:\Documents and Settings\User\Desktop\Stuff
Dest: C:\Documents and Settings\User\Desktop\Página
Run it and you'll get the message: "The destination path must not be empty".
Switch paths and you'll get: "The source path must not be empty".
The bug is at the word "Página" (notice the letter "á") (alt + 160)
If I rename that folder to "Pagina" (note that I changed "á" with "a")
(and also change it in Toucan) the bug is gone.
Tested several times with different paths.
Toucan 3.0.2
Win XP SP3
All other jobs run ok.
I hope this helps.
And sorry for the bad english.
Hmmm, my directory contains the following characters: "space", "(", ")" and "-".
It may be linked ?
I just tested with "space", "(" ")" and "-". I get no errors.
Maybe you get the error because your OS is in another language.
Mine is in english.
Do your other jobs work?
Any other special characters between your paths?
OK, i forgot to say that the name also contains "é" and my OS is ran in french, so as Toucan 3.
I've tested to remove the accents from the directory name and it WORKS !
NB: If the subfolders have some accents, it also works. The bug only affect the main folder, selected for the sync process.
Thanks you !
Do you plan to fix this error for the upcoming version ?
Now, i've noticed some more things:
- When using the program in french, the mirror sync does not work correctly. It will copy the new files but won't delete or update the ones that need to be. However, the preview function correctly see what need to be done !
- When doing the same thing in english, all of this work flawlessly !
- The progress bar on the mirror sync often overtake its position on the window.
However, i really appreciate this new version because the sync process is REALLY much faster than before (40s vs 5min).
the same issue
"The source path must not be empty".
the source path is
'C:\Documents and Settings\ABCD\桌面'
'桌面' is chinese
OK, characters with accents seem to be the cause of the problem, but removing them from hundreds of files and folders names is not an option for me and they worked flawlessly with prior versions.
Córdoba, Argentina
Don't worry, the bug only affect the main folder. All the subfolders can have accents !
use:
subst drive: drive:path
to say I am not ignoring this, I am stuck with a GPRS connection at the moment but should be back with broadband at the end of the week, I will then get a fix out asap!
this fixed in the latest pre-release? It should be
The message is gone, but it doesn't sync anything.
And I mean nothing gets moved or copied.
It runs but it does nothing.
Preview works as it should.
Same steps.
Copy, Mirror, Equalize job (it doesn't really matter, nothing moves).
"File Checks" don't matter either (nothing moves).
Nothing checked in "Other", No Rules selected (nor created).
Hope this helps.
thanks, I have got this one fixed now I think, I will probably put out another pre-release today or tomorrow
be fix in this pre-release
Fixed.
Thanks.