This section lists common error messages and possible solutions. Some of the most common problems with the Indexing Service can be fixed quite easily. For more complex issues, search the Microsoft Knowledge Base on line at http://support.microsoft.com/search/ for solutions.
CiCatalog=d:\inetpub\wwwroot\tmjs_index |
Make sure that the path is pointing to the directory that contains the catalog's Catalog.wci directory. In an Active Server Pages (ASP) file, you will need to add the Q.Catalog line in the code segment below:
set Q = Server.CreateObject("ixsso.Query") set util = Server.CreateObject("ixsso.Util") Q.Catalog="<catalog_name>" Q.Query = CompSearch Q.SortBy = "rank[d]" Q.Columns = "DocTitle, vpath, filename, size, write, characterization, rank" Q.MaxRecords = 300 |
Replace <catalog_name> with the name of your catalog as it appears in the Indexing Service console. (Include the quotation marks.)
In an .IDQ:
CiScope=/ CiRestriction=%CiRestriction% CiCatalog=<path to the directory holding the Catalog.wci directory> |
In an ASP:
FormScope=/ Q.Query=compsearch Q.Catalog="<catalog_name>" |
Replace <catalog_name> with the name of the catalog as it appears in the Indexing Service console. This will ensure that you are running the widest possible search with the most chances of returning results against the correct catalog, with nothing on the query line to prevent results from appearing.
Adobe makes a filter to enable the indexing of .PDF (Portable Document Format) files. After you install the filter, you may notice that .PDF files are no longer indexed after the Indexing Service is restarted or the computer is restarted.
The problem is caused when the Indexing Service restarts and reregisters all of the filter .DLL files. One of these .DLL files has a default association with the .PDF extension and therefore registers itself as the filter for these files. To fix this problem, ensure that the list of filter .DLL files includes the PDF filter by following these steps:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ ContentIndex |
When you use the Indexing Service to run a query and you set the sort method to anything other than Rank Descending, you do not receive the top matching records and you may get a different set of files on subsequent queries. Sorting on Rank Descending is the only way to get the top matching records from the catalog when the maximum number of returns is limited. Sorting on anything other than Rank Descending returns a subset of the total matching documents.
If the Indexing Service reports that the catalog is corrupted after the indexing process is completed, it means that a file can't be filtered and that Filter Retries is set to a number greater than 4. This can occur as soon as the indexing process has completed or several minutes later.
When this happens, the information that the filter process sends to the Indexing Service causes a report that the catalog information is corrupted even though the data on the drive is fine. To fix this, start the Registry Editor (Regedt32.exe) and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\FilterRetries. Change the value of this key to 4 or less, close Registry Editor, and restart the Indexing Service.
On occasion, it may take an extremely long time to index documents, and some documents may appear not to get indexed at all. In addition, the abstract for documents may be blank or contain incorrect information. This is usually caused by third-party software that places a lock on the Web content that you are attempting to index. Antivirus software programs and any other software that monitors or scans your Web content for extended periods of time can cause this problem. To work around this problem, disable any software that may be monitoring the Web content.