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
  • Sometimes this is caused, not by an invalid character in the file but in the object's title in Tridion Docs. If you open the properties, copy the text out and paste in  a text editor, ensure that there are no leading spaces in the object title, and copy the text back into the object title field, that will often clear the issue. This was especially the case with publications in Reach (the older review environment).

    emoji
Reply
  • Sometimes this is caused, not by an invalid character in the file but in the object's title in Tridion Docs. If you open the properties, copy the text out and paste in  a text editor, ensure that there are no leading spaces in the object title, and copy the text back into the object title field, that will often clear the issue. This was especially the case with publications in Reach (the older review environment).

    emoji
Children