What is wrong when I am told that "hexadecimal value 0x00 is an invalid character. Line 1 Position 1" and this prevents me from opening or checking out a map ?

My computer crashed (yes, it does that from time to time...), and when everything was restored I noticed that a map came up as "checked out".

That was odd, because the first thing I do after a crash is to delete all the files in the local storage, and no information appeared for this map.

Anyway, I was able to check it in, but then unable to open or check it out. Just a message "...hexadecimal value 0x00 is an invalid character. Line 1 Position 1..."

So I restored from an older version. Did not help.

So I restored from an even older version. Did not help.

So I downloaded the map to my C-drive and checked the codes in Notepad. There were no hexadecimal value 0x00 at the top of the file. I then uploaded the map. Did not help.

In the end I had to create a new map. No big deal, but awkward because it is used in very many publications.

Does this sound familiar? What is wrong?

emoji
Parents
  • We've had this happen, but unfortunately I can't find anything in my email history about it. Probably because everyone sends me screen shots instead of actual error message text.

    My best guess is that you have UTF-16 encoded content that isn't being recognized as that. Could be a UTF-16 file that lost its BOM and/or <?xml ...?> declaration. Or a UTF-16 string embedded in data where UTF-8 or something else is expected.

    How this happened due to a computer crash, I have no idea. Maybe the file was under edit and got corrupted?

    emoji
  • Thanks Jay! Yes indeed, I think the damage was done because the file was checked out when my computer decided to go "blue" on me. In this case the UTF codes were good. I compared the codes in the "bad" file with the codes in a "good" file, and since there are not many of them in the top of the file I did establish that everything - including the UTF - were ok.

    emoji
Reply Children
No Data