This article has been archived. It is offered "as is" and will no longer be updated.
When you try to submit a form that is configured to use the Save Results component in Microsoft Expression Web, you may experience the following symptoms:
The form fields are cleared.
The form fields are returned to their default settings.
The form is not saved when you submit it.
You do not receive a confirmation page.
This behavior occurs if the following conditions are true:
The form that you submitted is located on a Web server that is running Microsoft Internet Information Services (IIS). Additionally, the server uses 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.
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. For example, save the form as an .htm file.
By default, the following dynamic content technology file types are mapped to script handlers in IIS:
These file name extensions cannot be used for Web pages that save form results to files or that send form results to e-mail messages. This behavior occurs 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 (Shtml.dll).
The FrontPage SmartHTML Interpreter checks to determine whether the Web page that contains the form is mapped to a script handler. If the FrontPage SmartHTML Interpreter does not perform this check, the source code for the script-mapped page may be displayed in the browser.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
873011 You cannot use the Save Results component on a Web server that maps to a script handler with FrontPage 2003
310700 You receive a "Cannot run the FrontPage Server Extensions' Smart HTML interpreter on this non-HTML page" error message when you submit a form