Error 17000001 on action FNP8_SetURL in IBM Datacap Taskmaster Capture

Error 17000001 on action FNP8_SetURL in IBM Datacap

Taskmaster Capture

Abstract

Unable to connect to Content Engine 5.1 Server from Taskmaster.

Encountering the following error from the Export_rrs.log

"Error (385875969=hex:17000001). In CIMainAlgorithm::execute4DCO: Aborting: Action [FNP8_SetURL] requested abort [api source:]"

Cause

Document Title not defined.

Resolving the problem

Add the action FNP8_SetDocTitle action prior to FNP8_SetURL in the Export ruleset.

 

Taskmaster Web reporting a Capability error during scanning in IBM Datacap Taskmaster Capture

Taskmaster Web reporting a Capability error

during scanning in IBM Datacap Taskmaster Capture

 

Abstract

Attempting real scan in Taskmaster Web results in a "capability 6" or similar error

Symptom

While scanning in Taskmaster Web, a "capability 6 is not supported" message is reported. Pages fail to scan.

Resolving the problem

Capability errors reported during scanning in Taskmaster Web usually indicate a scanner problem with the Windows operating system's connectivity or device detection. If you receive a Capabilty error, perform the following steps:

1. Ensure that the scanner can scan offline using the same exact TWAIN source. A test program such as Twacker from twain.org can be used to test the TWAIN driver. Note: scanning with ISIS or Kofax is invalid since Taskmaster Web supports only TWAIN. If scanning offline fails, try restarting the scanner and/or machine. Please note that certain scanners may require that the scanner be turned on prior to starting up the PC.

 

2. If step one completes successfully, ensure that all scanner settings specified in it are identical to those used in Taskmaster Web. You can enable the "alter scan settings" check box prior to clicking Scan in Taskmaster Web to review basic and advanced scanner settings.

 

3. If scanning offline using TWAIN succeeds, using the identical scanner source and scanner settings, but the problem persists in Taskmaster Web, then ensure that all browser settings for Taskmaster Web are valid. Use the "IE Test Page" linked from the login to validate settings; let the test page completely load before clicking the Test! button.

 

4. Should the problem persist, ensure that the Windows user logged into the machine has full permissions to the local scan folder, assuming the workflow has an upload task. This folder is typically C:\Datacap\scan. Alternatively, use a local administrator account for testing.

If you continue to have problems, contact IBM Support for additional assistance

Batch Pilot scan error: "Wrong object passed as an argument" in IBM Datacap Taskmaster Capture

Batch Pilot scan error: "Wrong object passed

as an argument" in IBM Datacap Taskmaster Capture

 

Abstract

Receiving message "wrong object passed as an argument" when scanning with Batch Pilot in IBM Datacap Taskmaster Capture

Symptom

Error reported when scanning with Batch Pilot in IBM Datacap Taskmaster Capture

Resolving the problem

To resolve the issue, enable the "unload form on end batch" task setting:

1. Open IBM DatacapTaskmaster Client

2. Go to Settings | Workflow

3. Expand a job and highlight the scan task

4. Click Setup to bring up Task Setup

5. Choose File | Task Settings

6. Enable the "Unload form on End Batch" checkbox

7. Click OK, Done and then Apply/Done

8. Restart IBM DatacapTaskmaster Client and resume scanning

 

If the problem persists, try temporarily setting Task Instances to Leave Running. This is a user specific setting that must be performed on the scan machine when logged into Windows as the operator; the setting can be modified through Settings | General | Advanced.

Barcode recognition aborts with message "hDIB property was not set" in IBM Datacap Taskmaster Capture

Barcode recognition aborts with message

"hDIB property was not set" in IBM Datacap

Taskmaster Capture

 

Abstract

Barcode recognition aborts with message "hDIB property was not set" in IBM Datacap Taskmaster Capture

Symptom

Batches aborting during barcode recognition with this specific RRS log error message:

A problem was encountered while performing smooth zoom :

[....]

************************************************************

* ERROR! --> 'RRunner OnActionEnd() has caught an error from the previous action.'

* DESCRIPTION: BarcodeXpress Error. The hDIB property was not set. Please set it or adjust the ImageSource property.

* NUMERIC ID: -2147212485

