PDF documents and Verity Problem

Forum|Forum|17 years ago
July 25, 2008
5 replies
3493 views

We have an application that periodically indexes the document folder using cfindex.

If the folder contains PDF documents not created using CFPDF and are standard, the verity index process works correctly.

PDFs can contain forms and form data.

However, if I use CFPDF to use these particular PDFs to populate/flatten/merge and create new PDFs in the document folder and reindex the verity collection, the indexing process (KVOOP.EXE) uses up to 100% of the CPU process and crashes the Cold Fusion server and/or freezes the computer.

Is there a known bug with Verity and PDF forms created with CFPDF tag??

-------------------------------

After further investigations and checking the log files, I have come down to these error messages being the reason.

Warn E0-1514 (Drvr): TstrIOFilter:flt_kv: KV failed on filtering document: error = 6

Warn E2-0527 (Document Index): Document 13 (C:\Content\Document Test 155816.pdf): Stream error (-140) - SKIPPING

Invalid document ID/key. (-25)

How could I get around these errors?

Advanced techniques

This topic has been closed for replies.

Z

Zoe_Williams

Participating Frequently

Hey Aussie_Coder, did you fix this problem?

I'm using CF7 and its not indexing any PDFs created using 'Acrobat PDFMaker 9.0 for Word' and giving me the 'Stream error (-140) - SKIPPING' error like what you're getting. PDFs created in previous versions of 'Acrobat PDFMaker for Word' are being indexed fine.

The company is planning on upgrading everyone to v9 so this could be a huge issue for me soon.

Any hints or tips from anyone would be greatly appreciated.

Thanks

Z

Zoe_Williams

Participating Frequently

I have figured it out....

Adobe Acrobat v8 saves PDFs in v5 (1.4) format by default. Adobe Acrobat v9 saves PDFs in v7 (1.6) format by default.

ColdFusions CFINDEX doesn't like PFDs saved in v6 (1.5) or higher. So if you upgrade to Adobe Acrobat v9 and want to use the PDFs in a CF verity search you need to configure Distiller to save in v5 (or earlier) format so they can be indexed. (Or just resave the files to be optimised for v5 after they have been created.)

My solution was to configure the application to do a CFFILE READ on the PDF when a user uploads the document into the system. The first 8 characters of the file contents indicate the PDF version. v4 and v5 will work. v6+ won't work.

Hope this comes in handy for someone one day!