Site Recovered to Different Server, Search Finds No Results

[Will Niccolls]

After a crash of our intranet server, I recovered all site files onto a
directory on another server, pointed the default IIS 6 website home
directory to it, and all is functioning correctly, except the site search.
I installed and enabled the Front Page extensions, Indexing Service, and
allowed them. ASP and ASP.net are installed and allowed. WebDav, IDS, and
IDC are installed but prohibited. I recaculated hyperlinks.

Using FP 2000.

The search appears to work, but always returns 0 results. Apparently the
index/catalogue doesn't contain any data?

Any advice?

Thanks, Will Niccolls

 

[David Berry]

If you were using Index Server on the other site then on the new server you
need to go to Computer Management, Index Server and create a Catalog for the
site. Then open the site in FrontPage and re-calculate hyperlinks.

 

[Will Niccolls]

Thanks for the advice David. It was helpful in that I now now where to
configure indexing. Unfortunately it appears to be more complicated than
that.

In fact, there is already a catalogue whose tracking is associated with the
correct web. I restarted the Index server and recalcualted hyperlinks
again.

When I run the query tool in the Index management console I get the expected
results. And I can see that the catalog is finding files and building word
lists and indexes. But when running the search from the web it returns zero
results.

In IIS, the Home Directory page has "Index this resource" enabled.

As far as I can tell, the Search Form properties in the page are set at the
defaults when viewed in FP2000.

Any other ideas?

Thanks, Will

 

[David Berry]

See if this helps http://support.microsoft.com/kb/203796/

 

[Will Niccolls]

Yes, I've followed that document. I deleted and recreated the catalog, and
the Indexing Service query tool works to find the expected results, the same
search on the website still finds no nothing.

There seems to be some disconnect between the search form on the web site
and the catalog.

In this link: http://support.microsoft.com/kb/214835/

I learned a bit about the _vti_scripts directory and a configuration file
that sets a cicatalog location, but on my IIS 6.0 install this directory is
empty. Could that be the problem?

Any other ideas?

 

[Ronx]

That will be the problem - probably.

The location should point at the folder containing the catalogue, which
is a folder named catalogue.wci

The pagename.idq file in _vti_scripts can be edited in notepad, if you
have access to the server.

Example:

cicatalog=D:\WebSites\cats\rxs-test

--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/
http://www.rxs-enterprises.org/fp

 

[Will Niccolls]

Thanks Ron. The _vti_scripts directory is empty, and none of our backups
include a the pagename.idq.html file either. I tried adding the file and
configuring the cicatalog parameter and restarted indexing, IIS, and recalc
hyperlinks afterwards, still no result.