To patch an EzeScan installation there is some steps to do to ensure it will run successfully.

The first step is to perform a backup of your EzeScan Configuration.

Please refer to FAQ 22 for details on backup.

The second step is is to check the current version on your EzeScan installation.

This can be done by selecting Help \ About \ More Details.

This will tell you your version \ patch \ build level. eg. 4.2.170.1985

Where 4.2 is the version, 170 is the patch level, 1985 is the build level

On the EzeScan Website (requires a login) the latest patch is available in the EzeScan Patch Updates folder.

Take a note of the description. It will detail the minimum EzeScan version required to apply the patch.

e.g. If the minimum version is 4.2.160 and you are running 4.2.159 or lower, you will need to download the EzeScan Full Online Installation from the EzeScan Installers folder.

If you are running 4.2.160 or above then you can download an install the patch.

Note: The EzeScan Patch usually does not require a reboot.

If further assistance is required, please contact EzeScan or your reseller.

Direct link to FAQ

An EzeScan Hotfix is fix to address a customer specific issue.

Please Note: A hotfix is not required for a normal update of an EzeScan installation. Hotfixes should only be applied under the instruction of your EzeScan support representative.

The first step is to perform a backup of your EzeScan Configuration.

Please refer to FAQ 22 for details on backup.

The second step is is to check the current version on your EzeScan installation.

This can be done by selecting Help \ About \ More Details.

This will tell you your version \ patch \ build level. eg. 4.2.170.1985

Where 4.2 is the version, 170 is the patch level, 1985 is the build level

If your EzeScan is not on the latest patch level, the hotfix will not work.

e.g. the Hotfix 4.2.170.1986 will not work if your version is 4.2.169.X or below

Please refer to FAQ 101 for details on how to patch to the latest level.

To update to the latest hotfix.

Backup the file EzeScan.exe in the C:\Program Files\Outback Imaging\EzeScan 4.2 folder.

On the EzeScan Website (requires a login) the latest hotfix is available in the EzeScan Patches & Hotfixes folder.

Download the hotfix and unzip it.

Copy the file EzeScan.exe over the top of the current one in the C:\Program Files\Outback Imaging\EzeScan 4.2 folder.

You can then load EzeScan and test if your specific issue has been fixed.

If further assistance is required, please contact EzeScan or your reseller.

Direct link to FAQ

This is a generic TWAIN error. It usually means the scanner is offline or another internal issue with the scanner.

Firstly check the scanner to see if it is powered on, restart it to see if it fixes the issue.

If this does not fix the issue it is likely that the scanner has another problem. e.g. a document feeding or sensor issue.

These types of errors are not exposed by the TWAIN protocol so EzeScan will not be able to see it.

To diagnose the issue.

1) Close EzeScan

2) Load the Vendors scanning utility (usualy is shipped with the TWAIN driver) e.g. for Kodak it is the Scan Validation Tool, for Fujitsu it is the ScandAll Application.

3) Perform the exact same scan as you were in EzeScan. The scanners application should then display a much more descriptive message of the problem.

4) Take this information and contact your scanner vendor support channel.

If the issue does not occur using the utility and does using EzeScan then it is possible that it is an EzeScan issue.

Please contact your EzeScan Support channel to diagnose the issue further.

Direct link to FAQ

Applies to: EzeScan 4.3.7 and above

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 EzeScan 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.

To enable debug logging for EzeScan SERVER

1. Copy the override.ini file below into this following folder C:\Program Files (x86)\Outback Imaging\EzeScan

Please note: in the override.ini there are settings that could be modified.

For example:

- MaxLogSize is how big the log file will be in MB

- LogsToKeep is the amount of logs to store. e.g. when the service is restarted Log 1 will become Log 2 and so on.

- RotateDaily is to create a new log at 12AM of each day.

If changes are made save the file and restart the EzeScan_Routing Service. Please remember to do this as an administrator as windows will not allow saving into C:\Program Files

 

Debug log locations

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

C\ProgramData\Outback Imaging\EzeScan\Logs

Your installation may store log files in a different location. Select the menu option Admin, Workstation Options, Config to see EzeScan's application data directory. The debug logs will be stored in the logs subdirectory.

 

If you download the FAQ104 - rename to override.ini file on this page, please rename it to override.ini

Direct link to FAQ

If you are experiencing this error on your EzeScan SERVER it is because the EzeScan_Routing service is taking longer to start than Windows allows. The default startup time allocated for a windows service is 30 seconds.

The Routing Service may not be starting for the following reasons:

1) Depending on EDRMS clients to startup or other dependencies

