my code trip » ASP.Net

Fix for ‘XML Parsing Error: not well-formed Line Number 1, Column 2′ Error

Shiva — Tue, 27 Mar 2007 01:33:41 +0000

When you access an ASP.NET page in your browser, you may get an XML Parsing Error that says that the XML is not well formed. The error message also displays the page directive statement present in the 1st line of the .aspx file. First we will fix this error, then we will look at one possible reason why you may be getting this error in ASP.NET.

Fix the ‘XML Parsing Error’

Click Start > Run, and type the following command depending on which ASP.NET framework is in use by the default web site in your IIS.

ASP.NET 2.0 Framework

%Windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

ASP.NET 1.1 Framework

%Windir%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

You should see a command window that is displayed briefly, that shows that ASP.NET is being installed. After the registration is successful, the window will be closed.

Now refresh the .aspx page that you got the XML Parser error for in the browser and your page should be rendered correctly.

Why did you get this error ?

I have seen this error happen to me in situations where I had installed IIS after the installing the .Net Framework. This make sense. If you install IIS after you install the .Net Framework, then the framework is not registered with IIS. So when a request for a .aspx page comes to IIS, it simply passes on the contents of the page as-is without processing it. So in effect, the browser receives the entire .aspx page’s code, tried to parse it as an XML file, encounters the parsing error at the second character in the page directive and stops.

Related: ASP.NET IIS Registration Tool

Fix for ‘A potentially dangerous Request.Form value was detected from the client’ Error

Shiva — Wed, 27 Dec 2006 02:44:38 +0000

When you access one of your ASP.NET web pages, if you get an error message that says something in the lines of ‘A potentially dangerous Request.Form value was detected from the client’, then you are most likely passing < or > in the querystring parameters.

Allegedly Microsoft introduced this check in ASP.NET 1.1 to prevent scripting attacks. So how do you fix this ?

Fix the ‘A potentially dangerous Request.Form value was detected…’ Error

Open the .aspx page in a text editor or in Visual Studio 2003.
In the Page directive, add the following

validatePageRequest=”false”

Example:

<%@ Page language=”c#” Codebehind=”Software.aspx.cs” AutoEventWireup=”false” Inherits=”Setup.Software” validatePageRequest=”false”%>

Save and close the .aspx file. This should fix it.
This fix is only for that individual page. If you wanted to make this default for all your pages, then add the following in your section of your web.config file.

validateRequest=”false” />

Error Solution: Fix for ‘Unrecognized configuration section connectionStrings’ Error in ASP.NET 2.0

Shiva — Tue, 28 Nov 2006 02:40:38 +0000

After publishing your website in ASP.NET 2.0 using the Build > Publish Website in the Visual Studio 2005 IDE, when you try to access your application for the first time in the browser, you may get the “Unrecognized configuration section ‘connectionStrings’” error. This is because ASP.NET has introduced the new section in the web.config which will not be recognized in the .NET 1.1 framework.

If you look closely at the error message, IIS is trying to run the application using the 1.1 framework.

Fix the configuration section connectionStrings error.

Open IIS and browse to the website under computer_name > Web Sites > Default Web Site > website_name.
Where website_name is the actual name of the website, in this case the MyForecast website.
Right click website_name. Click Properties.
Click the ASP.NET.

From the ASP.NET Version dropdown, select 2.0… version and Click OK.
Now, if you visit your application main page, it should work !

(Note, you may need to restart IIS)

How to restore the Visual Studio 2005 Intellisense if it has disappeared from your Web.Config ?

Shiva — Mon, 27 Nov 2006 00:05:10 +0000

After you launch the ASP.NET configuration tool in Visual Studio 2005 by clicking Website > ASP.NET Configuration menu option, you might encounter a problem wherein the Intellisense within the web.config file has disappeared mysteriously.

This is because the ASP.NET Configuration application that you launched earlier adds the XML Namespace to your web.config as follows.

You can delete xmlns everytime you launch the ASP.NET Configuration application, or you can fix this issue once and for all by doing the following.

Open the WebAdminPage.cs file located at
%windir%\Microsoft.NET\Framework\v2.0.50727\ASP.NETWebAdminFiles\App_Code in Visual Studio or in a text editor.
In the SaveConfig method, change the assignment at line 93 from

config.NamespaceDeclared = true;

config.NamespaceDeclared = false;

Save and close the WebAdminPage.cs file.

If you run the ASP.NET configuration tool now, you will see that it does not add the XML namespace and so your intellisense will not disappear !