* SOURCE: PegasusImaging.ActiveX.BarcodeXpress.5

************************************************************

Diagnosing the problem

Enable RRS logging and examine the RRS log reporting the aborting action in the problem batch

Resolving the problem

Upgrade to the latest software version, including Fix Packs If the problem persists, open up a service request with IBM Support and upload a sample batch for analysis to the new service request record.

 

APTlayout.aspx does not display properly with IBM Datacap Taskmaster Capture

APTlayout.aspx does not display properly with

IBM Datacap Taskmaster Capture

Abstract

When Taskmaster Web has been configured to use the aptlayout.aspx page, it does not display properly, having grayed out sections and not fitting properly on the screen.

Cause

Aptlayout.aspx was designed for a screen resolution of 1024 x 768. Higher resolutions, particularly ones above 1280 pixels horizontally, will not display properly.

Resolving the problem

Lower the resolution of the desktop to 1024 x 768 or another resolution that displays aptlayout satisfactorily.

Exception has been thrown by the target of an invocation error with IBM Datacap Taskmaster Capture

Exception has been thrown by the target of an invocation

error with IBM Datacap Taskmaster Capture

Abstract

Datacap Studio fails to start, stating that an exception has been thrown by the target of an invocation.

Symptom

The following message box appears:



Title: Studio
Body: application error! Exception has been thrown by the target of an invocation.

Cause

This issue can occur if a necessary font such as Arial is not installed on the workstation.

Resolving the problem

Ensure that all standard fonts are installed on the workstation, to include Arial by confirming it is visible in the %windir%\Fonts folder. If not, install the font.

Entered field data is not saved with IBM Datacap Taskmaster Capture

Entered field data is not saved with IBM

Datacap Taskmaster Capture

Abstract

When entering data during the Taskmaster Client Verify (Batch Pilot) task, the entered value is not saved. This can occur for one or more fields, when placing the batch on hold or when later navigating back to the page.

Cause

The most common cause is incorrect control properties on the Batch Pilot form.

Resolving the problem

If the problem does not occur when auto-forming new Verify panels, then add custom changes one-by-one to isolate the problem to custom code.

If the problem does occur when auto-forming new Verify panels, then review field names inside the setup hierarchy. Trailing spaces are not supported inside a field name, ex: ABC_ (where the underscore is a space), and must be removed from the setup hierarchy prior to auto-forming new panels and processing a newly created batch.

Couldn't create DC_P8 FileNet object error with IBM Datacap Taskmaster Capture

Couldn't create DC_P8 FileNet object error

with IBM Datacap Taskmaster Capture

Abstract

Running FileNet P8 actions with Taskmaster Capture generates the following error:

Couldn't create DC_P8 FileNet object.
ERROR!!! N–2147024894

Cause

The dll is not registered with Microsoft .NET Framework 2.0 on the machine running the FileNet P8 actions.

Resolving the problem

To resolve this, register DC_P8_Server.dll with the codebase flag using the following command:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm.exe C:\Datacap\dcshared\DC_P8_Server.dll /codebase

Note:

• Microsoft Web Services 2 SP3 must be installed on the machine.


• Only one version of the DLL should be placed into a 'path' directory (e.g. system32, dcshared, etc).

Couldn't locate RRX code with IBM Datacap Taskmaster Capture

Couldn't locate RRX code with IBM Datacap

Taskmaster Capture

Abstract

When running a task, an action aborts with an error indicating that an RRX could not be found.

Symptom

The RRS log will state:

error: couldn't locate RRX code '[library].rrx'

Cause

The logged RRX file could not be located by IBM Datacap Taskmaster Capture. This may especially occur when migrating from an earlier version of the product.

Resolving the problem

Ensure that the RRX path logged by the action is a valid file path accessible by the account running the task. If the path is invalid, double-check the environment's configuration per the IBM Datacap Taskmaster Capture Installation and Configuration Guide Version 8.0.1.

When migrating from an earlier version of Taskmaster, any application specific RRX files will need to be modified to remove the ".rrx" extension from included library references. Edit the custom or application specific RRX file and modify XML tags as needed.

Ex: <i ref="validations.rrx"/> becomes

