Generate a Legacy Out-of-Process Error Log

IMPORTANT: Out-of-process error logging is available only when you configure KeyView to use the legacy out-of-process method. See Use the Legacy Out-of-Process Method.

You can monitor and debug out-of-process filtering operations by enabling a detailed error log. This enables you to see errors that are generated at run time, and to track problem files in stream or file mode.

NOTE: Error logs are not generated when in-process filtering is enabled.

The out-of-process error log might include the following information:

  • Generated error codes.
  • A time stamp.
  • The path and file name of the file in which the error occurred.
  • The length of the file in which the error occurred. If the name of the original file or the name of the temporary file are not obtained in stream mode, the file length is reported.

The following is a sample log file:

-KVOOPE 12 # Time: 11:14:32 # File Len = 68140
-KVOOPE 13 # Time: 11:23:05 # H:\files\WP\Word97\fnldmsa.doc
-KVOOPE  5 # Time: 12:15:54 # H:\files\SS\XL2000\corporate.xsl
-KVOOPE  5 # Time: 12:45:19 # H:\files\WP\WPerf5\wp501.doc
-KVOOPE 12 # Time: 14:25:33 # H:\files\PG\PPoint95\95.ppt
-KVOOPE 26 # Time: 16:26:04 # File Len = 19117568
-KVOOPE 10 # Time: 20:27:40 # File Len = 19117568

You can configure the following features of the log file: