Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

Symptoms

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:
InfoPath cannot open the following file: YourWebForm.aspx.
The file is not a valid XML file.
When you click Show Details, you receive an error message that is similar to the following:
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 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.

Note In the Show Details box, you notice that this is the source code of the ASP.NET Web page.

↑ Back to the top


Cause

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.

↑ Back to the top


Workaround

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.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

Steps to reproduce the problem

  1. Start Microsoft Visual Studio .NET 2003.
  2. On the File menu, click New, click Visual C# Projects, and then click ASP.NET Web Application.
  3. In the Location box, type InfoPathTest, and then click OK.
  4. In the Solution Explorer pane, right-click WebForm1.aspx, and then click View Code.
  5. Add the following Visual C# code to the Page_load method:
    Response.Charset = "";
    Response.ContentType = "text/xml";
    Response.Write("<?xml version=\"1.0\" encoding=\"UTF-8\"?><?mso-infoPathSolution solutionVersion=\"1.0.0.1\" href=\"<path to Manifest.xsf or to a .xsn file>\"  PIVersion=\"1.0.0.0\" productVersion=\"11.0.5120\" ?><?mso-application progid=\"InfoPath.Document\"?><my:myFields xmlns:my=\"http://schemas.microsoft.com/office/infopath/2003/myXSD/2003-03-25T19:43:06\" xml:lang=\"en-us\"><my:field1>some text</my:field1></my:myFields>");
    
  6. On the Debug menu, click Start.
  7. When you click Open, you receive the error message that is mentioned in the "Symptoms" section.

↑ Back to the top


Keywords: KB892951, kbprb, kbtshoot, kbnofix, kbbug, kbaspnet, kberrmsg

↑ Back to the top

Article Info
Article ID : 892951
Revision : 3
Created on : 9/22/2011
Published on : 9/22/2011
Exists online : False
Views : 352