SuperVars and application rules do not execute simultaneously in ProtoID.aspx in Datacap

When configuring a web FlexID (ProtoID) task to use SuperVars and also to run a task profile, only the custom rules are used and executed.

Solution:

ProtoID.aspx is working as designed, which is to run SuperVars or a specific task profile. To resolve the problem, modify your application rules to use either a task profile or super variables.

Older,Same batch is displayed in a Taskmaster Web session in Datacap

When trying to run a shortcut or batch in Taskmaster Web, a previously worked batch is displayed to the operator

Signs:

An operator clicks on an Operations shortcut link or attempts to run a batch manually through the Job Monitor, but the batch attempting to be selected is not displayed; instead a batch that was previously worked on by the user during his or her Taskmaster Web session is brought up.

Note: These symptoms occur even if Taskmaster Web (IIS) and Internet browser settings are configured to not cache pages, and even when bypassing the load balancer if one is applicable to the environment.

Reason:

If an operator starts a batch but does not finish it correctly, then this behavior will occur. That is to say, the operator did not cancel the batch, place it on hold, or submit/finish it. In many cases the user may have navigated away from the batch using the Internet browser's navigation buttons rather than the Taskmaster Web content buttons.

Solution:

This feature is by design for data integrity reasons. To avoid these symptoms or resolve them when they occur, the operator should use the appropriate Taskmaster Web buttons to release the original batch per normal processing. For example, in Verify the operator should index and Submit all pages or place the batch on hold. Once the batch has been processed and released per normal business procedures, the user will be able to move on to any other batch.

 

 

 

Unable to login to two applications simultaneously in Datacap

When attempting to login to a specific application, login fails unless another application is closed and stopped from all clients and services, including Rulerunner Quattro and Taskmaster Web.

Reason:

Taskmaster Server tracks which applications which are connected to the server using the db_index column stored inside the admin and engine databases (the value is identical between the two databases). If creating a new application or deploying a configuration such that the db_index values are not unique across all applications, login issues may result.

Diagnosing the problem

Login succeeds using a static set of credentials if and only if one or more additional applications are not being used (either by an operator or a background service). If enabling verbose Taskmaster Server logging, a line similar to the following is reported in the Taskmaster Server log file:

Database index 156 is the same for 'C:\Datacap\Flex\FlexAdm.mdb' and 'C:\Datacap\APT\APTAdm.mdb'. Thread: 8dc

Solution:

Update the db_index value inside the offending application(s)' admin and engine databases. The values are stored inside the [adminfo] and [enginfo] respectively. It is recommended that you use a random 3-digit number that will be unique for the application; once set, the db_index column value inside the [admin] and [engine] databases for that single application should be identical.

Note: If batches were previously scanned then it is required to update the engine database's [queue] table such that the qu_admDB column is updated to reflect the new db_index value. Otherwise such previously scanned batches will not be visible in the Job Monitor.

 

 

InstallingTaskmaster Web controls in Datacap Manually

Taskmaster Web installs various controls for certain functionality such as interfacing with scanners. These controls are normally downloaded and installed automatically when accessing the website with proper browser settings and user permissions. However, there may be rare cases due to corporate security / user environment where manual installation may be desirable or required.

Steps to install components used for physical scanning:
1. Login to the end user's machine with an account that has rights to install and register files
2. Make \Datacap\tmweb.net\Task\twpro.cab from Taskmaster Web available on the end user's machine
3. Extract the contents of twpro.cab into a new folder
4. Copy all extracted files into %windir%\system32 and, if present (x64 OS), %windir%\SysWOW64
This is typically C:\Windows\system32 and C:\Windows\SysWOW64
5. Right-click and run Command Prompt with the "Run As Administrator" option if User Account Control (UAC) is enabled
6. Execute the following command, adjust paths as necessary:
C:\Windows\system32\regsvr32.exe C:\Windows\system32\TWNPRO3.dll

Steps to install general Taskmaster Web files:
1. Login to the end user's machine with an account that has rights to install and register files
2. Make \Datacap\tmweb.net\Task\dcim.cab from Taskmaster Web available on the end user's machine
3. Extract the contents of dcim.cab into a new folder
4. Copy all extracted files into %windir%\system32 and, if present (x64 OS), %windir%\SysWOW64
This is typically C:\Windows\system32 and C:\Windows\SysWOW64
5. Right-click and run Command Prompt with the "Run As Administrator" option if User Account Control (UAC) is enabled
6. Execute the following commands, adjust paths as necessary:
regsvr32 C:\Windows\system32\DcEdit.ocx
regsvr32 C:\Windows\system32\dcimage.ocx
regsvr32 C:\Windows\system32\dcthumbs.ocx

Cross Check
Ensure that all other prerequisites mentioned in the installation and configuration guide such as the ability to run ActiveX components are met before confirming resolution.

Using LDAP or ADSI with RV2 in Datacap

In addition to any configuration within Taskmaster Server Manager, RV2 has its own requirement when using ADSI or LDAP authentication.

Taskmaster Server Manager offers multiple authentication systems for login. When using ADSI or LDAP authentication, password authentication is not performed and login is based on membership within certain AD/LDAP groups and their inclusion within the Taskmaster Administrator's Groups tab.

Solution:

RV2 has an EnableLDAP setting specific for ADSI and LDAP authentication. If left to the default of false, then login to RV2 will require that the operator enter a non-blank password even though password authentication will not be performed. Any login attempt without a password specific will fail and the user ID will generally include the domain name, e.g. DOMAIN\username.

To set the EnableLDAP option:

1. Make sure no operators are using RV2 to avoid them having his or her session abruptly terminated during this time. This can be enforced at server side by stopping IIS or the application pool servicing RV2.


2. Login to the RV2 web server.


3. Backup \Datacap\RV2\web.config using copy and paste.


4. Edit web.config using Notepad.


5. Locate the following line:
   <add key="EnableLDAP" value="false"/>


6. Change "false" to "true":
   <add key="EnableLDAP" value="true"/>Save changes.

 

In Datacap Taskmaster web,After scanning Batch contains document structure

After scanning through Taskmaster Web, the corresponding scan page file contains a document node.

Solution:

To avoid a document structure from being created at time of scanning:
1. Locate the ICP or BPP file corresponding to the Taskmaster Web task
2. Backup the file and open the original using a text editor like Notepad
3. Browse to the [General] section and add a CreateDoc=0 setting:
[General]
CreateDoc=0
<other settings>
4. Save changes and scan a new batch
The newly created batch will not contain a document structure if steps are followed correctly.

 

How to enabling verbose Taskmaster Server logging in Datacap

By default the installed version of logging for Taskmaster Server is a lightweight version. This version is sufficient to log many errors, but does not offer full logging. For troubleshooting ADSI or LDAP authentication, or reviewing all low-level queries in depth given a particular problem, verbose Taskmaster Server logging may need to be enabled.

Enabling verbose logging requires a one-time step of replacing dclog.dll in the tmserver folder, which means that the server service must be stopped temporarily. Enabling, disabling or truncating the log can be done transparently.

Steps to Replacing DCLog.dll :

1. Stop and close all clients and background services
2. Backup \Datacap\tmserver\dclog.dll on Taskmaster Server
3. a) Stop the Datacap Taskmaster Server Service
b) Close the Taskmaster Server Manager
4. Replace \Datacap\tmserver\dclog.dll using a copy of \Datacap\dcshared\dclog.dll
Note: Do not move or rename the dcshared file
5. Start the Datacap Taskmaster Server Service

Steps to Enabling Taskmaster Server Logging:
1. Open Taskmaster Server Manager on Taskmaster Server
2. Go to Logging -> Datacap Log
3. Configure logging parameters:
a) Output to file = Enabled
b) Number of Messages = All or a sufficient level
c) File path and name = Normally a local disk with sufficient space
d) Reflash buffer = Normally disabled, enable if immediate log writes are required
e) Write to common buffer = Disabled
4. Click Save
5. Click Yes to immediately load settings

Steps to Disabling Taskmaster Server Logging:
1. Open Taskmaster Server Manager on Taskmaster Server
2. Go to Logging -> Datacap Log
3. Disable 'Output to file'
4. Click Save
5. Click Yes to immediately load settings
Steps to Truncating a Taskmaster Server Log:
1. Open Taskmaster Server Manager on Taskmaster Server
2. Go to Logging -> Datacap Log
3. Enable or disable and re-enable 'Overwrite existing log file'
4. Click Save
5. a) Click Yes to immediately load settings
b) Disable 'Overwrite existing log file' if desired, Save and click Yes

Note: Disk consumption should be closely monitored when logging is turned on, with full logging severity the log file can have a very rapid growth rate.

 

Datacap Taskmaster Application Manager is disabled

Datacap Taskmaster Application Manager is disabled

Taskmaster Application Manager can be opened but when selecting an application, all fields are disabled (greyed out) such that settings cannot be altered through the user interface.

