ABBYY Finereader And Snow Leopard – File Not Created With ScanSnap

We’re a group of volunteers and opening a new scheme in our community. Your website offered us with valuable information to work on. You’ve done a formidable job and our whole community will be thankful to you.

I own a ScanSnap S510M with Abby FineReader. However I want to use fine reader to also convert a few pdfs that weren't created or scanned by the ScanSnap and am getting a message that it wont do it because it wasn't created by it. What is the easiest way for a mac user to change this to work. I have seen a few info file programs for the mac to look at the creator type but if I drop a pdf that has been created from the scanner, it doesn't give me any info as to what the creator type is or what I might need to change.
Thanks for your ideas

hopefully this put up doesn’t seem a number of times (it seems to freeze once i try to submit my comment.. not sure if it’s really posting), however all I really wished to say was good submit and thanks for sharing.

Though the new versions work, you're still much better off scripting Fine Reader for any volume of scanning. I modified the script a little to reflect not needing to hack around incompatibilities, and now kick off my OCR jobs every night before going to sleep. It's sped up my scanning dramatically.

My revision of the script is available here:
http://gist.github.com/321839

For anybody that hasn't figured this out already that is landing on this article, you can download the updated SnowLeopard version of FineReader for ScanSnap at the bottom of Fujitsu's Snow Leopard Compatibility page. Link below.

http://www.fujitsu.com/us/services/computing/peri…

I've been reading the fixes, but the pdftk script did not work for me. However, I ran across a very cool utility – "a-pdf". Select a whole folder of PDF files, type in the Creator and Producer to the ScanSoft settings, and off you go…PERFECT!
For those that don't want to fool with scripts, give this a try. They have a 15-day trial.

http://www.a-pdf.com/rename/?product-rn

A nice side benefit to finding a fix for the bug…I am moving over from Paperport to the ScanSnap solution. I have 7 years of PDF scan files that are not in searchable PDF format (Paperport creates it's own proprietary index). Using this utility, I just reset all the metadata for these PDF files and ScanSnap Organizer is busy converting them all to searchable PDF files!

Fujitsu has announced an update for ScanSnap Manager for S1500M, S300M, S510M and S500M that will work with Snow Leopard. Check out the following website:

<http://www.fujitsu.com/us/services/computing/peri…

At the bottom of that page, they state that ABBYY will be hosting the update to FineReader for ScanSnap, but the link isn't available yet. I imagine that it'll be posted somewhere soon…

FineReader update announced. Here's a summary from MacNN:

http://www.macnn.com/articles/09/11/11/gains.snow…

Quick question if I may. I'm trying to use the scansnap in snow leopard to regognise highlighted text, incorporate that into the pdf's metadata and then automatically generate the file name from that metadata keyword information. I have no problems getting the highlighter pen to work and to create an automator script to see that metadata. Where I'm having no luck is how to get automator to incorporate that info into the file nae.
Looked everywhere and only have a very very basic knowledge of automator (and none of applescript) so any help with this would be much appreciated.
Thanks in advance.

Well, we got an update from Fujitsu! They say "Fujitsu is still working hard to complete the ScanSnap Snow Leopard compatibility update. We expect to have it ready to share with all of you by the end of November…"

Thanks for this. A quick note — you can add two lines to the PDFInfoString.txt file to make pdftk change the PDF's creator, too. Then you can get rid of the 'pdfauxinfo' step.

My file reads:

InfoKey: Creator
InfoValue: ScanSnap Manager
InfoKey: Producer
InfoValue: Mac OS X 10.5.7 Quartz PDFContext

@Paul — you rock! Incredibly simple fix — shame on ABBYY and Fujitsu for not fixing this. It is pathetic.

How will we know when the new version is out? I found this with Google, must I keep pinging Fujitsu, or Abbyy, or…? Thanks

According to Abbyy, Fine Reader is not compatible with Snow Leopard! They are working on a new version but until ……………..

I created a new Automator Service, added the "Run Shell Script" action, kept the shell at "/bin/bash", changed the Pass Input to "as arguments", then created the following shell script:

for f in "$@"
do
/usr/sbin/pdfauxinfo -k "ScanSnap Manager" -i "$f" -o "$f"
/usr/local/bin/pdftk "$f" update_info /usr/local/lib/PDFInfoString.txt output ~/Downloads/-Scripts/TempPDFtkFile.pdf
mv -f ~/Downloads/-Scripts/TempPDFtkFile.pdf "$f"
g="${f##*/}"
g="${g%.*}"
open -a 'FineReader for ScanSnap.app' "$f"
while [ ! -e "${f%.pdf} processed by FineReader.pdf" ]; do
sleep 30
done
sleep 15
mv -f "${f%.pdf} processed by FineReader.pdf" "$f"
/usr/local/bin/growlnotify -a "FineReader for ScanSnap" -t "FineReader for ScanSnap" -m "FineReader has finished OCRing $g"
done

-where pdfauxinfo is a command line utility that can set the creator/author/password/etc of a pdf. It's free from http://msyk.net/macos/pdfauxinfo/
-where /usr/local/lib/PDFInfoString.txt is the "bugfix.txt" file Michael F described above.
-where ~/Downloads/-Scripts/ is just some random directory into which I can temporarily store a file. PDFtk doesn't allow the output file to overwrite the input file.
-where growlnotify is the command line version of the popular notification utility. It's free at http://growl.info/ That line can be removed if desired.

I'm not a shell script writer, but the above script works for me. It works especially well in Snow Leopard as a Service. I can right-click on a bunch of PDFs and select "OCR PDFs with FineReader" (which I named my service) and it works like a champ.

I too was screwed by this incompatibility. I told Abbyy a month or so ago about the issue and explained exactly what the problem is to them (the format of the PDF that Mac OS X generates changed slightly and their software doesn't handle it correctly). I have an alternative fix for this which I'm happy to share if you contact me directly at pmarcos@comcast.net. It involves installing what's called an "Input Manager" bundle which patches their software to avoid this issue.

I get the 'File Not Created with ScanSnap' error too. I too am surprised they didn't anticipate this during Snow Leopard beta.

Chalk me up as another dissatisfied user w/ the 'File Not Created with ScanSnap' error.

I encounter the following error dialog anytime I throw a pdf at ABBYY FineReader: Error
Problem was encountered while loading component files. Can't proceed.

Totally incompetent on Fujitsu ScanSnap (in their responsibility to manage a relationshiip with their suppliers) that the fix wasn't ready before Snow Leopard left beta.

It would be interesting to see whether the problem is with Scansnap Manager (not setting the PDF metadata "Creator" field properly under Snow Leopard) or with Finereader (not reading the field properly from the PDF under Snow Leopard).

A good test of case 2 would be to take a PDF scanned under Leopard, and try dropping it onto the "Scan to OCR" app in the "Finereader for Scansnap" folder (in Snow Leopard), and see what happens.

Another test (case 1) would be to scan a PDF under Snow Leopard, then copy it to a Leopard machine and drop it onto "Scan to OCR".

This bug is personally my one showstopper in upgrading to Snow Leopard — if anyone has already upgraded and would be interested in troubleshooting with me, leave a comment and we can be in touch privately.