This is a problem with the Avision Scanner driver. It can be fixed by editing the apsetup.ini file. This file will be located in either the c:\AVXXX directory or c:\FBBM directory. Open the file in Wordpad and find the section named [LineArt]. Locate the line that says EzeScan=1 and change it to EzeScan=0.

Direct link to FAQ

The below points detail what is required from a licensing and installation perspective for the steps required to have EzeScan connect to Objective.

1) The Objective Server needs to be licensed for the Client API (please check with the Objective Administrator)

2) The Objective Developers Kit needs to be installed on the EzeScan PC (please check with the Objective Administrator to obtain the installer)

3) Once the Objective Developers Kit is installed the following files need to be copied to

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

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

   a) All .dll files in C:\Program Files (x86)\OBJECTIVE\Developers Kit\VB

   b) The objapi.dll in C:\Program Files (x86)\OBJECTIVE\Developers Kit\C++

Once this is complete, EzeScan will be able to browse and save to Objective.

Notes:

If the EzeScan login/password validation is failing to connect to the Objective Server, then make sure that the objective server name and port details, and the username and password details specified in Ezescan are correct.  Try using the Objective desktop client application with those credentials to make sure that the server is up and operational. 

If the Objective desktop client application works but EzeScan still doesn't connect to the server, then try using the C:\Program Files (x86)\Objective\Developers Kit\VB\apitest.exe program to login to the objective server. If this also fails to connect to the server, then there may be a problem with the Objective Server.

Direct link to FAQ

Adobe have made some small changes to the way that the Acrobat Reader 7.0 advanced search option works with image based text searchable PDF's.   EzeScan version 4.0.407 has had 2 small improvements made to the PDF creation function to allow it to produce PDF's that are searchable by the advanced search option in Acrobat 5, 6 or 7.

Direct link to FAQ

Here's what you need to do to get it working.

  1. Start EzeScan
  2. Press F2 to start the Operator Actions form.
  3. Select the job you want to fix.
  4. On the scan tab, set Threshold to zero (0). This disables this setting.
  5. Set Brightness to 128 and Contrast to 128.
  6. On the enhancement tab, tick the Despeckle 1x1 option.
  7. Save those settings.
  8. Repeat steps 3-8 for as many job types that you have setup.

That should fix the problem and you should now be able to scan okay in black & white.

Direct link to FAQ

 

In KFI follow these simple rules for the zone that will contain the DS Folder value.

  1. Use a leading backslash (e.g. \Initial Top Level Collection A or \Clients)
  2. Use \ between each collection name (e.g. \Clients\Invoices\2006\ACME)
  3. The top level collection name must be an existing root level collection in DocuShare. In the example above the \Initial Top Level Collection A collection was renamed as \Clients
  4. When EzeScan processes the collection structure it will automatically create any sub collections that don't exist.
Direct link to FAQ

You'll need to install MDAC 2.8. You can download it from the Microsoft website. This is only needed for Win98 or Win2000 since Windows XP includes MDAC 2.8 by default.

Direct link to FAQ

 

Assuming it did once work okay, then sometimes the c:\windows\setscan.ini file which is used by the Canon ISIS and TWAIN drivers becomes corrupted and this causes the Canon TWAIN driver to stop working with EzeScan.

Try the following:

1) Close EzeScan

2) Rename setscan.ini to setscan.old

3) Reload EzeScan and run a job (that uses this scanner)

4) You will get a prompt for a scanner model, select your scanner in the drop down list.

5) Test that the job runs ok.

6) Load EzeScan and try the job again.

 

Contact EzeScan support if the issue is still occuring.

Direct link to FAQ

 

The following describes how EzeScan can import an image and XST file so the data can be used with EzeScan KFI.

Note: The Xerox template must be set to multipage TIF or PDF and EzeScan must be set to Import Folder Mode.

Instructions:

  • Admin Jobs (F6) -> Import Tab -> Import Existing Index File - set this to XST
  • Admin KFI (F7) -> Fields Tab -> Select "Edit" on a Field -> Value Tab -> Entry in data file -> (See below)

As we convert the XST file to an XML format for processing the "Entry in text file" value is an XML xpath query

For example in the XST file we may have:

[service xrx_svc_general]
{
string JobTemplateName = "ABC";
enum_DCS DcsDefinitionUsed = FX_APEOSPORT_C5540/C6550/C7550;
string JobTemplateDescription = "";
enum_encoding JobTemplateCharacterEncoding = ASCII;
string JobTemplateLanguageVersion = "2.0";
boolean SuppressJobLog = FALSE;
string NetworkUsername = "/";
}
end

to extract JobTemplateName the "Entry in text file" value can be either

    //JobTemplateName

OR

    //xrx_svc_general/JobTemplateName

Most fields can be extracted using the simpler first option unless there are multiple fields in the XST file with the same name (i.e. MetaData fields).
For a MetaData field below is the sample data in the XST file.

[description xrx_dscrpt_metadata]
entry_1{
string MetaDataFieldName = "Title";
string MetaDataPrompt = "Title";
string MetaDataDefaultValue = "";
string MetaDataValue = "scan by User";
}
entry_2{
string MetaDataFieldName = "Summary";
string MetaDataPrompt = "Summary";
string MetaDataDefaultValue = "";
string MetaDataValue = "this is a summary";
}
entry_3{
string MetaDataFieldName = "Description"
string MetaDataPrompt = "Description";
string MetaDataDefaultValue = "";
string MetaDataValue = "and the description";
}
end

to extract MetaDataValue for entry_2 the "Entry in text file" this value could be

    //entry_2/MetaDataValue

OR

    //xrx_dscrpt_metadata/entry_2/MetaDataValue
When the Job + KFI is run the respective value (that was typed on the Xerox UI)
will display in the KFI index panel.
Please contact EzeScan Support if further assistance is required.
Direct link to FAQ

 

A. Ezescan program executables are normally installed into the "c:\program files\outback imaging\ezescan" directory. This can be changed during the installation process if required.

Note: In older installs all the other data folders mentioned below resided under "C:\Program Files\Outback Imaging\EzeScan" by default

B. EzeScan configuration files are created in the "c:\documents and settings\all users\application data\outback imaging\ezescan" directory.

Or alternatively you can edit the "c:\program files\outback imaging\ezescan\override.ini" file to specify a different directory where the license and configuration files will be stored (in the example below, the first line is commented out and ignored, and the second line is processed).

[Folder Paths]

;Common Data=c:\Documents and Settings\All Users\Application Data\Outback Imaging\EzeScan

Common Data=C:\Program Files\Outback Imaging\Ezescan

In either case if the EzeScan users on the PC do not have local Admin rights then the you must grant the "All Users Modify" privilege on this Common Data directory and all of it's sub directories.

C. EzeScan temporary files and working files are created in the Default Application Data Directory which is initially set to  "c:\documents and settings\all users\application data\outback imaging\ezescan" directory. EzeScan creates a cache sub directory and many other sub directories in this location.

Or alternatively this directory location can be changed using the EzeScan Admin->Options form. Simply enter a new location in the Default Application Data Directory field on the General tab.

In either case if the EzeScan users on the PC do not have local Admin rights then the you must grant the "All Users Modify" privilege on this Default Application Data Directory  directory and all of it's sub directories.

Direct link to FAQ

 

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

Pages