Hi Stefan,
I'm having an issue reported elsewhere (#124, #128, #150) where some files are being encrypted and uploaded, others are not. The log will say "Encrypting"... on the first line for the file and then "Failed to encrypt file" on the next line for each file. There are a lot of files this is happening to.
I'm backing up
From: E:\Data\Development
To: O:\CryptSync\Development
No character length issues for the path and file name.
Let me know what data I can get to you to assist.
Thanks!
Not sure if it's relevant, but I've mapped O: to my OneDrive for Business online cloud storage.
Folder and files can be written without issue, and all of the files CryptSync can encrypt are being uploaded successfully to the O: drive.
I'll let it run the whole way through for this folder and will then look at the log file to see if there are any file types in particular that are failing to encrypt.
Add #169 to the list of Tickets with that behaviour.
I have the same problem with T-Online Magenta Cloud and with GMX Cloud. I have tried to copy the directory structure before synch and that works for me!
With
you can create the directory structure in the cloud.
When I do this before starting the synch the files are encrypted. Maybe you will try that to see if it is the exact same problem in OneDrive.
Interesting, thanks Fritz, I'll check that out. I'm playing with another program called GoodSync as well, I note it creates the folder structure first before sync'ing, may be on to something there.
Stefan, could you add an option (or a default even) to create the folder structure first before syncing the files?
I've also determined that OneDrive for 365 (aka Sharepoint) also has illegal characters that cause errors when sync'ing, some of which Windows itself can handle: http://tinyurl.com/q8lb3r9
2016: " # % * : < > ? / \ |
2013: ~ " # % & * : < > ? / \ { | }.
To get around this I've found a program pfrank which works brilliantly at renaming folders/files locally: http://www3.telus.net/pfrank/. That being said you could probably turn on "Encrypt File Names" to get around this, though probably doesn't encrypt the folder names if you have illegal characters in them.
Intermediate folders are automatically created with the API SHCreateDirectory
dup of [#169]
Related
Tickets: #169