Article ID: 873011 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
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:
This behavior occurs if the following conditions are true:
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.
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:
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.
For additional information about similar issues with FrontPage, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/292629/ )Cannot use search component with active server pages
(http://support.microsoft.com/kb/828901/ )Cannot use the search component with active server pages in FrontPage 2003
(http://support.microsoft.com/kb/310700/ )Error message: Cannot run the FrontPage Server Extensions' Smart HTML Interpreter on this non-HTML page
(http://support.microsoft.com/kb/320872/ )Web clients receive "Cannot run the FrontPage Server Extensions on this page" error message when they submit a feedback form