Troubleshooting


This section contains information about some actions that you can take when errors appear to have occurred with your documents.

Checking File Types

You can determine information about how the Verity engine evaluates the document type and character set for a particular document by looking at the "info" messages that the engine produces. You can see these "info" messages using mkvdk with the -verbose flag, as shown in the command-line syntax below:

mkvdk -verbose -create -collection mycoll -insert mydocs/*

The above example illustrates how to index a set of documents into a collection called mycoll in verbose mode.

You may want to check the document type recognized by the engine if errors occur. For example, if a web page is interpreted by the auto recognizer engine as a plain ASCII document, then zone searching will not work; if the auto recognizer thinks that the document is written in an incorrect character set, extended characters will not be displayed.

Disable Document Filters by MIME Type

You can disable filtering for a particular MIME Type in the style.uni file. To disable the use of a KeyView filter for the MIME Type entry, place a pound sign (#) at the beginning of each line in the entry as shown below:


# type: "application/x-lotus-amipro"
# /format-filter = flt_kv
# /charset = guess
# /def-charset = 1252
As a result, the Verity engine will not index or display documents for the MIME Type shown.





Copyright © 2002, Verity, Inc. All rights reserved.