Reason & Solution


This issue is typically caused by one of two items:

1. A restricted version of Taskmaster Application Manager is being used

2. The application file has been previously locked, e.g. by another user

To eliminate the first possibility, close Taskmaster Application Manager and run it only on a machine where Datacap Studio has been previously installed. Continue below if the issue is not resolved.

Close any known open instance of the Taskmaster Application Manager and re-test. Should the problem persist, browse to the application folder where the application file (*.app) resides and identify if there is a lock file (*.app.lock). Identify and close the instance of the Taskmaster Application Manager that created the lock file; if confident that the application is not locked elsewhere, backup all files within the folder, delete the lock file manually, and test again.

If all else fails, reboot the machine, test, and then contact IBM support if not successful.

 

How to make a Batch Pilot combo box list read only in IBM Datacap Taskmaster Capture

How to make a Batch Pilot combo box list read only in IBM Datacap Taskmaster Capture

Question

How to make a Batch Pilot combo box control drop down list read only.

Cause

By default, users may be able to type custom values into the control.

Answer

To make the control read only:

1. Open the form in Batch Pilot standalone and select the combo box.


2. Right-click and choose Properties.


3. Update Style to 2 - DropDownList.


4. Apply and save changes. Users will only be able to select a list option once accessing the updated form.

Using the Match Required and Locked properties can also provide similar behavior.

Action execution failed with SetPassword in IBM Datacap Taskmaster Capture

Action execution failed with SetPassword in IBM Datacap Taskmaster Capture

Abstract

When running NENU, it fails on the SetPassword action with the following error:


13:45:13.811 (93) t:12E8 p:35FEED8 Error (-2147352567=hex:80020009). In CCom::Call: Action execution failed: object [Datacap.Libraries.Nenu.Actions] method [SetPassword] [api source:]

Cause

There is no password defined in the SetPassword action. This most commonly occurs when setting up a NENU ruleset to connect using Windows (NTA) authentication, as NTA authentication does not use a password.

Resolving the problem

If no password is needed, remove the action completely. Do not leave it in the ruleset with a null parameter.

Action execution failed with SetPassword in IBM Datacap Taskmaster Capture

Action execution failed with SetPassword in IBM Datacap Taskmaster Capture

Abstract

When running NENU, it fails on the SetPassword action with the following error:

13:45:13.811 (93) t:12E8 p:35FEED8 Error (-2147352567=hex:80020009). In CCom::Call: Action execution failed: object [Datacap.Libraries.Nenu.Actions] method [SetPassword] [api source:]

Cause

There is no password defined in the SetPassword action. This most commonly occurs when setting up a NENU ruleset to connect using Windows (NTA) authentication, as NTA authentication does not use a password.

Resolving the problem

If no password is needed, remove the action completely. Do not leave it in the ruleset with a null parameter.

MClaims Application ICD-10 Compliance in IBM Datacap Taskmaster Capture

MClaims Application ICD-10 Compliance in IBM Datacap Taskmaster Capture

Abstract:

Is the MClaims application for IBM Datacap Taskmaster ICD-10 Compliant?

Answer

The MClaims application has support for ICD-10 built in to the code. However, revised forms are still being released by the regulatory agency, and so compliancy for any given form is dependent on it having been released long enough to be added to the MClaims application. Customers should test any form they use to confirm it meets ICD-10 compliancy standards.

SplitBatch only creates one child batch in IBM Datacap Taskmaster Capture

SplitBatch only creates one child batch in

IBM Datacap Taskmaster Capture

Abstract

When SplitBatch is run by Rulerunner Quattro, it only creates one child batch instead of the number of batches dictated by the SplitBatch rules. This problem does not occur if SplitBatch is run by Taskmaster Client.

Symptom

Batch priorities are also set incorrectly when SplitBatch is run by Rulerunner Quattro.

Cause

This has been identified as a product defect under APAR IO15741.

Environment

Datacap Taskmaster 8.0.1 Fix Pack 3

Resolving the problem

Download and install Interim Fix 8.0.1.3-Datacap-Taskmaster-WIN-TestFix-Quattro0228:0609577.

1. Go to the IBM Fix Central Identify Fixes page.


2. Select Individual Fix ID and enter:
   8.0.1.3-Datacap-Taskmaster-WIN-TestFix-Quattro0228:0609577


3. Select Continue and step through the remaining screens to download the fix.


4. Read the readme file for instructions and restrictions prior to installing.

 

