Hi,

The only time I've seen that error is when loading a file that contains non-printable characters within an xml value (such as a separator in an input connector definition), an issue I was assured by MS was to be fixed. I'd suggest opening the file in textpad & having a look at the hex matching that position, you may find something in there below the value x0D