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

Question

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         


        

Answer 1

I had the same issue. It was caused because I handled exceptions in global.asax, and called Server.ClearError(), without calling a Response.Redirect or similar. I guess, that the code failed and the error was removed, so asp.net could not display an errormessage, nor could could it display the requested page.

I have also received this error, because I overrided the render method of the page, and forgot to call base.render(writer), thus sending an empty page to the browser.

Answer 2

I had this problem on all of my pages when I deployed to IIS, solution turned out that the account the app pool was running under didn't have enough privileges to connect and execute database queries

Answer 3

I found this issue because URL was redirecting to a different location. Correcting that resolved the issue.

It was redirecting to http://localhost/forms/abc.aspx, however it should have been redirected to http://localhost/projectname/forms/abc.aspx

Answer 4

The site is developed in ASP.NET, not XML. Does this have any bearing on the problem?

Answer 5

I was facing the same issue. My solution may not apply to ASP.NET, I am working in node/express land. My API endpoint was not returning any data in the response:

return res.status(200).end();

When I included something in the data response it resolved the issue:

return res.status(200).send('ok').end();

Answer 6

Maybe some encoding problems, corrupted 'unicode sequence' in the beginning of your file or something of this nature?