This article was previously published under Q292629
This article has been archived. It is offered "as is" and will no longer be updated.
For a Microsoft FrontPage 2000 version of this article, see 205540. For a Microsoft FrontPage 98 version of this article, see 194284. For a Microsoft FrontPage 97 version of this article, see 183046.
When you click Search on an Active Server Page (ASP), the results of your search are returned, but the ASP script on your page does not execute. In some cases, the following error message appears in your Web browser:
Cannot run the FrontPage Server Extensions' Smart HTML interpreter on this non-HTML page: "http://<myserver>/<myfile>.asp"
The Uniform Resource Locator (URL) in the Address box in Internet Explorer resembles the following
where <myserver> is the location of your Web and <myfile> is the name of the file you are previewing.
You can not use the Search Form on an Active Server Page.
When an Active Server Page is requested on a server, Asp.dll parses it. It finds any script specified to run on the server, executes it, and displays the results.
When you conduct a search using the Search Form, Shtml.dll parses the search page and the results of the search are expanded into the search file and displayed in your Web browser.
When a search is performed using the Search Form on an Active Server Page, Shtml.dll cannot parse the file because Asp.dll is already parsing it. Because Shtml.dll fails, it outputs the message described in the "Symptoms" section.
When using Microsoft Index Server, the Search Form does not use Shtml.dll. Instead, the action for the form points to the .idq file associated with the file.
To resolve this behavior, use one of the following methods.
Method 1: Install Microsoft Index Server
Install Microsoft Index Server on the Web server hosting your Web.
For more information about obtaining and installing Microsoft Index Server, please see the following Microsoft World Wide Web site: