PDFlib TET PDF IFilter 4.0 Manual

5.2 Problems with TET PDF IFilter Operation
If TET PDF IFilter does not seem to work as expected, the analysis methods discussed below
may help.
Identifying problematic documents. Depending on the IFilter client in use, logging entries
may or may not include the names of affected files, and file names may or may not
be useful. For example, Indexing Server does include file names, while Windows Desktop
Search does not include them. On the other hand, SharePoint downloads the documents
via HTTP and creates a temporary local copy. The event log contains the temporary
local file names which are unrelated to the original URLs. As an aid for identifying
the affected PDF documents the event log entries contain the file size in bytes. You can
use the search engine itself to quickly identify affected documents.
> In Windows Desktop Search you can use the following query expression (assuming
12345 is the file size in bytes):
size: = 12345
> With Indexing Service use the following query (assuming 12345 is the file size in
bytes):
@size = 12345
> In SharePoint you can identify failed attempts to filter a file in the SharePoint crawl
log (Shared Services Administration: SharedServices, Search Settings, Crawl Log). The errors
regarding PDF documents listed here correspond to the errors issued by TET PDF
IFilter in the Windows application event log. By comparing the file size of the files in
the crawl log with the entries in the event log you can identify problematic documents.
Locked PDF documents will not be indexed. If an application locks a PDF file, TET PDF
IFilter cannot index the document. In particular, files are locked as long as they are
opened in Acrobat. While the IFilter client may retry the locked document later, the index
will be incomplete until the locked document is released. We therefore recommend
to avoid viewing PDF documents in Acrobat during indexing.
5.2 Problems with TET PDF IFilter Operation 73