One drive doesn't like media name

Post by **Valkrider** » 22 Apr 2016 11:57

Today suddenly OneDrive has complained about a file name. (see the attached screen grab)

I seem to remember reading something about this before but a search of the forum has not turned up anything.

: Screen Shot 2016-04-22 at 11.30.08.png (39.93 KiB) Viewed 5319 times

Ossie57 · Post by **Ossie57** » 22 Apr 2016 12:26

Hi,

I think that you may have invalid characters in the file name.

Here is a list of invalid chararcters that are not supported when syncing to One Drive:

The following characters in file names aren't supported when you sync OneDrive for Business:
# (number sign)
% (percent)
< (less than)
> (greater than)
: (colon)
" (double quote)
| (pipe)
? (question mark)
* (asterisk)

so maybe remove the colon in your file name.

good luck!

Gowermick · Post by **Gowermick** » 22 Apr 2016 12:35

All you need to do, is rename the file and delete everything after '.jpg', so your filename becomes
GBC_1911_RG14_02991_475.jpg

Post by **tatewise** » 22 Apr 2016 12:54

I don't understand how you got colons (:) into your file-name because they are not allowed in Windows file-names at all, ever, never.

Certainly .jpg:Zone.Identifier:$DATA is a very strange file-type.

Gowermick · Post by **Gowermick** » 22 Apr 2016 14:03

Mike,
It obviously originated from a non-Windows system, i.e. A website run on Linux or Unix.

Post by **Valkrider** » 22 Apr 2016 17:48

This is on a Windows 7 system running under a virtual machine on my Mac.

After some more investigation this is a 26 byte file and the original jpg image is still in the folder. I suspect it may be a temporary Mac or VM file that was written and not deleted.

Anyway now deleted and FH and the images are still fine.

Post by **tatewise** » 23 Apr 2016 16:03

Even though it may be a temporary file it should still abide by the Windows filename rules and not use any banned characters such as colon (:).

Should that anomaly be reported to the VM vendor or to Apple?

Post by **Valkrider** » 23 Apr 2016 16:20

Mike

Possibly I will wait until / if it happens again and do some more digging. It is odd as it wasn't the last media file that I added during my FH session it was about half way through. It may have something to do with all files being run from and stored on a Mac drive formatted with the Mac HFS+ file system which allows the colon as a file character unlike the Windows file system which does not allow it.

Post by **tatewise** » 23 Apr 2016 16:22

That sounds OK.

BTW: Colin, did you see the latest Crossover Test Reg Access (13615) posting?

Post by **Valkrider** » 23 Apr 2016 18:01

Mike

Yes I did but I am afraid it will be Monday before I can test it properly as I have a busy evening and day tomorrow.

Family Historian User Group

* One drive doesn't like media name

One drive doesn't like media name

Re: One drive doesn't like media name

Re: One drive doesn't like media name

Re: One drive doesn't like media name

Re: One drive doesn't like media name

Re: One drive doesn't like media name

Re: One drive doesn't like media name

Re: One drive doesn't like media name

Re: One drive doesn't like media name

Re: One drive doesn't like media name