Microsoft Knowledge Base Email Alertz

(201524) - If Microsoft Index Server is installed on your Web server, the FrontPage Search component uses the document index and search capabilities of Microsoft Index Server. In some cases, however, you may want to use the FreeWAIS search engine that is...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 201524 - Last Review: February 21, 2007 - Revision: 3.1

How to configure your FrontPage server to use WAIS search engine instead of Index Server

This article was previously published under Q201524

For a Microsoft FrontPage 98 version of this article, see 194484  (http://kbalertz.com/Feedback.aspx?kbNumber=194484/EN-US/ ) .
For a Microsoft FrontPage 97 version of this article, see 181204  (http://kbalertz.com/Feedback.aspx?kbNumber=181204/EN-US/ ) .

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://kbalertz.com/Feedback.aspx?kbNumber=256986/EN-US/ ) Description of the Microsoft Windows Registry

SUMMARY

If Microsoft Index Server is installed on your Web server, the FrontPage Search component uses the document index and search capabilities of Microsoft Index Server. In some cases, however, you may want to use the FreeWAIS search engine that is included in FrontPage instead of the Microsoft Index Server search engine.

This article describes how you can configure your FrontPage 2002 or FrontPage 2000 Extended virtual server on Microsoft Internet Information Services (IIS) to use the FrontPage Wide Area Information Service (WAIS) search engine instead of Index Server.

MORE INFORMATION

When you use the FrontPage 2002 or FrontPage 2000 search engine on IIS version 3.0 or later, you can use Indexing Services, which is a search engine that is built into IIS or Microsoft Windows. Or, you can use WAIS, which is a search engine that is built into FrontPage.

To use the WAIS Search with the FrontPage 2002 Server Extensions or FrontPage 2000 Server Extensions, you must configure this option in the Windows registry on your server. You can configure this setting to apply to all of your virtual servers, or you can configure the setting to apply to your individual virtual servers.

This article is divided into the following topics: WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Make WAIS Available for All Web Sites

To make the WAIS Search available to all of the virtual servers on your IIS Web server, follow these steps:
  1. At the server, click Start, point to Run, and then type regedit.
  2. Locate the following key in the registry:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\All Ports
  3. Right-click All Ports, click New, and then click String Value.
  4. For the name of the string, type noindexserver.
  5. Double-click the string.
  6. For the value of the string, type 1.
  7. Quit the Registry Editor.

Make WAIS Available for a Specific Web Site

To make the WAIS Search available for a single virtual server on your IIS Web server, follow these steps:
  1. At the server, click Start, point to Run, and then type regedit.
  2. Locate the following key in the registry
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Ports\Port /LM/W3SVC/1:
    where Port /LM/W3SVC/1: is the first virtual server, typically the default Web site.
  3. Right-click Port /LM/W3SVC/1:, click New, and then click String Value.
  4. For the name of the string, type noindexserver.
  5. Double-click the string.
  6. For the value of the string, type 1.
  7. Quit the Registry Editor.

Build the WAIS Text Indexes

After you modify the registry, you must run Recalculate Hyperlinks for each virtual server to allow the WAIS text indexes to be built. To do so, follow these steps.
  • To build the WAIS indexes from the server:
    1. Right-click a virtual server.
    2. Click All Tasks.
    3. Click Recalculate Web.
  • To build the WAIS indexes from a client:
    1. Open a Web in FrontPage.
    2. Click the Tools menu, and then click Recalculate Hyperlinks.
    3. Click Yes when you are prompted to continue.
Repeat these steps as you have to for other affected virtual servers.

REFERENCES

For additional information about configuration options for FrontPage Server Extensions, click the following article numbers to view the articles in the Microsoft Knowledge Base:
310931  (http://kbalertz.com/Feedback.aspx?kbNumber=310931/ ) Where to find the FrontPage 2000 Server Extensions Resource Kit (SERK)
310932  (http://kbalertz.com/Feedback.aspx?kbNumber=310932/ ) Where to find the SharePoint Team Services Administrator's Guide
For additional information about enumerating the names of IIS Web sites, click the following article number to view the article in the Microsoft Knowledge Base:
197891  (http://kbalertz.com/Feedback.aspx?kbNumber=197891/ ) Enumerating the names of IIS Web sites using WSH

APPLIES TO
  • Microsoft FrontPage 2002 Server Extensions
  • Microsoft FrontPage 2000 Server Extensions
Keywords: 
kbwebservices kbwebserver kbconfig kbinfo KB201524
       

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