Windows 10 Pro 1809 PC. Current BETA release. Office 365 HOME account. Chrome browser.
Press ADD backup, give it any name and password, hit next.
Set Storage Type to OneDriveV2, setup AuthID (using Office 365 Home account)
Now put test path into the Path on Server box and hit TEST.
- An accepted path will offer to be created. (Press NO as folder not needed)
- A failed path will kick out the error box as in my earlier post.
(Note I never proceed past this Backup Destination setup page. I just backed out of the half setup config once testing is completed. The [Test Connection] button was all I needed for the path test)
All of the following are legal paths. Plus, Space, Exclamation Marks are all legal for folder names. (And used to work with OneDriveV1)
The error message said “contains invalid trailing character” when the ++ were on the end of the folder name.
The error message also said “contains invalid trailing character” when the ++ were on the start of the folder name.
That does go to imply that the issue only occurs when the “invalid characters” [sic] are at the start or end of the folder name. Perfectly acceptable in the middle of a foldername
Using Percentage Encoding
The use of percent encoding DOES work.
zzBACKUPS/%2b%2bFOLDER did create zzBACKUPS/++FOLDER
zzBACKUPS/FOL%2b%2bDER did create zzBACKUPS/FOL++DER
Other feedback from a noob to this backup
The error messages are SERIOUSLY impossible to read for us mere humans. Any plans to have clearer error messages with the developer info hidden behind an advance button?
Only now when I am reading it after testing have I actually see the text at the end there about “contains invalid trailing character”. it would be REALLY helpful if text like that was highlighted in some way. Or promoted to be the first line.
Or maybe the errors just need a “Translate for ID-10T user” button.