[To view most effectively in Notepad, turn on Word Wrap (Edit menu).]
Microsoft Office 97 Web Find Fast (TM)
Release Notes
Copyright 1996 Microsoft Corporation.

Welcome to the Microsoft Office 97 Web Find Fast Release Notes.  This document contains important documentation concerning this Web Find Fast release, and should be reviewed thoroughly.  Where there is a conflict between 
other Web Find Fast documentation and this file, please refer to this file.
_______________________________________________
CONTENTS
-Introduction
-System Requirements
-Documentation
-Installation
-Frequently Asked Questions
-Troubleshooting
_______________________________________________

[INTRODUCTION] 
Web Find Fast allows you to index Office documents (including HTML documents) on HTTP servers or shared folders throughout your intranet. Web Find Fast can also be used on an Internet server. Once an index is created, end 
users can then perform full-text searches of the index for words or phrases, or for specific document properties 
such as Author or Title. 
Users can view query and results pages in a Web browser, such as Microsoft Internet Explorer version 3.0. Clicking the name of a found document on the results page opens the document in the appropriate application. If your Web browser supports Active Documents, such as Microsoft Internet Explorer 3.0, the Office application opens within your Web browser.
Web Find Fast uses indexes created by the Find Fast NT service running on Windows NT Server or Windows NT Workstation. The Windows NT server or workstation must be configured as an HTTP server using Web server software, such as Microsoft Internet Information Server (IIS).  If you are using Windows NT Workstation, please make sure you do not violate the
connection license agreement with your HTTP server.

 
[SYSTEM REQUIREMENTS]
To run Web Find Fast, you need the following:
* Windows NT Server or Workstation version 3.51 and Service Pack 5 (or later)  or  Windows NT Server or Workstation version 4.0 (or later).
* An installed Web server such as the Microsoft Internet Information Server (IIS). IIS is available on the Windows NT Resource Kit CD-ROM or for free download at http://www.microsoft.com/Infoserv/IISInfo.htm. 
* On the client side, you need a Web browser such as the Microsoft Internet Explorer 3.0, or Word as your browser.
Note:  The release version of the Internet Explorer 3.0 is available on your Office 97 CD and can also be downloaded 
from http://www.microsoft.com/ie/.  

To run the Web Find Fast remote administration tool, you need the following:
* Windows NT Server 4.0 (or later)
* An NTFS partition on which to install the remote administration tool
* Microsoft Internet Information Server 2.0


[DOCUMENTATION]
There are several sources of information to help you with the setup and configuration of Web Find Fast:

For Web Find Fast:
* Readme.txt:  This file.
* Webadhlp.htm:  This file can be found in the <installation path>\Office\Webadmin\ directory and contains the main 
documentation for this feature, including Setup and configuration instructions.  It describes Web Find Fast administration
in detail, and also contains a list of frequently asked questions (FAQs).
* Admnwiz1-4.htm:  These files can be found in the <installation path>\Office\Webadmin\ directory and contain a short 
tutorial for creating a Web Find Fast index using either the Find Fast UI or the remote administration
tool.
* Srchwiz1-4.htm:  These files can be found in the <installation path>\Office\WebFFast\ directory and contain a short 
tutorial for creating a Web Find Fast index using the Find Fast UI.

For Windows NT Server or Workstation 3.51 and 4.0:
* Consult the documentation that comes with Windows NT and the Windows NT Resource Kit for operating system configuration
instructions.

For Microsoft Internet Information Server (IIS):
* Consult the administration documentation that comes with IIS for configuration instructions.


[INSTALLATION]
Web Find Fast Setup can be accomplished in a few easy steps.
First, install the Microsoft Office Server Pack:
1. Log into a Windows NT account with administrator privileges so that Setup can properly create a Windows NT service for Find Fast.
2. Insert your Office 97 CD and open the Srvpack folder.
3. Double-click Setup.
4. Click to install Web Find Fast.
5. Read the descriptions for both the Web Searching and Web Administration options.
6. Click the Change Folder button to select a separate folder for each of these options. Be sure each folder has read and execute permissions on your Web server. Also use NTFS security to control who has access to the files in the Web Administration folder.  This can be done after installation; however, if you are using the remote administration tool, make sure that you install on an NTFS partition.
7. When prompted, provide an account for the Windows NT service that is created for Find Fast.  Provide a user account that gives Find Fast the permissions it needs to create index files on the local machine, read all files that are covered by the index, and connect to UNCs to index remote documents. 


*IMPORTANT:  Web Administration files can be used remotely from any Web browser to create, modify, and delete indexes.  So, it is very important that you control who has access to these files.  Use NTFS directory security to specify a list of users who can administer Web Find Fast remotely.  Also, make sure that IIS is set to make use of Windows NT security by making sure that the "Windows NT Challenge/Response" checkbox is set in the Service panel of the IIS Service manager.  If you are using Netscape, or don't require the additional security of your password being encrypted, you only need to set the "Basic (Clear Text)" checkbox.	
	For the \WebAdmin directory, you must remove all accounts, including the "Everyone" account, from the folder permissions list, and then add <machine_name>\Administrators with "Change" or "Full" permissions set.  No one else should have access to the folder, then, except for administrators of the machine.

*Attention CGI users:  Web Find Fast uses the ISAPI technology to integrate with Web servers that provide this interface, such as Microsoft Internet Information Server.  Web Find Fast will also work as a CGI application, but some modification is required.  In query.htm and queryadv.htm you must change the following HTML source from:

<!-- Set the virtual path where the Web Find Fast dll will be -->
<FORM METHOD = "GET" ACTION = "webserch.dll">

to

<!-- Set the virtual path where the Web Find Fast dll will be -->
<FORM METHOD = "GET" ACTION = "webserch.EXE">

since webserch.exe is the CGI version of Web Find Fast.  Some Web servers have a dedicated CGI directory where all your CGI scripts must be placed.  If that is the case, you must copy webserch.exe, webserch.dll, and webintl.dll to the CGI directory for everything to work correctly.
 
*Caution:  The Office Server Pack installs a special Windows NT service version of Find Fast.  If you install Office 97 after installing the Office Server Pack,  you must be careful to avoid replacing this Find Fast NT service with the less powerful single-user Find Fast.  When you run the Office Setup program, choose the Custom installation; under the Office Tools option, clear the Find Fast check box.
At the end of Setup, you are asked to restart your computer to complete the installation. After your computer restarts, see the "Documentation" section earlier in this document to complete your Setup.

[FREQUENTLY ASKED QUESTIONS]
Q: I just added a folder to my index, but when I try to search for documents that I know are in that collection, I can't find them.  What's going on?
A: By default, Find Fast updates its index every 2 hours.  To update an index immediately, use the Find Fast UI in the Windows Control Panel.  For information about updating indexes, see Find Fast online Help.

Q: I currently have an index residing in a folder, and I want to make a new index in a subfolder.  Can I do this?
A:  No, Find Fast does not allow indexes to overlap.  If you have already created an index, remember
that it indexes everything within that folder, and includes any subdirectories below it.  You should never create an
index in any of the subdirectories.  Similarly, you shouldn't create a new index that is a "superfolder" of this
index.  Otherwise, the index you have created will be located in the path of the index in the superfolder, and will not work
properly.

Q:  If I use the remote administration tool, can I continue to use the Find Fast UI in the Windows Control Panel?
A:  No, you should use either the remote administration tool or the Find Fast UI, but never both at the same time.
If the Find Fast UI is currently running, the remote administration tool does not run.

Q:  I want to use the remote administration tool, but I don't want to use an NTFS partition.  Is there any way around
this?
A:  Yes, but it's recommended only if you are in a highly trusted networking environment.  When IIS is first installed,
the anonymous logon account is given as IUSR_<machine name>.  This account is also given guest permissions on the 
machine itself.  If you go into the User Manager, you can give the IUSR account administrative permissions, and then
the administration tool will work.  Once you are done using the administration tool, you can switch your anonymous logon
account back to a guest account.  See the IIS documentation for further information.

Q:  I tried to use the remote administration tool, but it reports that the "process is already running."  What
is going on here?
A:  Depending on the size of your document collection, it can take some time for the tools to complete running.  However, there are two additional possibilities for this message.  First, if the server was rebooted while one of the tools was running, it probably didn't unload properly.  Second, if the security permissions weren't 
configured properly, the tool may have failed.  You can check to see whether the tool is running properly by looking at
the Task Manager on the server.  The executable names you should see are rindex.exe, rsummary.exe, and rwebpage.exe.  If they are present, but don't appear to be taking up CPU time, they need to be unloaded.  The correct way to
do this is to end the process from the Task Manager, and then to delete the following registry key and all its subkeys: HKLM:Software:Microsoft:Shared Tools:Find Fast:WebSearch:ProcessKeys.

Q:  When I choose to "View my current indexes" through the remote administration tool, I just get back a random series of characters?
A:  When you use the remote administration tool, make sure that you use the HTTP protocol, as opposed to the FILE protocol.  For example, make sure your URL looks like "http://myserver/display.dll?" and not "file:\\myserver\display.dll?".

Q:  When I generate Web pages using the Web Find Fast PageView feature, I see that an input box is available at the top of the page which allows me to do a direct search against the index.  The problem is that when I do a search, the URL looks for http://webserch.dll?.  How do I make the URL point at the correct server (i.e. http://MyServer/webserch.dll?)?
A:  Before you generate your Web pages, it is important that you open up the HTML source to webpage.htm and adjust some hidden values to make sure that the generated Web pages all point to correct place.  Specifically, you need to go to the following section in webpage.htm:

<!-- Insert your virtual path to the webserch.dll here -->
<INPUT TYPE="hidden" name="WebDirectoryV" value="http://webserch.dll">

<!-- Specify, using the "Friendly Name", which index this page should search against -->
<INPUT TYPE = "hidden" NAME = "Index" VALUE = "">

Q:  I see only garbage when I use my browser to view Office documents from my HTTP server, why is this?
A:  Certain HTTP servers, like Netscape and IBM, do not use the windows registry to store MIME types.  They store the
MIME types in files which you must edit after you install new software.  On Netscape, for example, you must edit the
"mime.types" files in your \Config subdirectory in order to display Office files correctly by adding:

type=application/vnd.ms-powerpoint  	exts=ppt
type=application/x-msexcel   		exts=xls
type=application/msword   		exts=doc

Please consult you HTTP server's documentation for further information on this issue.


[TROUBLESHOOTING]
Problem #1
I can't access the query page (Query.htm) from a Web browser.  
Query.htm and other search pages should be in the folder that you selected during Setup for the Web Searching option.  (Run Setup again to change to a different folder). Make sure that this folder is accessible to users from your Web server with both read and execute privileges.  For example, using the Microsoft IIS, do the following:
1. Double-click the Internet Services Manager.
2. Double-click the Internet service for your Web server to display the Properties dialog box.
3. Click the Directories tab and select the directory where you copied the Web Find Fast files and created an index.
4. Click Edit Properties.
5. Select the Execute and Read check boxes at the bottom of the dialog box, and then click OK.
6. Select the Enable Default Document check box and enter a path to the file Query.htm if you want this to be the default page for your Web site.
Note:  Make sure that your Windows NT server is accessible to your users from the network.  On the Start menu (Windows 95 or Windows NT Workstation 4.0) or in Program Manager (Windows NT Workstation 3.51), click Administrative Tools/User Manager.  On the Policies menu, click User Rights.  Check to be sure that Everyone can Access this computer from the network.
Note: You can run Setup again to change the folder location for the Web Searching or Web Administration option.  Run Setup first to remove Web Find Fast and then a second time to reinstall Web Find Fast with the new folder location.

Problem #2.
I can't access the administration pages (for example, WebSrchW.htm) from a Web browser.
Administration Web pages should all be in the folder you specified during Setup for the Web Administration option.  Follow steps described previously. Also, make sure the following are true:
* You have read/execute access to the Web Administration folder.
* You have administrator privileges on this machine.
* The Web server is set to support Windows NT Challenge/Response.  If you are using a Web browser that doesn't support Windows NT Challenge/Response, then you also need to enable Basic (Clear Text) password authentication.
If you are still not able to use administration pages to create an index, you should use the Find Fast UI from the Windows Control Panel instead. 

Problem #3.
Web Find Fast can't find an index.
When you submit your search, a page with the following error message may be returned:
"Error in query or search:  Web Find Fast cannot find an index for your search..."
This can occur for one of two reasons:  
* The Query.htm page may not be referring to the right index.  Please refer to the webadhlp.htm file on editing the query.htm page. 
* Find Fast may have failed to create an index. If you have waited a sufficient amount of time (at least one hour per 100 MB of documents) and still can't execute a search, try the following:
1. In the Windows NT Control Panel, double-click the Find Fast icon.  
2. On the Index menu, click Show Indexer Log (or open the file Ffastlog.txt located in the System folder in the Windows folder).
3. Scroll to the end of the log to see if the index create has failed.  If you see no message such as "Index create failed," wait for index creation to complete.
4. If you may see messages telling you that some files are corrupt and that Find Fast is unable to index them, move these files to another folder outside the scope of the index.
5. The document collection you are trying to index may be too large for a single Find Fast index.  If your collection of documents is over 15 GB and you are unable to create an index, consider dividing your collection into smaller collections (in separate folders) and indexing each folder separately.

Problem #4
Web Searching doesn't return matching documents from network folders.
The Find Fast service may not have the necessary read permission to access network folders that you've included in the scope of your index.  You can check by looking at the indexer log -- open Find Fast from the Windows Control Panel and then click Show Indexer Log on the Index menu. Scroll to the end of the log. You may notice messages that Find Fast is unable to access a folder. If so, you can change the account that the Find Fast service runs under either by rerunning Setup or by doing the following:
1. In the Windows NT Control Panel, double-click the Services icon. 
2. Select the Microsoft Find Fast NT service.
3. If the service is not running click Start.
   -or-
   If the service is paused, click Continue.
4. Click Startup to open the Startup Options dialog box. 
5. Select the Automatic check box.
6. Click This Account and enter a valid user ID and password that grants read access to any network folders that you may choose to index (often this is your own ID and password).  

Problem #5
Web Searching works for a while and then fails.
Check the Find Fast indexer log.  If the index is no longer usable, double-click the Find Fast icon in the Windows Control Panel, delete the index, and then create the index again.

Problem #6
Web Searching does not return new files and returns old files that are no longer there.
If Web Find Fast doesn't return files that are new or returns old files that are no longer in the collection, this could mean that the index is no longer being updated. To check, do the following:
1. In the Windows NT Control Panel, double-click the Find Fast icon.  
2. Make sure the Find Fast status window lists a task for this index and that this task says either "Update paused" or "Update automatically."
3. If the task does not say either "Update paused" or "Update automatically," then click Update Index on the Index menu, select the index, and select the Update automatically check box.


Other Issues
* If you are running Internet Explorer 1.5, you may receive an error message if you try open an HTML file directly from File Manager or from an MS-DOS prompt, or if you use the File protocol.  For information about how to correct this problem, see the following Knowledge Base article:  http://www.microsoft.com/kb/bussys/iis/q145774.htm.
* If the total file set to be indexed is greater than approximately 15 GB, index creation may fail.
* If you change the logon account for the Find Fast service in the Services dialog of the Control Panel in any way, you must stop and restart the service for the new changes to take effect.
* If you are using the IBM web server, install Web Find Fast to a directory path that doesn't have spaces in it since IBM's web server doesn't map HTTP addresses to directories with spaces in the folder name.