Batch aborts running SetFieldLocateVariables with IBM Datacap Taskmaster Capture

Batch aborts running SetFieldLocateVariables

with IBM Datacap Taskmaster Capture

Abstract

When running a batch within a Flex application, the batch aborts on the SetFieldLocateVariables action

Symptom

The RRS log shows:

Error: ADODB.Recordset
Description: Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.
Error code: 0x800a0bcd - (null)Source: (null)
Line: 2418, Char: 9 [api source:]

Cause

The SetFieldLocateVariables action accesses the Flex database to get the field information for that Document Type (Fingerprint Class). If that information is missing or misconfigured, this error can occur.

Resolving the problem

Run FlexConfigurator.exe, located in the dco folder for the application, and then make sure that all fields for that Document Type are correctly defined.

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.

 

Batch aborts running CallPOLR with IBM Datacap Taskmaster Capture

Batch aborts running CallPOLR with IBM Datacap Taskmaster Capture

 Abstract

Running Batch Profiler in the APT application using Rulerunner Quattro, or any other application that uses POLR, aborts when attempting to run the CallPOLR action.

Symptom

The rrs log shows:

17:08:31.732 (0) t:B18 p:A929730 Error (0=hex:0). In CScript::Call(SAFEARRAY): Action execution failed: Script Error:
Error: (null)
Description: (null)
Error code: 0x80131509 - (null)Source: (null)
Line: 165, Char: 3 [api source:]
17:08:31.732 (0) t:B18 p:A929730 EXCEPTION: code="0" msg="Action execution failed: Script Error:
Error: (null)
Description: (null)
Error code: 0x80131509 - (null)Source: (null)
Line: 165, Char: 3" loc="CScript::Call(SAFEARRAY)" API=""

Cause

Taskmaster Client not installed on the Rulerunner Quattro server. POLR has a dependency on Taskmaster Client, even if run by Quattro.

Resolving the problem

Install Taskmaster Client on the Rulerunner Quattro server.

AutoDelete does not contain a 'suspended' batch status filter in IBM Datacap Taskmaster Capture

Auto Delete does not contain a 'suspended'

batch status filter in Datacap Taskmaster Capture

Abstract

AutoDelete does not contain a 'suspended' batch status filter in IBM Datacap Taskmaster Capture

Resolving the problem

The "suspended" status is normally not used, but batches can be set to the status using the rrunner library action SetTaskStatus or some equivalent. In AutoDelete there is no filter for the batch status; this limitation is removed in IBM Datacap Taskmaster Capture 8.0.0 and later through NENU, the replacement for AutoDelete.

In Taskmaster 7.6 and earlier, batches with the "suspended" status can be deleted manually through the Job Monitor. In IBM Datacap Taskmaster Capture Client the Job Monitor Filter menu has a SQL button where a customized filter can be inserted -- the value qu_status IN ('suspended') can be used to show only batch records with the suspended status. Similar functionality exists in Taskmaster Web with the Monitor's Filter button screen.

Stopping writes into the taskstats table by tmclient.exe and TMSub.exe in IBM Datacap Taskmaster Capture

Stopping writes into the taskstats table by tmclient.exe

and TMSub.exe in IBM Datacap Taskmaster Capture

Abstract

How to stop Taskmaster Client or Taskmaster Client Service from writing into the taskstats table in in IBM Datacap Taskmaster Capture

Answer

You can prevent Taskmaster Client and Taskmaster Client Service from writing into the engine database's [taskstats] table on a per task and per status basis. To do this:

1. Locate the Batch Pilot Project (BPP) file corresponding to the task for which you want to disable writing into the [taskstats] table.

2. Backup the BPP file and then open the original using Notepad or similar text editor.

3. Add section [TaskStats] if it does not already exist.

4. Under [TaskStats], add SkipTaskStatsOnStatus=x, where x is the status to avoid.

5. Repeat step #4 as many times as necessary and then save the BPP.

 

Here are the most common list of returned task statuses:

0 = Abort

1 = Canceled

2 = Finished

3 = Waiting

4 = Hold

5 = Suspended

8 = Pending

Here is an example of content from a BPP:

[TaskStats]

SkipTaskStatsOnStatus=8

 

Assuming that this was the BPP of a VScan task, Taskmaster Client and Taskmaster Client Service will avoid inserting data into the [taskstats] data when the task returns a "pending" status due to no files being found in the input folder for VScan. However, if the task returns "finished" because files are in the source directory, then a record will be inserted into the [taskstats] table by Taskmaster Client or Taskmaster Client Service.

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.