Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
When the Response.Charset property is set to NULL on an ASP.NET Web page, the source code of the Web page is returned instead of the Response content body if you try to open a form in Office InfoPath
Article ID: 892951 - View products that this article applies to.
You visit a Microsoft ASP.NET Web page that contains the Response.Charset property set to NULL. When you try to open a form in Microsoft Office InfoPath 2007 or in Microsoft Office InfoPath 2003 from the Web page, you receive an error message that is similar to the following:
When you click Show Details, you receive an error message that is similar to the following:
InfoPath cannot open the following file: YourWebForm.aspx.
The file is not a valid XML file.
Note In this error message, YourWebForm.aspx is the name of the Web form that you are trying to open. YourWebApp is the name of the ASP.NET Web application.
The form contains XML that cannot be parsed:
A name was started with an invalid character.
Line 1, Position 2
<%@ Page language="c#" Codebehind="YourWebForm1.aspx.cs" AutoEventWireup="false" Inherits="YourWebApp.YourWebForm" %>
Note In the Show Details box, you notice that this is the source code of the ASP.NET Web page.
This problem occurs when you have read and write permissions to the file on the computer that is running the ASP.NET Web application. Typically, this problem occurs when you have administrator rights or if you are a member of the VS Developers group on the computer that is running the ASP.NET Web application. When you try to open the form in InfoPath, the actual source code of the ASP.NET Web page is returned.
Note Only users who are developing the application will experience this behavior. Users who are not developing the application and are just opening the .aspx page will not experience this behavior.
To work around this problem and to load the InfoPath form correctly, you must access the ASP.NET Web application by using an account that does not have read and write permissions to the ASP.NET Web page.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Steps to reproduce the problem