When running a scan job on the ADF of some scanners you might find that only the first page is being scanned. This problem is known to occur on Ezescan installations that have recently been upgraded from version 4.0 to 4.1 or above, where the Ezescan TWAIN settings have been enabled.

To rectify this issue open the Admin Jobs form (F6) ->select the scan job -> open the Scan tab -> within the tab enable the 'MT' and 'SA' options -> and then save the job. Once you have reached this point your scanner should now be able to scan all the pages in the ADF tray.

Direct link to FAQ

EzeScan KFI is not always loading the value into a TRIM Context Foreign Barcode field.

The first time save an image into TRIM Context and you load a value of 123456 into a TRIM Foreign Barcode field it works. But when you save the next image and try to reuse the value of 123456 in the TRIM Foreign Barcode field, it just leaves the field blank?

Why? Well its because the Foreign Barcode value should be unique. In reality a physical sticker would be printed and affixed to one document only, not multiple documents.

So if you are testing with Foreign Barcodes values, make sure they are incrementing or changing for each document saved.

Direct link to FAQ

We have found that if EzeScan is installed with User Account Control (UAC) set to ON that some important EzeScan dll's are not properly registered.

When installing EzeScan on Vista it is required that User Account Control to set to OFF for the user installing it. It is also required the user is has Local Administratior permissions or even better to install as the Local Administrator Account.

To disable User Account Control for a user account.

1. Select Start Menu, Control Panel

2. Select "User Accounts"

3. Select "Turn User Account Control on or off"

4. Uncheck the box "Use User Account Control (UAC) to help protect your computer"

5. Click OK

Restart the PC for the changes to take effect and then try a new instalation of EzeScan.

Direct link to FAQ

If EzeScan 4.1 has been uninstalled and then EzeScan 4.2 has been installed you may find that the Operator Action \ Admin Form (F2 of F6) and the KFI Form (F7) will not load.

To fix the issue do the following.

Select Start, then Run

Type "regsvr32 msstdfmt.dll" (without the quotes)

You should then get a message with the following.

"DllRegisterServer in msstdfmt.dll Suceeded"

The issue appears to be caused by the 4.1 uninstall.

EzeScan Development are currently investigating.

 

Direct link to FAQ

If you are experiencing a technical issue with EzeScan it may help to load EzeScan in debug mode to see if any errors are logged. Debug logs are primarily designed for second-level support and development, but they also contain useful troubleshooting information that EzeScan does not normally display to the user.

Supplying a debug file to your EzeScan support channel will also assist in speeding up turnaround times to resolve your problem. We advise that you try running the software on the latest EzeScan Patch level before sending debug information to support.
 

Three different debug methods

You can view debugging information in EzeScan in three ways:
 

  1. Log messages to the debug window.

    To do this load EzeScan and press Ctrl + Alt + D. The Debug window will appear, containing log messages. Perform the task to replicate the problem and view the debug window to see the results.
     
  2. Log messages to the debug window and to a log file.

    To do this load EzeScan and press Ctrl + Alt + L. The Debug window will appear, and all messages will also be logged to a file. Perform the task to replicate the problem and view the debug window or the debug.log file. To locate the log file see Debug Log Locations below.
     
  3. Log messages to the debug log file.

    This will log the activity to a log file only and not display the Debug window. Every time EzeScan is started a new log file is created. (EzeScan will keep up to 7 log files and then rotate them automatically)

    To enable this option, copy the override.ini file below into

      For EzeScan 4.2: C:\Program Files (x86)\Outback Imaging\EzeScan 4.2

      For EzeScan 4.3: C:\Program Files (x86)\Outback Imaging\EzeScan

 

Debug log locations (EzeScan will keep up to 7 log files and then rotate them automatically)


The EzeScan debug log files will be stored by default in the following locations:

Windows 2003 Server / XP

C:\Documents and Settings\All Users\Application Data\Outback Imaging\EzeScan\Logs

Windows Server 2016, 2012, 2008 R2, 10, 8.1, 7 and Vista

C\ProgramData\Outback Imaging\EzeScan\Logs

Please note: Your installation may store log files in a different location. If they don't appear in the above folder, select the menu option Admin, Workstation Options, Config tab to see EzeScan's application data directory. Debug log files will be stored in the logs subdirectory.

Download File: 
Direct link to FAQ

Some older versions of Ezescan 4.1 and 4.2 have known issues where the Save As function does not work for Hummingbird 5.1.0.5 ODMA destinations. To rectify this issue please download and install the latest patch from the downloads section on our website.

