Ошибка xml parsing error not well formed

3

  android:text="@string/hello";

3

1

To solve this issue, I pasted my layout into https://www.xmlvalidation.com/, which told me exactly what the error was. As was the case with other answers, my XML had < in a string.

Remove the semicolon after hello

</android.support.constraint.ConstraintLayout>

0

Answers

• What we see that somehow ASPX file is parsed by XML parser.

  ASPX is not an XML and so this error is expected from XML parser.

  I’d recommend you to go to http://forums.asp.net/ to find why this happens.

All replies

• What we see that somehow ASPX file is parsed by XML parser.

  ASPX is not an XML and so this error is expected from XML parser.

  I’d recommend you to go to http://forums.asp.net/ to find why this happens.

• .ASPX files can be XML and can be parsed using XML parser. Example:

  <%@ Page Language=»VB» %>
  <script language=»VB» runat=»server»>
      Sub Page_Load(ByVal sender As Object, ByVal e As EventArgs)
          ‘Set response to XML
          Response.ContentType = «text/xml»
          Dim dt As New System.Data.DataTable
          Try
              ‘Set connection string
              Dim connStr As String = «Data Source=ServerName;Initial Catalog=DatabaseName;User ID=UserName;Password=Password»
              ‘Set Select statement
              Dim sql As String = «SELECT * FROM caddb.dbo.GetVehicles()» ‘Selects from the table valued function GetVehicles
              ‘Create Data Adapter specifying the select statement and connection string
              Dim da As New System.Data.SqlClient.SqlDataAdapter(sql, connStr)
              ‘Fill the DataTable with data
              da.Fill(dt)
          Catch ex As Exception
              ‘If connection failed, write the error instead
              Response.Write(«<Vehicles><error>»)
              Response.Write(ex.ToString)
              Response.Write(«</error></Vehicles>»)
              Exit Sub
          End Try
          ‘Write the XML Version info not required but is sujested
          Response.Write(«<?xml version=’1.0′ encoding=’utf-8′  standalone=’yes’?>»)
          ‘Write the parent node begin
          Response.Write(«<Vehicles>»)
          For Each row As System.Data.DataRow In dt.Rows ‘Cycle through the rows of the data table
              writeRowXML(row) ‘Write the row to XML
          Next
          ‘Write the parent node end
          Response.Write(«</Vehicles>»)
         
      End Sub
      Sub writeRowXML(ByRef row As System.Data.DataRow)
          Response.Write(«<Vehicle>»)
          Response.Write(»    <lat>» + row.Item(«lat»).ToString + «</lat>»)
          Response.Write(»    <lng>» + row.Item(«lng»).ToString + «</lng>»)
          Response.Write(»    <speed>» + row.Item(«speed»).ToString + «</speed>»)
          Response.Write(»    <heading>» + row.Item(«heading»).ToString + «</heading>»)
          Response.Write(»    <time>» + row.Item(«time»).ToString + «</time>»)
          Response.Write(«</Vehicle>»)
      End Sub
  </script>

  The resulting file would be XML. It would look like this:

  <Vehicles>
  <Vehicle>
      <lat>35.3738301</lat>
      <lng>-97.1908954</lng>
      <speed>0</speed>
      <heading>0</heading>
      <time>12/2/2006 1:42:30 AM</time>
  </Vehicle>
  <Vehicle>
      <lat>35.3838409</lat>
      <lng>-97.1908963</lng>
      <speed>45</speed>
      <heading>180</heading>
      <time>12/2/2006 1:42:30 AM</time>
  </Vehicle>
  </Vehicles>
  

• hi did you ever find a solution to this problem

• Hi,

  .ASPX file itself is not an XML. When you run it, it can produce XML as its output (as in your example). What sergey is saying is, that for some reason instead of the result fo the execution of your ASPX file (which would be an XML) the ASPX file itself is being parsed by the parser. And that fails (as expected).

  This is probably caused by a misconfiguration of the webserver serving the ASPX files (must be set to execute those and not serve them as a content file).

  Thanks,

• I figured of this would be a problem with IIS and went to

  Finally I got it fixed this is what I did.

  Start -> settings -> control panel -> Add Remove Programs
  Selected Add Widows components
  Unchecked Internet Information Server (IIS)
  and clicked on  next to uninstall it

  Once I was uninstalled i followed the same process. This timed checked iis insted of
  uncheck to re install iis

  Start -> settings -> control panel -> Add Remove Programs
  Selected Add Widows components
  Checked Internet Information Server (IIS)
  and clicked on  next

  Again registered .net with iis

  Read More.

  http://muruganad.com/ASP.NET/XML-Parsing-Error-not-well-formed.html

  Thanks!
    Murugan
  www.muruganad.com

  • Edited by

    Tuesday, September 8, 2009 9:52 PM

• This Doesn’t help I still get the error in vs 2008 of

  XML Parsing Error: syntax error
  Location: file:///C:/Users/Matthew.Matthew-PC/Documents/Visual%20Studio%202008/Projects/Go%204%20Ward/special.aspx
  Line Number 1, Column 1:This is a marker file generated by the precompilation tool, and should not be deleted!
  ^

• I recently encountered this issue and it was solved very easy for me. I encountered it to due to a VS2008 Web Deployment Project. I marked for it to create a virtual directory however under the virtual directory settings it did not have a version of ASP.NET selected. Changing this in IIS fixed this occurrence for me.

  InetMGR

  Right click virtual directory < Properties

  ASP.NET

  Change drop down as appropriate.

  • Proposed as answer by
    Chris Marisic
    Monday, September 21, 2009 5:34 PM
  • Edited by
    Chris Marisic
    Monday, September 21, 2009 5:35 PM
    spelling

• This Doesn’t help I still get the error in vs 2008 of

  XML Parsing Error: syntax error
  Location: file:///C:/Users/Matthew.Matthew-PC/Documents/Visual%20Studio%202008/Projects/Go%204%20Ward/special.aspx
  Line Number 1, Column 1:This is a marker file generated by the precompilation tool, and should not be deleted!
  ^

  You are loading an .aspx file from the file system. Load it over HTTP from a web server where ASP.NET is installed then it will work. With Visual Studio you have a development server or you can use IIS.

  ---

  MVP XML
  My blog

• Not sure if you figured out this problem yet but try the following solution.

  Click on Start ->Run and type in the following command if you are using .NET 2.0 framework:
  %Windir%Microsoft.NETFrameworkv2.0.50727aspnet_regiis -i

  Once done the .NET Framework will be reinstalled. Your problem had to do with the fact that you no doubt installed the IIS after installing the .NET Framework. If the .NET Framework is not registered with IIS then it will not parse it properly.

• Thank you. Reinstalling .NET 2.0 solved the issue.

When loading and saving XML data using FromXml() and ToXml() in C++, the data should be in the local C++ code page. If this is not the case then you may get the error ‘Error — not well-formed (invalid token) at line x’.

This may be resolved by building the application as Unicode, or by using FromXmlStream() and ToXmlStream() which deal with Binary Data and converting the data yourself.

XML Encoding

Xml documents can be encoded using a number of different encodings. The type of encoding is indicated using the encoding tag in the document header (i.e. <?xml version=»1.0″ encoding=»UTF-8″?>).

There is also a problem that commonly occurs in C++ UNICODE applications when dealing with UTF-8 encoded data. If you load a UFT-8 encoded file into a UNICODE application, the temptation is to store it in a UNICODE string (WCHAR*), and the conversion to Unicode is often implicit (part of some string/bstr class). However these conversions typically assume the source string is in the local code page, which is rarely UTF-8, and more frequently ANSI. So when the data is converted to UNICODE, the conversion function does not treat the data as UTF-8, and so does not correctly decode it. This results in a UNICODE string which no longer represents the source.

In these circumstances, it is better to either treat the data as binary or to use the appropriate conversion method — utf8 to Unicode.

It is common to want to pass the XML document you have created to a non-Unicode application. If you need to do this then you may look first at ToXml, this will provide you with a UNICODE string, however converting this to an ASCII or ANSI string may cause the corruption of complex characters (you lose information going from 2 bytes to 1 byte per character). You could take the string returned from ToXml, and apply your own UTF-8 encoding, however the encoding attribute in the header (<?xml version=»1.0″ encoding=»UTF-8″?>) would not be present, and the XML parser decoding the document may misinterpret it.

The better solution is to use the ToXmlStream method. This allows you to specify an encoding, and returns a stream of bytes (array of bytes in VB). This byte stream is a representation of the XML Document in the given encoding, containing the correct encoding attribute in the header (<?xml version=»1.0″ encoding=»UTF-8″?>).