Table of contents
This value identifies the minimum number of restriction nodes created by query normalization. If this value is exceeded, the query fails 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 was reached. This key keeps a user from overloading the server’s capacity with an overly large query.
When disk space occupied by the shadow indexes exceeds this value and the free space on the catalog disk drive falls below the MinDiskFreeForceMerge value, Index Server executes a master merge.
When the disk space occupied by the shadow indexes exceeds this percentage of the catalog drive, Index Server executes a master merge.
This value determines the maximum number of concurrent word lists that can exist.
This value, in 128K chunks, identifies the maximum amount of memory consumed by an individual word list. When this limit is reached, Index Server finishes the document it’s currently filtering and adds that document only. Any other documents are re-filed and placed in another word list later.
This value sets the minimum number of idle threads kept alive to process incoming queries.
This value identifies when Index Server should perform an annealing merge because the system was idle more than average during the previous merge check period.
This value identifies the minimum combined size of word lists that forces a shadow merge.
This value identifies the minimum free memory used to create word lists.
This value identifies the maximum size of memory buffers used for Property Cache.
This value identifies the priority of the merge thread.
This value is the minimum free disk space needed before the content indexer forces a merge. Acceptable values range from 5 percent to 25 percent.
The InstalledLangs value lists the set of languages installed. Each string in the InstalledLangs value names a subkey below the Language key.
This value gives the full virtual path to the generic error template file that’s displayed to the user. This .htx template is processed when none of the specific error pages applies. The CiRestriction, CiErrorMessage, and CiErrorNumber variables can all be referenced in the .htx file.
This value identifies the full virtual path to the error page returned in response to errors in the .htx file. The CiRestriction, CiErrorMessage, and CiErrorNumber variables can all be referenced in the .htx file.
This value identifies the full virtual path to the error page returned in response to errors in the .idq file. The CiRestriction, CiErrorMessage, and CiErrorNumber variables can all be referenced in the .htx file.
This value 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 users see most often. The CiRestriction, CiErrorMessage, and CiErrorNumber variables can all be referenced in the .htx file.
This value associates the registry section with a specific locale.
This value identifies the file name of the noise-word list for this locale. The file must be located in the %SystemRoot%\System32 directory.
This value identifies the ActiveX class ID of the class used for locale-specific stemming.
This value identifies the ActiveX class ID of the class used to split phrases for this locale. III-116 If Microsoft Index Server is currently indexing all your files, you can make it quit by limiting Index Server to indexing just those files you register.
A value of 0 tells the Content indexer to Index only those file types that have been registered and ignore the rest. This feature is handy when you don’t want to index .exe files and .com files, for example. SQL SERVER III-117 You can specify the protocol you want SQL Executive to use in its Advanced tab, but if you need to specify a particular protocol for SQL Executive to use when connecting to servers, you need to add the following registry entry.
You must still create a specific server connection in the Advanced tab of the SQL Client Configuration Utility. Then set the ServerHost value in the SQL Executive section of the registry to the appropriate server name. SQL should then use the defined protocol on all its connection attempts to subscribing servers. III-118 To increase the concurrent number of SQLExec tasks that use a DB-Library connection, change the following registry value.
The number of available concurrent tasks is the number of MaxDBProcesses — three for SQL overhead. Restart your SQL server for these changes to take effect. III-119 If the SQLMonitor Service on Windows NT won’t start and you recently changed the SQL Server SA accounts password, you should change it back. If you can’t remember the password, here’s how to fix the problem.
Type the new SA account password for the value.
Restart the machine for these changes to take effect. III-120 You’ve installed SQL Server 6.5, but SQL Executive does not come up. When you try to start it from the Control Panel, you get an Error 109. To fix the problem, change this registry value.
Restart the machine for these changes to take effect. EXCHANGE SERVER 4.0 III-121 If you have tried to change your Exchange password, chances are you have encountered this error: “The NT Domain password could not be changed. A required action was not successful due to an unspecified error.” You need to add the following registry parameters to fix this problem.
Add the following value under the LSA key:
Use this entry if you are running NWLINK.
Add the following value under the LSA key:
Use this entry if you are running TCP/IP. Restart the machine for these changes to take effect. III-123 If you cannot communicate with your Exchange Server using your Exchange client and have recently installed a firewall, you may need to change the following registry entries.
Some Internet firewall software doesn’t accept the TCP/IP ports Exchange uses to communicate via RPC. You need to modify these ports on the Exchange server to something that your firewall software can use. Restart Exchange for these changes to take effect. III-125 The Exchange client installs multiple protocols so that it can connect to the server using any one. As a result, sometimes it seems that Exchange takes forever to load. You can speed things up by eliminating the protocols you don’t use. For example, if you use only TCP/IP, you can change the following registry entry.
The default setting is 0x8 and is fine under normal conditions. If your installation has several gateways or connections configured, try increasing this parameter. INTERNET NEWS AND MAIL III-126 If you need to move the address book file, you need to modify these two registry values. This change is especially useful if you have just upgraded your hard drive and want to move some of the larger files to a disk with more room.
This value sets where Internet Explorer stores the address book files. Be sure to include the drive and fully qualified path.
This value is the actual location of the .wab files, in the format username.wab. If your login is tim, your wab file is tim.wab. PEER WEB SERVICES III-128 Have you ever tried to change the port numbers for the personal Web server or FTP server that comes with Front Page? Well, now you can. Each of the values below represents its corresponding services TCP/IP port number in hexadecimal. You can change them to any valid port number. Restart your machine for any changes to take effect.
This value is the TCP/IP port number for the FTP Service.
This value is the TCP/IP port number for the Web Service.
This value is the TCP/IP port number for the Gopher Service.
This value is the TCP/IP port number that the administration program for Peer Web services listens on. NETSCAPE NAVIGATOR 3.0 III-132 You recently joined a domain, and some of your settings were wiped out for Netscape Navigator. You invested a lot of time in setting up Netscape Navigator, and now you can access the correct version only if you boot locally. This registry location shows where Netscape stores its information.
Save the key and then log on to NT as the domain user. Restore the saved key and you’re back in business. III-133 Do you need to browse Japanese, Chinese, or Korean HTML files with your Netscape browser? Follow these steps.
GOPHER III-134 To change the Administrator name for your Gopher service, change this registry entry.
Add the following value under the Parameters key:
The default value is Administrator. Change this value to the name that’s appropriate for your site. Restart the service for these changes to take effect. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Page: 1, 2, 3, 4, 5 |
next page  |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||