You cannot use the Save Results component on a Web server that maps to a script handler with FrontPage 2003

Support for Office 2003 has ended

Microsoft ended support for Office 2003 on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When you submit a form that is configured to use the Save Results component in Microsoft Office FrontPage 2003, you may experience the following symptoms:
  • The form fields are cleared.
  • The form fields are returned to their default settings.
However, the form is not saved when you submit it, and you do not receive a confirmation page.
CAUSE
This behavior occurs if the following conditions are true:
  • The form that you submitted is located on a Microsoft Internet Information Services (IIS) Web server with Microsoft FrontPage Server Extensions.
  • The form that you submitted has a file name extension that maps to a script handler on the IIS Web server.
RESOLUTION
To resolve this behavior, save the form as a Web page that uses a file name extension that is not mapped to a script handler on the IIS Web server, such as an .htm file.
MORE INFORMATION
By default, several dynamic content technology file types are mapped to script handlers in IIS. For example, the following file name extensions are mapped to script handlers in IIS:
  • An .asp file
  • An .aspx file
  • An .stm file
  • An .shtm file
  • An .shtml file
  • An .idq file
  • An .idc file
  • An .htr file
The previously mentioned file name extensions cannot be used for Web pages that save form results to files or that send form results to e-mail messages because Web pages that contain forms that save results to files or that send form results to e-mail messages are processed through the FrontPage SmartHTML Interpreter (the Shtml.dll file).

The FrontPage SmartHTML Interpreter (the Shtml.dll file) checks to see if the Web page that contains the form is mapped to a script handler. If the FrontPage SmartHTML Interpreter did not do this check, the source code for the script-mapped page may have been displayed in the Web browser.
REFERENCES
For additional information about similar issues with FrontPage, click the following article numbers to view the articles in the Microsoft Knowledge Base:
292629 Cannot use search component with active server pages
828901 Cannot use the search component with active server pages in FrontPage 2003
310700 Error message: Cannot run the FrontPage Server Extensions' Smart HTML Interpreter on this non-HTML page
320872 Web clients receive "Cannot run the FrontPage Server Extensions on this page" error message when they submit a feedback form

Properties

Article ID: 873011 - Last Review: 12/28/2014 22:36:19 - Revision: 1.3

  • Microsoft Office FrontPage 2003
  • kbnosurvey kbarchive kbtshoot kbprb KB873011
Feedback