Article ID: 828901 - Last Review: January 6, 2006 - Revision: 1.3 Cannot use the search component with active server pages in FrontPage 2003 For a Microsoft FrontPage 2002 version of this
article, see
292629
(http://support.microsoft.com/kb/292629/
)
. For a Microsoft FrontPage 2000 version of this
article, see
205540
(http://support.microsoft.com/kb/205540/
)
. For a Microsoft FrontPage 98 version of this article,
see
194284
(http://support.microsoft.com/kb/194284/
)
. For a Microsoft FrontPage 97 version of this article,
see
183046
(http://support.microsoft.com/kb/183046/
)
. On This PageSUMMARYYou cannot use the Microsoft Office FrontPage 2003 Search Form component on an Active Server Web Page. If you want to include a search component on an Active Server Page Web page, you can use the Microsoft Indexing Service
on your Microsoft Internet Information Services (IIS) Web Server. First, install the Microsoft Indexing Service on the Web
server that hosts your Web page. Next, configure FrontPage 2003 to use the Indexing Service to search the Web
site. Alternatively, you can use .htm or .html instead of .asp pages with the search form. Use one of these two methods to use search on an Active Server Page. SYMPTOMSIf you create an Active Server Page (ASP) in Microsoft
Office FrontPage 2003 that includes a search component, when you view your
Active Server Page Web page in your Web browser, and then click
Search, the results of your search are returned, but the ASP
script on your page does not run. You may receive an error message that is
similar to the following: Cannot run the FrontPage Server
Extensions' Smart HTML interpreter on this non-HTML page:
"http://Your_Server_Name/Your_File.asp"
http://Your_Server_Name/Your_File.asp/_vti_bin/shtml.dll/Your_File.asp CAUSEThis behavior occurs because you cannot use the FrontPage
2003 Search Form component on an Active Server Page. When an Active Server Page is requested on a server, Asp.dll parses the Active Server Page. ASP.dll finds any script that is specified to run on the server, runs the script, and then the results appear in your Web browser. When you conduct a search by using the Search Form, Shtml.dll parses the search page, the results of the search are expanded in the search file, and then the results appear in your Web browser. When a search is performed by using the Search Form on an Active Server Page, Shtml.dll cannot parse the file because Asp.dll is already parsing the file. Because Shtml.dll cannot parse the search page, it outputs the error message that is mentioned in the "Symptoms" section. RESOLUTIONTo resolve this behavior, use one of the following methods. Method 1: Use the Microsoft Indexing Service on your IIS Web ServerWhen you use the Microsoft Indexing Service, the Search Form does not use Shtml.dll. Instead, the action for the form points to the .idq file associated with the file. To install the Microsoft Indexing Service on the Web server that hosts your Web, follow these steps:
If you create catalogs for many virtual servers, store the catalogs outside the FrontPage 2003 content area and put each catalog in its own unique folder. To configure FrontPage to use the Indexing Service to search a Web site, follow these steps:
Method 2: Use .htm or .html instead of .asp pages with the search formDo not use Active Server Pages with the Search Form. Use HTML pages only.
| Article Translations
|
Back to the top
