The information in this article applies to:
SYMPTOMSAfter you configure catalogs and apply them to the appropriate virtual server in the Index Server Manager, searches in the browser return results from a different Web site. Typically, this will occur on a new installation of IIS 4.0 and FrontPage 2000 with newly created catalogs. If you have other webs that the search works properly on, and these webs are using Index Server, then this article will likely not apply to your problem. CAUSE
The Cicatalog value in the idq file for the web is not being updated to
point to the correct catalog. You can verify this by going to the content
area of a virtual server experiencing this problem. c:\inetpub\virtualserverLook for a folder called _vti_script. You may have to modify your view settings in Windows Explorer to see this folder, (On the View menu, click Options, and then select the Show all files option). Using Notepad, open the Pagename.htm0.idq file. At this point, you should be able to note that the cicatalog value is cicatalog=C:\Inetpub. The cicatalog value should point to the location of the catalog you created for this virtual server. If the cicatalog refers to C:\Inetpub, then your search bot is using the catalog for the Default Web Site. Because of this, your search will return results from the Default Web Site and not the web the search is in. RESOLUTIONTo resolve this problem, update the IDQ file to point to the correct catalog. You can either edit the cicatalog value to point to the correct catalog, or perform the following steps:
For additional information, please see the following article(s) in the Microsoft Knowledge Base: Q203796 Configuring FrontPage 2000 to Search Using Index Server STATUSMicrosoft has confirmed this to be a problem in the FrontPage 2000 Server Extensions. Additional query words: front page
Keywords : fpse2000 |
Last Reviewed: April 14, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |