• Operational Registry Parameters
• Virtual Servers and Catalogs Registry Parameters
• Language-Specific Registry Parameters

- A -
Index Server Registry Parameters

Microsoft Index Server is controlled by many registry parameters, which can be edited through the use of the regedit program. These registry parameters fall into three different categories: operational parameters, virtual server and catalog parameters, and language-specific parameters.

---

Because invalid registry parameters can cause serious problems with your Windows NT and Index Server installation, much attention should be placed on correctly editing only those registry parameters for which the user interface does not have an appropriate update capability.

---

Operational Registry Parameters

The operational registry parameters affect the operation of Microsoft Index Server. Using the regedit program, you can find and edit these parameters under the following path:

HKEY_LOCAL_MACHINE

\SYSTEM

 \CurrentControlSet

  \Control

   \contentindex

Figure A.1 displays the regedit program that shows the operational registry parameters.

Figure A.1. Index Server operational registry parameters.

Listed are the valid Index Server operational registry parameters and a description of each.

• DaemonResponseTimeout—Specifies a timeout period after which the CiDaemon process should have responded with an appropriate response. One such reason for the CiDaemon to timeout would be because of a looping condition due to a corrupted file.
  
  
• EventLogFlags—Controls the generation of certain event log messages. []
  
  
• FilterContents—Identifies whether the contents of a file will be filtered or whether only the properties of the file will be filtered. A value of 0 specifies that the contents will not be filtered. Otherwise, the contents and properties will be filtered.
  
  
• FilterDirectories—Identifies whether directories will be filtered for system properties and displayed in query results. When set to a non-zero value, directories will be filtered.
  
  
• FilterFilesWithUnknownExtensions—Identifies whether files with extensions that have not been registered will be filtered. When set to a value of zero, only registered file types will be filtered.
  
  
• FilterRetries—Identifies the maximum number of times a file will be retried for filtering if there are failures while trying to filter the file.
  
  
• ForcedNetPathScanInterval—Identifies the time interval between forced scans on directories with no notifications.
  
  
• GenerateCharacterization—Controls the automatic generation of file characterizations (abstracts).
  
  
• GrovelIISRegistry—Controls whether all virtual roots within the Internet Information Server are automatically indexed.
  
  
• IsapiDefaultCatalogDirectory—Identifies the default content index catalog directory.
  
  
• IsapiMaxEntriesInQueryCache—Identifies the maximum number of cached queries.
  
  
• IsapiMaxRecordsInResultSet—Identifies the maximum total number of rows to fetch for a single query.
  
  
• IsapiMaxRecordsPerGetRows—Identifies the maximum number of rows that will be returned in a single fetch (get) operation. A result set can be made up of multiple fetches.
  
  
• IsapiQueryCachePurgeInterval—Identifies the time interval under which a query cache item will remain active.
  
  
• IsapiRequestQueueSize—Identifies the maximum number of Web query requests to queue during periods of high server activity.
  
  
• IsapiRequestThresholdFactor—Identifies the number of threads per processor beyond which query requests are queued.
  
  
• IsapiVirtualServerCatalogs—Each key in this section associates a virtual server with a specific catalog. The key name is the IP address of the virtual server (NULL is used for the default server) and the value is the location of the catalog, as it would be entered in the CiCatalog parameter of an .idq file.
  
  
• Language—Identifies language-specific registry information.
  
  
• MasterMergeCheckpointInterval—Identifies the checkpointing interval for master merge. During master merges, this parameter determines how often data is written to the new master index. This is especially useful when a master merge is paused and restarted.
  
  
• MasterMergeTime—Identifies the time at which a master merge will occur. This value is stored as the number of minutes after midnight.
  
  
• MaxActiveQueryThreads—Identifies the maximum number of concurrently processed asynchronous query threads.
  
  
• MaxCharacterization—Identifies the maximum number of characters in the automatically generated characterization (abstract).
  
  
• MaxFilesizeFiltered—Identifies the maximum size of a single file to be filtered using the default filter. If the size of a file exceeds this value, only file properties will be filtered. This limit does not apply for registered file types (that is, those file types that do not use the default filter).
  
  
• MaxFilesizeMultiplier—Identifies the maximum amount of data that can be generated from a single file, based on its size. This value is a multiplier and is used in conjunction with the current file size to determine the maximum file size after content indexing. For example, a value of 2 means that a file can generate up to 2 times its size in content index data.
  
  
• MaxFreshCount—Identifies the maximum number of newly indexed files that will cause a master merge to be started.
  
  
• MaxIdealIndexes—Identifies the maximum number of indexes considered acceptable in an ideal system. If the number of indexes exceeds this value and the system is idle, an annealing merge will take place to bring the total count of indexes to this number.
  
  
• MaxIndexes—Identifies the maximum number of persistent indexes in the catalog. If this number is exceeded, a shadow merge will be performed to bring the total below this number.
  
  
• MaxMergeInterval—Identifies the sleep time between merges. Index Server activates this often to determine whether an annealing (most common), shadow, or master merge is necessary.
  
  
• MaxPendingDocuments—Identifies the maximum number of pending documents to be filtered before considering the content index out of date for property queries.
  
  
• MaxQueryExecutionTime—Identifies the maximum execution time of a query. If a query takes more than this amount of CPU time, its processing will be stopped and an error status indicated.
  
  
• MaxQueryTimeslice—Identifies the maximum amount of time to execute a query in a single CPU time slice. If more asynchronous queries are active than allowed query threads, a query is put back on the pending queue after this time interval. CPU time slicing is done only after a matching row is found, so the time spent in a time slice may overrun this and a considerable number of rows may be examined in the time slice.
  
  
• MaxQueueChunks—Identifies the maximum number of in-memory buffers (queue chunks) for keeping track of pending documents. The higher the number, the less frequently the memory buffers have to be written to disk.
  
  
• MaxRestrictionNodes—Identifies the minimum number of restriction nodes created by query normalization. If this value is exceeded, the query will fail with the status of QUERY_E_TOOCOMPLEX. This status message means the query was too complex to be completed because the limit imposed in this registry key has been reached. This key keeps a user from overloading the server's capacity with an overly large query.
  
  
• MaxShadowFreeForceMerge—Identifies when a master merge is forced to be executed because the free space on the catalog disk drive has fallen below the MinDiskFreeForceMerge value and the disk space occupied by the shadow indexes exceeds the value of MaxShadowFreeForceMerge.
  
  
• MaxShadowIndexSize—Identifies that a master merge should be started because the disk space occupied by the shadow indexes exceed this percentage of the catalog drive.
  
  
• MaxWordLists—Identifies the maximum number of concurrent word lists that can exist.
  
  
• MaxWordlistSize—Identifies the maximum amount of memory consumed by an individual word list. When this limit is reached, only the document being filtered will be added. Additional documents will be re-filed and later placed in another word list. Each unit is 128KB.
  
  
• MinDiskFreeForceMerge—Identifies when a master merge should be performed because the free space on the catalog drive has fallen below the value of MinDiskFreeForceMerge and the disk space occupied by the shadow indexes exceeds the value of MaxShadowFreeForceMerge.
  
  
• MinIdleQueryThreads—Identifies the minimum number of idle threads kept alive to process incoming queries.
  
  
• MinMergeIdleTime—Identifies when an annealing merge should be performed because the average system idle time for the last merge check period has been exceeded.
  
  
• MinSizeMergeWordlists—Identifies the minimum combined size of word lists that will force a shadow merge.
  
  
• MinWordlistMemory—Identifies the minimum free memory used for word-list creation.
  
  
• PropertyStoreMappedCache—Identifies the maximum size of memory buffers used for Property Cache.
  
  
• ThreadClassFilter—Identifies the priority class of the CiDaemon process. The value 20 is Normal Priority Class, 40 is Idle Priority Class, 80 is High Priority Class, and 100 is Real-time Priority Class.
  
  
• ThreadPriorityFilter—Identifies the NormalPriority of the filtering thread within the CiDaemon process.
  
  
• ThreadPriorityMerge—Identifies the priority of the merge thread.
  
  

Table A.1 contains each of the parameters listed previously and the range of valid data associated with each parameter.

Virtual Servers and Catalogs Registry Parameters

The virtual servers and catalogs registry parameters associate a virtual server with a specific catalog. The key name is the IP address of the virtual server. The key name NULL signifies the default server. Using the regedit program, you can find and edit these parameters under the following path:

HKEY_LOCAL_MACHINE

\SYSTEM

 \CurrentControlSet

  \Control

   \contentindex

    \IsapiVirtualServerCatalogs    

Figure A.2 displays the regedit program with the virtual servers and catalogs registry parameters displayed.

Figure A.2. Index Server virtual servers and catalogs registry parameters.

Currently, the only valid Index Server operational registry parameter is the <IP Address> parameter. A description of the <IP Address> parameter as well as additional information pertaining to this parameter is as follows.

<IP Address>—Each IP Address key represents an association of a virtual server with a specific catalog. The <IP Address> parameter is of type REG_SZ with a default pathname of root.

Language-Specific Registry Parameters

Language-specific registry parameters control the selection of word-breaker, stemmer, and noise-word lists for a given language. They also select the error pages returned in response to invalid user and administrator actions. Using the regedit program, you can find and edit these parameters under the following path:

HKEY_LOCAL_MACHINE

\SYSTEM 

 \CurrentControlSet 

  \Control 

   \contentindex

    \Language

     \language (i.e. English_US)

Figure A.3 displays the regedit program with the language-specific registry parameters displayed. The InstalledLangs value lists the set of languages installed. Each string in the InstalledLangs value names a subkey below the Language key.

Figure A.3. Index Server Language-Specific Registry Parameters

Figure A.4 displays the English_US language-specific registry parameters.

Figure A.4. Index Server English_US Language-Specific Registry Parameters

Within each specific installed language, the following registry entries are recognized:

• ISAPIDefaultErrorFile—Identifies the full virtual path to the generic error template file. This .htx template is processed when none of the specific error pages applies. CiRestriction, CiErrorMessage, and CiErrorNumber can all be referenced.
  
  
• ISAPIHTXErrorFile—Identifies the full virtual path to the error page returned in response to errors in the .htx file. CiRestriction, CiErrorMessage, and CiErrorNumber can all be referenced.
  
  
• ISAPIIDQErrorFile—Identifies the full virtual path to the error page returned in response to errors in the .idq file. CiRestriction, CiErrorMessage, and CiErrorNumber can all be referenced.
  
  
• ISAPIRestrictionErrorFile—Identifies the full virtual path to the error page returned in response to errors in the query restriction (CiRestriction). This is the error page that will be seen most often by users. CiRestriction, CiErrorMessage, and CiErrorNumber can all be referenced.
  
  
• Locale—Associates the registry section with a specific locale.
  
  
• NoiseFile—Identifies the file name of the noise-word list for this locale. The file must be located in the %SystemRoot%\System32 directory.
  
  
• StemmerClass—Identifies the ActiveX class ID of the class used for locale-specific stemming.
  
  
• WBreakerClass—Identifies the ActiveX class ID of the class used to split phrases for this locale.