Data at the root level is invalid. Line 1, position 40.

jemel · Post by **jemel** » Thu Nov 12, 2009 1:16 am

Hi,
This error message has become quite common in my project. When I open the file in Flare's internal text editor, I see nothing wrong on line 1. I have no idea what has happened, since the files seemed to work a couple of days ago (before my entire team got the latest patch for Flare 5). We use CVS as our version repository.

Is there anyone out there who knows what the problem might be?

Best regards,
Jenny

Post by **NorthEast** » Thu Nov 12, 2009 4:44 am

Since you say it happened straight after installing the patch; the first thing I would try is to use an un-patched Flare v5, and see if you get the same message.

jemel · Post by **jemel** » Thu Nov 12, 2009 7:51 am

Sorry, I was unclear on that, it did not happen directly after that. It turned out that one of my team members had not updated to this version (for him it did not work) and for one of my team members who had updated, it worked. On my computer it does not work.

KevinDAmery · Post by **KevinDAmery** » Thu Nov 12, 2009 10:39 am

Sorry, still not clear: you say it doesn't work on your system, but I'm not clear on whether you have patched your system or not.

If you haven't, it sounds like the solution is to patch everyone's installations, since the one system you confirmed has the file working has been patched.

jemel · Post by **jemel** » Fri Nov 13, 2009 1:14 am

Sorry for being so confusing. We now all have the latest patches. But it is on my machine only that we get this problem. It is not a new problem entirely, since we have had problems with Flare reading files before. I get this error message for all files that I try to open in my project.

Now, however, we noticed that one of the TOC-files had strangely formatted links (little squares are put into the file). As soon as the strangely formatted links were removed from the TOC-files, we were able to open the other topic-files. But, why is it that we constantly seem to be getting corrupt TOC-files? In our group, two of us use Windows XP and one of us use Windows Vista. The one with Windows Vista seems to have less trouble that the ones with Windows XP. We use CVS as our versioning system. Most of the time when we check in our TOC-files into CVS, they become corrupt, and we need to send them between us in a mail.

Our theory is that it is Flare that changes the TOC-file to utf-16 and that way CVS handles the file as a binary file. But where in the process does Flare change the coding for the file? And why? And why is it impossible to open a regular topic-file when a TOC-file is corrupt?

helen · Post by **helen** » Fri Nov 13, 2009 2:59 am

jemel wrote:Our theory is that it is Flare that changes the TOC-file to utf-16 and that way CVS handles the file as a binary file. But where in the process does Flare change the coding for the file? And why? And why is it impossible to open a regular topic-file when a TOC-file is corrupt?

This thread may help you: http://forums.madcapsoftware.com/viewto ... =13&t=8765

Please report it as a bug (add to the weight to get it fixed).

MadCap Software Forums

Data at the root level is invalid. Line 1, position 40.

Data at the root level is invalid. Line 1, position 40.

Re: Data at the root level is invalid. Line 1, position 40.

Re: Data at the root level is invalid. Line 1, position 40.

Re: Data at the root level is invalid. Line 1, position 40.

Re: Data at the root level is invalid. Line 1, position 40.

Re: Data at the root level is invalid. Line 1, position 40.