Very Computer

PROBLEM
=======
SharePoint Team Services SEARCHES yield "No records were found
matching your query", but I can query the Catalog from the Index
Server MMC with no problem.

OBJECTIVE
=========
I'd like STS searches to return the same results as my catalog
queries.

BACKGROUND
==========
I recently migrated this site from a test environment where it was
working beautifully to a pre-production environment where STS searches
are failing.

TEST ENVIRONMENT (SUCCESSFUL)
=============================
Win2K, SP2
IIS 5
SharePoint Team Services (Version 5.0.2.2623)
SQL Server 7

  /Microsoft SharePoint Search Proxy
   - IP: 10.1.1.29
   - TCP Port: 8624
   /OWS_VRoot_4
    - Local Path: D:\websites\MYSITE

PRODUCTION ENVIRONMENT (FAILING)
================================
Win2K, SP2
IIS 5
SharePoint Team Services (Version 5.0.2.2623)
SQL Server 2000

  /Microsoft SharePoint Search Proxy
   - IP: (All Unassigned)
   - TCP Port: 5907
   /OWS_VRoot_2
    - d:\websites\MYSITE

RESEARCH
========

I've conducted research using the following resources but have not
found topics that address this completely.

http://www.microsoft.com/technet/

http://groups.google.com/groups?hl=en&group=microsoft.public.sharepoi...

http://groups.google.com/groups?hl=en&group=microsoft.public.sharepoi...

http://groups.google.com/groups?hl=en&group=microsoft.public.office.i...

http://groups.google.com/groups?hl=en&group=microsoft.public.inetserv...

REQUEST
=======

I'd be grateful for any help, online or interactively, that anyone can
offer. I'll gladly post our results here for others' benefit.

Gratefully,

Hans Henningsen

I figured it out. Here's what I learned:

ROOT CAUSE:
==========
The CiScope variable in each sub web was pointing to the wrong virtual
server. This was left over from the migration from ServerA to ServerB.

SOLUTION:
========
I pointed the CiScope variable in each sub web to the correct virtual
server. I did this by opening up the "search.idq" file for each sub web in
Notepad and then updating the incorrect line to point to the correct virtual
server.

EXAMPLE:
=======

In this example I've recently migrated my virtual server, "MyWeb", and all
of its sub webs from ServerA to ServerB. Both servers have: Windows 2000
Server, IIS5, and SharePoint Team Services.

On ServerA the IIS Instance of MyWeb was "LM/W3SVC/2". Now on ServerB, the
new HostServer, MyWeb has to share space with lots of other virtual servers
and its new IIS Instance is "LM/W3SVC/4".

The IIS MMC (Microsoft Managment Console for Internet Information Services)
shows:

Internet Information Services
 /<HostServer>
  /Microsoft SharePoint Search Proxy
   /OWS_VRoot_1
   /OWS_VRoot_2
   /OWS_VRoot_3
   /OWS_VRoot_4

But the CiScope line in the search.idq file for MyWeb and each of its sub
webs reads:

CiScope=/OWS_VRoot_2/%DocLibDir%

The solution then is to change the CiScope line (using NotePad or another
text editor) to:

CiScope=/OWS_VRoot_4/%DocLibDir%

NOTE:
Each sub web's "search.idq" file is located off its own root directory in
the _vti_script folder. Examples:

   D:\websites\myweb\_vti_script\search.idq
   D:\websites\myweb\mySubWeb1\_vti_script\search.idq
   D:\websites\myweb\mySubWeb2\_vti_script\search.idq
   -- etc. --

Good luck!

Hans Henningsen

Hans,

A million thank-yous! This has been bugging me for months! I tried your
suggestion and it worked. For other people trying this, its worth pointing
out that they should ignore the search.idq in the _layouts folder: its just
the one in _vti_script that needs checking.

Thanks again, Hans!

Zapf