发表新帖
发表新帖

What could be causing an XML Parsing Error: no element found?

前端 未结
关注
15 1839
刺人心
刺人心 2020-12-20 11:49

I recently migrated an ASP site from my dev machine to a live server. All the pages except my FAQ page works just fine, but my FAQ brings up:

XML Parsing Er
相关标签:
15条回答
  • 情深已故
    2020-12-20 12:37

    If you are calling a .vb or .cs script from a .aspx page and get this error, add the following code to the .aspx page. FireFox needs to some semblance of valid mark up apparently. This worked for me.

    <html>
<body></body>
</html>
    0 讨论(0)
  • 爱一瞬间的悲伤
    2020-12-20 12:39

    Maybe there is no XML (XML is a blank string)?

    0 讨论(0)
  • 不知归路
    2020-12-20 12:39

    I ran into this issue when installing my services on a fresh virtual machine. (ie; no other WCF services had been run on this machine, yet.)

    You need to install and add a mapping for WCF Services into IIS. The easiest way to do this is as follows:

    1. Run a command prompt with elevated administrator privileges

    2. In the command prompt, navigate to C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation

    3. Run the command ServiceModelReg.exe -i

    4. Restart IIS by running the command iisreset

    0 讨论(0)
  • 花落未央
    2020-12-20 12:40

    This is a very old thread, but I found this while googling for the same problem and wanted to contribute a definitive answer for anyone else who searches for this in the future.

    I got this error when an exception was thrown while the page directives were being parsed. I updated aspx files from source control, and the developer who checked them in had a different version of a 3rd party library of controls. The Register Assembly page directives referenced a version I didn't have, so the exception was thrown at this point. I'm assuming that this error shows up in the client when an exception is thrown so early in the page request life cycle that nothing at all is sent to the client.

    We are logging all exceptions at the app level in Global.Application_Error, so I was able to get this info from the logs. We grab the last exception with the following code:

    Server.GetLastError().GetBaseException()
    0 讨论(0)
  • 借酒劲吻你
    2020-12-20 12:41

    hey same error occured for me and solution for this error is first open iis manager and then in the iis manager under your server name double click on web service extension and in that if your active server pages is "prohibited" change it to "allow" and now your asp page will run.

    0 讨论(0)
  • 忘掉有多难
    2020-12-20 12:42

    There can be two reason for this. One you may have one or more unclosed HTML tag or you may have not set content type for our response. Read http://chiragrdarji.wordpress.com/2010/02/17/xml-parsing-error-no-element-found/ for more detail.

    0 讨论(0)
 看不清?
提交回复
热议问题