If applying the latest patch does not rectify this problem, then try repairing your install of the Hummingbird DM Extensions.

Direct link to FAQ

A third party system may have an option to supply XML data and many multifunction devices have the ability to perform indexing at the User Interface and then send the scanned image and an xml file which will contain the data of what the operator has typed in at the device.

EzeScan can import this image plus the XML file together and use the XML data as KFI fields.

Let say for example that an operator has scanned in an image and typed in two fields. 1) Name 2) Client Number

The device will create two files.

imagename.pdf

imagename.xml

EzeScan will pickup these two files simultaneously.

 

The name field must be loaded into the Name KFI field.

The Client Number field must be loaded into the Client Number KFI field.

For this to work the following steps below must be performed.

1) In the EzeScan Job (F6) or Routing Job (F9) on the Import Tab the feature "Import Existing Index File" must be set to XML

2) In the KFI for this Job (F7) click on the Edit button for the name field. Select the Value Tab, for the option "Enter in data file" we must call the xpath value of Field 1

3) In the KFI for this Job (F7) click on the Edit button for the Client Number field. Select the Value Tab, for the option "Enter in data file" we must call the xpath value of Field 2

Once this has been setup EzeScan will read the respective field information from the XML file.

Explanation of an XPath

An xpath is a language to extract information from an XML document.

Please refer to the link below for more information to extract your Xpath information.

XPath Syntax Examples

Please feel free to contact us for further assistance with regards to XML importing and manipulating of its data.

 

Direct link to FAQ

Registering on our web site gives you the ability to download our software, documentation and sample jobs. You are also entitled to our regular newsletter, which details the latest features and enhancements to the EzeScan product suite.

To register, fill out all required fields on the user registration form.

A member of the EzeScan support team will then activate your account and send you an email notifying you that your account has been activated. You can then access the downloads section to our website. Please note that you will not have access to product downloads until your registration has been activated.

Direct link to FAQ

Multi Feed Sheet Detection is a feature that is on most new medium and high end scanners. This feature can detect if two or more sheets of paper are scanned through the ADF at the same time. The scanner can usualy have a level of detection enabled i.e. Low, Medium or High. When some sheets are misfead the scanner will beep and pause so the operator can attend the misfead and then continue the batch using EzeScan's append feature.

If the scanner is configured via EzeScan's "Use Twain Settings Below" the Multi Feed option will need to be set in the scanners configuration file as the Multi Feed option is not a part of the TWAIN specification.

For a Kodak i600 series: The file should be called setup001.ini and will usualy reside in c:\program files\common files\kodak\i6xx\ folder

For a Kodak i400 Series: The file should be called bitonaldocumentocr.profile and reside in the C:\WINDOWS\twain_32\Kodak\kds_i1400\profiles\scanner model folder.

Note: Please backup the file before making any changes!

In the configuration file you are looking for a setting called

[CAP_ULTRASONICSENSITIVITY]

This can be set to LOW, MEDIUM or HIGH

Where it says "=TWUS_" Set it to your disired setting.

e.g.

[CAP_ULTRASONICSENSITIVITY]
Current_i620=TWUS_MEDIUM

Save the file and then run a job through EzeScan. A good test to see if it is working OK is to put a small piece of paper ontop of an A4 sheet and scan it. It should catch with the page and the scanner should beep and / or stop. An Error may be displayed in EzeScan as well.

This will confirm that this feature is working with EzeScan successfully.

Direct link to FAQ

Note: Wintalk Integration requires the EzeScan workstation to be licensed for the EDRMS module, and also requires EzeScan version 4.2.10 or higher.  To obtain a copy of a sample EzeScan WinTalk  Job please see the Downloads > Software Downloads > Sample Jobs > Objective section of the website. (requires a user login)

Objective 7.5

1) Browse to the following folder C:\Program Files\Objective\Navigator 7\Extensions\WinTalk

2) Backup and then open the wintalk_application_compatibility_policy.xml file.

3) add the following to the bottom of the file but make sure it is above the
</compatibility_policy> line.

  </application>
 <application>
  <display_name>EzeScan</display_name>
  <process_name>ezescan.exe</process_name>
  <compatible>true</compatible>
  <instances>multiple</instances>
  <dialog name="Save As">
                       <view>false</view>
  </dialog>
  <release policy="prompted">
   <strategy>
   </strategy>
  </release>
 </application>

 

Direct link to FAQ

Pages