97. Why are my WorkSite jobs failing after upgrading EzeScan? |
|
If you have just upgraded your EzeScan to version 4.2.34 (or above) and finding that your WorkSite KFI / UPLOAD jobs are failing it could be due to the WorkSite Operator field not being populated correctly. Firstly check with your WorkSite administrator to see if the WorkSite field "Operator" is mandatory. If so, the Target UPLOAD field mapping of "Operator" needs to be set. There are two options that can be used here. Set the Operator Target Field to a static value and put in a valid WorkSite username. or Set the Operator Target Field to a static value of "<<S2>>" <<S2>> this is the EzeScan placeholder of the windows login name. When these values have been set, the respective username will be applied to the Operator WorkSite field. If the upload issue is still occuring after applying these settings please contact us for further assistance.
|
MOST POPULAR FAQs
- 14. What scanners are supported by EzeScan?
- 52. What are the minimum hardware / software specifications required to install and run EzeScan?
- 41. Why is my Avision Scanner scanning images as white text on a black background?
- 48. How do I configure EzeScan PRO+KFI to import .XST files produced by a Xerox MFD?
- 47. My Canon DR9080C scanner has stopped working with EzeScan via the TWAIN driver?
- 16. How do I add words to the Internal OCR Engine custom dictionary?
- 42. Why is the UPLOAD Objective 6.3/7.X Integration complaining about a missing objpb63/objpb dll?