2) Slow or busy processor on the EzeScan Server.

 

To fix this problem, Microsoft has a Knowledge Base article on how to debug a Windows Service.

We recommend adjusting the service timeout from 30 seconds to 2 minutes.

824344 How to debug Windows services (refer to item 3)

Or follow these instructions.

  1. In Registry Editor, locate, and then right-click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  2. Point to New, and then click DWORD Value. In the right pane of Registry Editor, notice that New Value #1 (the name of a new registry entry) is selected for editing.
  3. Type ServicesPipeTimeout to replace New Value #1, and then press ENTER.
  4. Right-click the ServicesPipeTimeout registry entry that you created in step c, and then click Modify. The Edit DWORD Value dialog box appears.
  5. In the Value data text box, type 120000 (2 minutes)
  6. Under Base select the Decimal option, and then click OK
  7. Reboot the server for the changes to take effect.

 

Direct link to FAQ

Please do the following to confirm if this option is enabled.

1) Select Admin -> Jobs and select your job from the drop down list and then select the Output tab.

2) Click on the Options Button and go to the Messages tab.

3) Confirm that the option "Display EDRMS Record Number Message" is ticked.

4) Click OK and then the Save Button.

5) Run the job and confirm that the record number message is displayed.

Please contact us if you require further assistance.

 
Direct link to FAQ

This may be an issue with the version of the Objective API files being used by EzeScan to communicate with the Objective server. Please contact us to confirm that this is the issue. If it is you will need to contact Objective for further details.

Direct link to FAQ

This issue is typically the result of installing EzeScan from within a Zip file. It is always best practice to unzip the EzeScan CD .zip file into a folder and then run setup.exe.

The MSI installer displays the error as it is looking for the MSI install files in a temp folder (usually C:\WINDOWS\Installer)

To correct please do the following:

 Login to the PC using an account with local adminstration rights

 Extract the installation Zip file to the local HDD for example "C:\ezescan_cd"

 Open command prompt and change to the path to Packages subfolder for example, "cd C:\ezescan_cd\Packages"

 Type in the following command "msiexec /i ezescan.msi /L*v ezescan.log"

 Then follow the prompts on the install screen until the error occurs

 Close the installer and open the ezescan.log file that is created in the packages folder

You will see some lines like this.

    Package we're running from ==> C:\WINDOWS\Installer\1a8d065.msi

    Opening existing patch 'C:\WINDOWS\Installer\1a8d066.msp'

In this instance the folder path is C:\Windows\Installer

From the EzeScan CD rename the EzeScan.msi file to the msi file the log is looking for. In this instance 1a8d065.msi

From the EzeScan CD rename the EzeScan_Patch.msp file to the msi file the log is looking for. In this instance 1a8d066.msp

Copy the two newly renamed files into the specified folder.

Run the Setup.exe again and the installer should load correctly.

Please contact us if you require further assistance.

 

Direct link to FAQ

An OPEX scanner will save it's scanned documents as a single page TIF file and also include an XML file of the data (.oxi). EzeScan can import the documents plus data and then this can be used in EzeScan for processing.

Importing Images and XML data

To import the images:

- Create a new job in EzeScan

- Set the Job to "Enable Import Folder Processing"

- Set "Import Existing Index File" to XML (import tab)

- Specify your import and output folders.

In the Import tab there is a RUN option. In here the operator is required to enter a run command (this will combine the TIF files and import the xml data).

Please note: The operator will need to know the folder path of where the OPEX scanner is saving its data to.

Below is a sample command to import from an OPEX scanner output.

"c:\program files\outback imaging\ezescan 4.2\ezescan.exe" -mergeoxi "c:\import\opex\" -mergeto "C:\ProgramData\Outback Imaging\EzeScan\Input\Opex Test"

The -mergeoxi switch is the parent folder path of where the OPEX batch folder images and xml data resides.

The -mergeto switch is where the merge data will be moved to, typically this should be the same folder defined in the EzeScan Job Import Folder.

Press the Save button to apply the changes.

 

Extracting the XML data for use with KFI

The KFI module can be used to extract the XML data into KFI fields.

In the KFI field Value tab, there is an option called "Entry in data file" the operator needs to input the XPath of the variable.

e.g. for the Page Name varianle it would be "//Batch/Transaction/Page/@PageName" (without the quotes)

 

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

It has been reported that when using the OpenText SmartOffice integration on Windows XP SP3 the EzeScan Installer attempts to perform a repair.

To resolve this issue please download and install the Microsoft .Net 1.1 package and then reboot the PC.

Direct link to FAQ

Pages