There are several things to look at, but first a quick explanation of how the <Import Folder> button works:

  1. 1. When you press <Import Folder> EzeScan first looks in the job workflow subdirectory (e.g. c:\program files\outback imaging\ezescan\workflow\your_job_name) to see if it is currently processing a document. The workflow directory is an internal directory created by EzeScan, you don't get to specify where it is located using our setup forms. If the operator stops processing a job or EzeScan quits unexpectedly we know that the last job will be always be kept intact in the workflow subdirectory. So if there is a file left in the directory and you have pressed the <Import Folder> button on the Operator Actions form (F2/F6), then we simply reopen it and carry on processing it.
  2. If there are no files in the workflow directory then EzeScan will start importing files from the job import directory (e.g. c:\program files\outback imaging\ezescan\input\your_job_name) 1 file at a time. EzeScan moves the file from the job import folder into the job workflow directory  (e.g. c:\program files\outback imaging\ezescan\workflow\your_job_name), and then displays the document in EzeScan.  If "Start to auto profile document" is ticked it will begin to profile the document automatically.
  3. If there are no files in the workflow directory (e.g. c:\program files\outback imaging\ezescan\workflow\your_job_name) and no files in the job import folder  (e.g. c:\program files\outback imaging\ezescan\input\your_job_name) and Import Folder has been configured with "Keep Polling" with a "5" second interval then EzeScan will go into polling mode. Every 5 seconds it will test to see if any files have arrived in the import folder. Depending on it's configuration EzeScan may also search for files using methods mentioned below:
    • If you are using the "Import from Folder" options then EzeScan will traverse sub directories to find the next file to import. It will move the file to the job workflow directory, then open it and begin processing it. Depending on the configuration options, it may also delete empty import subdirectories as it goes through the import directory structure.
    • Or if you are using the "Import from Email" option then EzeScan will read 1 item of email from the specified mailbox, detach any images from that email messages, and then place the image into the job import folder (e.g. c:\program files\outback imaging\ezescan\input\your_job_name), where on the next import folder polling pass it will be actioned by EzeScan.
    • Or if you are using the "Import from FTP" option then EzeScan will FTP up to 10 documents from the remote FTP Server and place them into the job import folder (e.g. c:\program files\outback imaging\ezescan\input\your_job_name), where on the next import folder polling pass it will be actioned by EzeScan.
  4. Once a file drops into the import folder (c:\program files\outback imaging\ezescan\input\your_job_name) , EzeScan moves the file from the import folder into the job workflow directory  (e.g. c:\program files\outback imaging\ezescan\workflow\your_job_name), and then displays the document in EzeScan.  If "Start to auto profile document" is ticked it will begin to profile the document automatically.
  5. Once the document is displayed in the EzeScan Viewer, it is then profiled and stored according the job's "Other Destination" settings. The final step in storing the file is to remove the copy of the file that was in the job workflow directory, and then the steps 1-5 repeat themselves for the next file to be processed.

So what can go wrong with this process?

  • Sometimes you look in the import directory and see plenty of images files, but EzeScan never opens any of them, it just keeps polling!
  • Sometimes EzeScan encounters a problem when it searches for the next file to process either in step 1, 2, or 3 above. The most common problem is when the import code attempts to process a non image file (i.e. one that does not have a .tif, pdf, gif, bmp or jpg file extension.
  • The import folder setup includes a file types button. If you press this button you will see a list of file types EzeScan will process (normally tif, pdf, bmp, gif and jpg) and also an empty list of files to delete/ignore. Sometimes windows might create a file like thumbs.db in the import folder or workflow folder. This will cause problems for the import folder code unless you specifically add the "thumbs.db" file extension to the list of the files to ignore. If you are using a Xerox Copier then you should also add .XST files to the list of files to be deleted.
  • So simply removing the rogue file from the import folder or job workflow directory will normally fix the problem. Adding it's file extension to the delete/ignore list should stop it happening again. To make it easier to clear the stuck file, the F2/F6 Operator Actions form includes a <Clear> button. This buttons will clear any files that are stuck within the job workflow directory. Press the <Clear> button, followed by the <Import Folder> and things should go back to normal.
  • Sometimes you are part way through profiling a document and you simply close EzeScan before you completed the profiling of the document. If you did not specifically delete the remaining pages, then they will reappear each time you press the <Import Folder> button.  On the F2/F6 Operator Actions form press the <Clear> button and EzeScan will get rid of the leftover document once and for all.
  • If you have tried any of the fixes above and things are still not working? Then one final thing to try is to restart EzeScan. If this fixes the problem then we may have a programming issue. Let us know so we can look into it for you.
Direct link to FAQ