The biggest problem I've had setting up Syncdocs (and working with Windows file system) is handling the error that occurs when a file path is to long. When Syncdocs scans either the local drive or the Google Drive and finds path names that are too long, it would be great if it could produce a report with links to the offending files and an indication of how much shorter the path name would have to be in order to sync correctly. I had to do this manually by scanning through the error report.
Handling file path names that are too long(7 posts) (5 voices)
Thank you for the suggestion. We will add this as a debug reporting option in future. We are hoping to be able to bypass this Windows path length limitation in the next version of Syncdocs, as it is an increasing annoyance, however, this means we will lose XP compatibility or require a .NET library upgrade.
For detecting long paths in windows, I am using the old version of Path scanner which was (is?) free : http://www.parhelia-tools.com/products/pathscanner/PathScanner.aspx
Another tip I use is to put what I want to save in google drive in a main root folder called :
The short name allows me reduce the number of "too long files" to rename. ;)
Thanks for the tip about path scanner. Although it's a bit tricky to read, the Syncdocs log file has an error entry for all the long paths. I just worked through these. Luckily they were all in an archive that's not used very often so I just moved one of the folders in the path to the root directory, zipped it and moved it back. This allowed the sync to work fine.
Long Path Tool is a best software to solve this issue. 5++ Rating. Long Path Tool is a best software
it is a free software. You can Try itPosted 1 year ago #
You can also checkout long path tool, it's an automated software for this type of errorsPosted 8 months ago #
You must log in to post.