Description of the InfoPath 2007 hotfix package: June 29, 2007

Issues that the hotfix package fixes

This hotfix fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

• Consider the following scenario:
  • You enable the Open in the browser setting in an InfoPath Forms Server.
  • You create a form that can be opened in a browser or in InfoPath 2007.
  • You save the form to a document library on the InfoPath Forms Server.
  • You click the hyperlink to the form in the document library.
  In this scenario, the form opens in InfoPath and not in a browser.
• Consider the following scenario:
  • You create a browser-enabled form and then add a file attachment control to the form.
  • You publish the form to a Microsoft Office SharePoint Server 2007 document library with or without using InfoPath Forms Server.
  • You upload documents that have file names that use DBCS characters, such as Korean or Chinese characters.
  • You double-click one of the files to download the file by using Internet Explorer.
  In this scenario, the file name is scrambled. Additionally, the file cannot be opened unless you replace the file name extension with the correct file name extension for the file type, such as ".doc" for a Microsoft Word document or ".xls" for a Microsoft Excel spreadsheet file.
• You complete an InfoPath 2007 form and then save the resulting .xml file to a SharePoint Server document library. Then, you try to open the .xml file in a browser. When you do this, you may receive the following error message:
  This form template is not currently browser-enabled. It must either be republished as a browser-enabled form, or opened using Microsoft Office InfoPath 2007.
  This issue occurs if one of the following conditions is true:
  • The form was saved by using a fully qualified domain name to a SharePoint Server document library that has Alternate Access Mapping (AAM) functionality enabled. Then, you used NetBIOS or the URL of the file location to open the file.
  • The form was saved by using NetBIOS to a SharePoint Server document library that has AAM functionality enabled. Then, you used the fully qualified domain name of the file location to open the file.
• When you try to open a form in a browser, you may receive a parsing error.
  
  This issue occurs when the CharSet header for the form is not sent to the InfoPath Forms Server when the call to open the form is sent to a Java 2 Platform, Enterprise Edition (J2EE) Web service. When this occurs, the InfoPath Forms Server uses UTF-8 character encoding to try to read the form. If the form does not use UTF-8 encoding, the parsing error occurs.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix package.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

32-bit hotfix package

The global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download informationMicrosoft Windows Installer .msp file informationAfter the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

64-bit hotfix package

The global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download informationMicrosoft Windows Installer .msp file informationAfter the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:Additional notes

• For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
• For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
  824684 Description of the standard terminology that is used to describe Microsoft software updates