In the example above, "validations.rrx" causes aborts when invoked because validations.rrx has been replaced with validations.dll in Taskmaster 8.0.1.

 

Pilot.GetProfileString returns an incomplete value with IBM Datacap Taskmaster Capture

Pilot.GetProfileString returns an incomplete

value with IBM Datacap Taskmaster Capture

Abstract

The Pilot.GetProfileString method is truncating the end of the string, returning an incomplete value.

Cause

The Pilot control's GetProfileString method has a limitation of 259 bytes, so anything beyond the first 259 characters will be truncated and ignored.

Resolving the problem

This can be resolved by getting multiple values and concatenating them.

BarCode: Failed to load an image file with IBM Datacap Taskmaster Capture

BarCode: Failed to load an image file with

IBM Datacap Taskmaster Capture

Abstract

When reading a barcode, the batch aborts and the RRS log contains the error message:

BarCode: Failed to load an image file

Cause

A variety of issues can cause barcodes to abort the batch, included unsupported barcode types and corrupt images.

Resolving the problem

To resolve, do the following:

• Verify the image is a supported format for the Barcode/X engine. This engine accepts black and white images only, and does not support LZW compression.


• Check the size of the image and try loading it into various image viewers to see if it is corrupt.


• Check to see if another process or action is running that has the image open / locked.

 

ICR/P error #-2147418113 with IBM Datacap Taskmaster Capture

Abstract

The ICR/P Parascript option gives an error when recognizing a field and the batch aborts. The error text is:

ICR/P error #-2147418113: ICR_P: Incorrect field type, or this field type is not registered in a system.

Cause

Taskmaster cannot locate field type information.

Resolving the problem

To resolve:

1. 1. Edit the registry by adding a new Key HKLM\SOFTWARE\Parascript\FieldScript 3.0 (Parascript should already exist; do not name the key FieldScript 4.0; or FieldScript 4.1).


2. Edit the registry by adding a new Key HKLM\SOFTWARE\Parascript\FieldScript 3.0\FieldTypes.


3. Edit the registry under the newly created key Field Types by adding a new String Value called Directory.


4. Update value of (STRING) Directory to point to C:\Datacap\dcshared\ICRP\FieldScript4.1\FieldTypes


5. In Command Prompt (use Run as Administrator to start the program if UAC is enabled) the following command:
   C:\Datacap\dcshared\ICRP\FieldScript4.1\BIN\FieldTypeInstaller.exe /ia
   /d"C:\Datacap\dcshared\ICRP\FieldScript4.1\FieldTypes"

Note: A valid SoftKey must be installed on the machine running ICR/P recognition.

IBM Datacap Taskmaster Capture is allowing only one client connection at a time

IBM Datacap Taskmaster Capture is allowing

only one client connection at a time.

Problem(Abstract)

Datacap Taskmaster client application is allowing only one connection at a time.

Cause

The UNC path of Taskmaster client application is missing in the Datacap.xml.

Resolving the problem

Putting the UNC path to the application in the Datacap.xml file will resolve the issue.

To add the UNC path to an app, the format is as follows:
<app name="appname" ref="\\servername\Datacap\appname"/>

Here is the content of the default datacap.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<datacap ver="8.0">
<app name="1040EZ" ref="1040EZ"></app>
<app name="Express" ref="Express"></app>
<app name="Flex" ref="Flex"></app>
<app name="Survey" ref="Survey"></app>
<app name="APT" ref="APT"></app>
<app name="MClaims" ref="MClaims"></app>
<app name="AppWizard" ref="DStudio\AppWizard"></app>
</datacap>

Here is the content of the default datacap.xml file with a UNC path for 1040EZ:

<?xml version="1.0" encoding="UTF-8"?>
<datacap ver="8.0">
<app name="1040EZ" ref="servername\1040EZ"/>
<app name="Express" ref="Express"></app>
<app name="Flex" ref="Flex"></app>
<app name="Survey" ref="Survey"></app>
<app name="APT" ref="APT"></app>
<app name="MClaims" ref="MClaims"></app>
<app name="AppWizard" ref="DStudio\AppWizard"></app>
</datacap>

Input is too long error creating Oracle tables with IBM Datacap Taskmaster Capture

Input is too long error creating Oracle tables

with IBM Datacap Taskmaster Capture

(Abstract)

When attempting to create a table in Oracle programmatically using Taskmaster,

an error is received stating input is too long.

Symptom

The exact error message is:

SP2-0027: Input is too long (> 2499 characters) - line ignored

Cause

Oracle cannot accept commands with 2500 or more characters in them.

Resolving the problem

To resolve the problem, break-up any statements that exceed 2499 characters

into separate lines and try again.

VScan aborts after changing the batches directory path with IBM Datacap Taskmaster Capture

VScan aborts after changing the batches

directory path with IBM Datacap Taskmaster

Abstract

VScan aborts in Taskmaster Client or Taskmaster Client Service after changing the batches directory path in Taskmaster Application Manager.

Cause

When using Taskmaster Client or Taskmaster Client Service, any change to the file path of the batches folder must be followed by going to Task Settings and resaving the task in order to propagate the setting from the application file to the admin database.

Environment

This is applicable only to Taskmaster Client and Taskmaster Client Service, not any other clients to include Taskmaster Web.

Resolving the problem

After changing the batches directory path, do the following:

1. Open Taskmaster Client


2. Go to Settings -> Workflow


3. Expand the corresponding workflow


4. Locate and select the batch creation task


5. Click the Setup button


6. Go to File -> Task Settings and then press OK on Settings for VScan task


7. Click Done on the VScan Setup - Batch Pilot window


8. Click Apply on workflow window, then click Done

If there are multiple jobs, the steps do not need to be repeated for each scan task unless a different scan module is used.

IBM Datacap Taskmaster Capture cannot complete Verification on some documents

Datacap Taskmaster cannot complete

Verification on some documents

Abstract

After verifying the document, Verification reports: "Verification is not complete. Put Batch on Hold?" Unable to complete Verification despite having all fields completed.

Cause

The document type must have a problem STATUS filter assigned to it and Verification must be able to change the status as fields are corrected.

Resolving the problem

Set the STATUS filter

1. In Taskmaster Client, go to Settings -> Workflow.


2. Expand the job being used and highlight the Verify task.


3. Click Setup from the right side and then File -> Task Settings.


4. Click on the Filters tab and in the Type section, select the document type.


5. Make sure that the Level drop-down list is set to PAGE and Property is set to STATUS.


6. Enter 1 into Problem Value field and click Add.


7. Save changes, apply, and restart Taskmaster Client.

Allow Verification to change the status

Add the Status_Preserve_OFF action as the first action of the function that handles page validation.

Maximum connections reached with IBM Datacap Taskmaster Capture

Abstract

Datacap Taskmaster client applications fail login to the Taskmaster Server service. Logging shows an error stating that the maximum number of available connections has been reached.

Cause

Certain rare events can leave an orphaned login within Taskmaster. If enough of these occur for a specific station, than any further logins from that station will fail, as no more connections are available. This requires that either the connections be reset or the maximum increased.

Resolving the problem

Reset the connections

1. Make sure that no client applications are logged in from the station that will be reset.


2. Run Taskmaster Client. It can be run from any station including the one being reset.


3. Log in as admin or any other user with full rights.


4. Select Settings, Stations, and highlight the station to be reset.


5. Click Advanced, Reset.


6. Click Yes of the warning window.


7. Click OK, Apply, and Done to close the remaining windows.

Increase the maximum connections

1. Run Taskmaster Client. It can be run from any station including the one being reset.


2. Log in as admin or any other user with full rights.


3. Select Settings, Stations, and highlight the station to be reset.


4. Click Advanced.


5. Change Maximum number of virtual stations to 1000 or some other large value.


6. Click OK, Apply, and Done to close the remaining windows.

Couldn't load needed object with IBM Datacap Taskmaster Capture

Abstract

Convert is failing and generating the following message in the rrs log:

Couldn't load needed object: Datacap.Libraries.Convert.Pdf into Datacap.Libraries.Convert.Pdf instance

Cause

This error occurs when the Datacap Taskmaster PDF (DCPDF) components have not been installed or registered correctly.

Resolving the problem

To resolve this issue:

• Make sure that all the system32 files have been copied to the system folder on the computer running the DCPDF actions.


• Make sure that pdfshell.dll and PDF2TIFFEx.dll have been registered.