Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 214835 - Last Review: February 21, 2007 - Revision: 1.2
Search returns results from wrong Web
This article was previously published under Q214835
After 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.
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.
For example:
c:\inetpub\virtualserver
Look 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.
To 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:
- Click Start, point to Programs, point to Windows
NT 4.0 Option Pack, point to Microsoft Index Server, click
Index Server Manager.
- Click the + next to Index Server on Local Machine.
- Click the Default Catalog, Web, right-click, and click
Properties.
- Click the Web tab.
- Click the dropdown box for Virtual Server and click a different
catalog. Before clicking OK, select the dropdown box for virtual server
and reselect Default Web Site. Essentially, you are just reapplying
the default catalog to the Default Web Site. This process will cause
registry keys to be written so that FrontPage will be able to detect
additional catalogs.
- With Default Web Site selected, click Ok and exit the
Index Server Manager.
- In FrontPage, open the web for this virtual server and on the
Toolsmenu click Recalculate Hyperlinks.
- In the browser, search for a word that would be found in this
virtual server. If your problem is specific to this problem, your search
should return the correct results from the correct web.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
203796Â
(http://kbalertz.com/Feedback.aspx?kbNumber=203796/
)
How to configure FrontPage to search a site by using Index Server
Microsoft has confirmed that this is a problem in the FrontPage 2000 Server Extensions.
APPLIES TO
- Microsoft FrontPage 2000 Server Extensions
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate