Hi,
MadCap displays the error - System.XMl.XMlException error. '.'.hexadecimal value 0x00. is an invalid character.
This error occurs when I am trying to build HTML output.
Attached screenshot of the error.
Please assist me in resolving this error.
Regards,
Vijji
System XML XMLexception error
-
Vijayalaxmi
- Jr. Propeller Head
- Posts: 1
- Joined: Tue Oct 15, 2019 5:12 am
System XML XMLexception error
You do not have the required permissions to view the files attached to this post.
-
ChoccieMuffin
- Senior Propellus Maximus
- Posts: 2632
- Joined: Wed Apr 14, 2010 8:01 am
- Location: Surrey, UK
Re: System XML XMLexception error
Did Flare create a build log when this error happened? If so, the last thing it was looking at might be where the problem lies. I'm afraid I can't offer any further suggestions.
Started as a newbie with Flare 6.1, now using Flare 2023.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
-
MarkMetcalfe
- Propeller Head
- Posts: 25
- Joined: Thu Jun 24, 2010 11:57 am
- Location: Nashua, NH
- Contact:
Re: System XML XMLexception error
I saw this in the Printed documentation topic and posted this response, but since i was building an online output, I will repeat my response here. (Admins can do what they like.)
I got this error. I wonder if it has something to do with a bad sector on a disk, or in a file.
I could see nothing wrong with the last file that processed; nothing at Line 19 position 8. So here is what I tried. Maybe you can try it.
I copied my Content and Project folders to folder on another disk, and also to another Temp folder on the same disk. In both cases, one or more folders or files would not copy. For example, if my Target folder would not copy (en masse), I manually created a Target folder at the new location and then copied the files from the old Target folder to the new Target folder - until I found the file that would not copy. (Fortunately, I had a backup of whatever file wouldn't copy, and copied that backup to the new location.) I was able to build the project on both on the new disk and the new Temp folder location without the error.
This doesn't exactly explain WHAT was actually happening or even WHY, but I SUSPECT there was a file corruption somewhere in the project that the error could not pinpoint for me.
Note that my original source project (a genealogic family history) was located and built on an external disk drive, and built with no issues before. As a precaution against a failing drive, I ordered a new external disk drive since my current XDD is several years old.
And always protect your project files with source control and/or backup files!
I got this error. I wonder if it has something to do with a bad sector on a disk, or in a file.
I could see nothing wrong with the last file that processed; nothing at Line 19 position 8. So here is what I tried. Maybe you can try it.
I copied my Content and Project folders to folder on another disk, and also to another Temp folder on the same disk. In both cases, one or more folders or files would not copy. For example, if my Target folder would not copy (en masse), I manually created a Target folder at the new location and then copied the files from the old Target folder to the new Target folder - until I found the file that would not copy. (Fortunately, I had a backup of whatever file wouldn't copy, and copied that backup to the new location.) I was able to build the project on both on the new disk and the new Temp folder location without the error.
This doesn't exactly explain WHAT was actually happening or even WHY, but I SUSPECT there was a file corruption somewhere in the project that the error could not pinpoint for me.
Note that my original source project (a genealogic family history) was located and built on an external disk drive, and built with no issues before. As a precaution against a failing drive, I ordered a new external disk drive since my current XDD is several years old.
And always protect your project files with source control and/or backup files!
Re: System XML XMLexception error
Hi,
I got the same problem, and I think I found what happenned...
I work with Smartgit to version of my work.
I was in a merge process, but it was too late to manage the different conficts of all files, so I closed Flare.
The day after, when I reopen my project, I had the error message "System.Xml.XmlException", and none of my projects could be opened...
As some files (like Recentlinks.xml) were in conflict status, Smartgit add some lines in the files like "<----- OLD FILE"
I just needed to solved my versioning conflict, then I could reopen all my projects...
I wish it can helps...
I got the same problem, and I think I found what happenned...
I work with Smartgit to version of my work.
I was in a merge process, but it was too late to manage the different conficts of all files, so I closed Flare.
The day after, when I reopen my project, I had the error message "System.Xml.XmlException", and none of my projects could be opened...
As some files (like Recentlinks.xml) were in conflict status, Smartgit add some lines in the files like "<----- OLD FILE"
I just needed to solved my versioning conflict, then I could reopen all my projects...
I wish it can helps...
Re: System XML XMLexception error
I also had this error.
The message text was:
"Name cannot begin with the '<' character, hexadecimal value 0x3C. Line 2, position 2."
There were unresolved changes in a few of the files, which created text in line 2 of those files: <<<<<<< Updated upstream
I found it by using VSC and searching in a folder for files with "<<"
Once resolved, the error went away.
The message text was:
"Name cannot begin with the '<' character, hexadecimal value 0x3C. Line 2, position 2."
There were unresolved changes in a few of the files, which created text in line 2 of those files: <<<<<<< Updated upstream
I found it by using VSC and searching in a folder for files with "<<"
Once resolved, the error went away.