FP2000: Cannot Use Search Component With Active Server PagesID: Q205540
|
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:
The Uniform Resource Locator (URL) in the Address box in Internet Explorer resembles the followingCannot run the FrontPage Server Extensions' Smart HTML interpreter on this non-HTML page: "http://<myserver>/<myfile>.asp"
http://<myserver>/<myfile>.asp/_vti_bin/shtml.dll/<myfile>.asp.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 ASP 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 ASP 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.
http://www.microsoft.com/ntserver/nts/downloads/recommended/NT4OptPk/default.aspFor additional information about using Index Server with FrontPage, please see the following article(s) in the Microsoft Knowledge Base:
Q194391 How to Integrate FrontPage 98 and Index Server
Additional query words: run time search index 2000RTMPublic
Keywords : fpactive fpiis fpext kbInternet
Version : WINDOWS:
Platform : WINDOWS
Issue type : kbprb
Last Reviewed: July 1, 1999