Error : FNP8_Upload failing when using IBM Datacap

When Exporting Documents to Filenet ,It is getting Fail


In the export.log file, the following errors were listed:

15:04:43.931 (313) t:1278 p:5E24A68 Upload failed.
15:04:43.931 (0) t:1278 p:5E24A68 ERROR!!! N-2146233088
Error description = Error executing the batch operation
....
15:04:43.932 (0) t:1278 p:5E24A68 Error (385875969=hex:17000001). In CIMainAlgorithm::execute4DCO: Aborting: Action [FNP8_Upload] requested abort [api source:]
15:04:43.932 (0) t:1278 p:5E24A68 EXCEPTION: code="385875969" msg="Aborting: Action [FNP8_Upload] requested abort" loc="CIMainAlgorithm::execute4DCO" API=""

Reason:

Upon further investigation, it was found that one of the property fields was a choice list. The export log showed that the property list was being set to "", which was not a valid selection according to the choice list definition on the customer's IBM P8 Content Engine (CE).

It was necessary to remove the blank field from the Datacap choice list and correct the spelling of all items in the Datacap choice list. The Datacap choice list and the CE choice list must be identical, since the CE is case sensitive when comparing choice list fields.

Diagnosing & Solution

Review the export.log and find all of the document properties that are being set by the function FNP8_SetProperty. Determine which ones are choice lists and what the return value is from the operator input. Verify that the spelling is identical to the CE property definition. Be aware that the spelling is case sensitive.

After the Datacap choice list content's spelling was corrected to match the CE choice list, the export operated correctly.

How to display validation errors for a Taskmaster Web start panel

While running validations in a start panel in Taskmaster Web, messages indicating invalid data - according to the application rules - may not be displayed. Additionally, an invalid field's background color may remain unchanged. This is a result of the field statuses not being updated.

Solution:

Call Status_Preserve_OFF from the rrunner library against the batch level node so that all start panel fields have their statuses updated upon failure of any respective field level rule. Field level MESSAGE variables will be used to indicate to the operator why any input data was incorrect, and such fields will be distinguished by a red background color. The action PilotMessage_Set from the rrunner library can be leveraged to compose custom validations failure messages.

Task setup error - Wrong number of arguments or invalid property assignment: SetProfileString in Datacap

When trying to save task settings in Taskmaster Client, the following error is displayed:

Wrong number of arguments or invalid property assignment: 'SetProfileString'

When trying to run the task, receive the error:
Type mismatch: 'Pilot.MsgLog'

Reason & Solution

This happens when the task module is configured to Batch Pilot DLL

To overcome this Change the task module's program name to Batch Pilot (BPilot.exe) and then re-test.

Rulesets library collection.xml isn't loaded error reported in Taskmaster Web

Taskmaster Web reports an error when running rules or validations, the error states "rulesets library (collection.xml) isn't loaded" similar to the following screenshot:

Reasons:

Cause of this error is when the [dco] table of the admin database has a dco_id value that is not identical to the corresponding workflow name.

Solution:

• Open the admin database and then the [dco] table. The value listed inside the dco_id column should be identical to the first part of the dco_setup, and also identical to the workflow name listed inside Taskmaster Application Manager. This name should also be specified inside the \Datacap\\dco_\rules\collection.xml files.

For example, Flex contains the following default values:dco_id = Flex
dco_setup = Flex@C:\Datacap\Flex\dco_Flex\Flex.xml
Taskmaster Application Manager:

collection.xml = <rsapp name="Flex">

• Make all values uniform across your configuration. Once finished, restart the Datacap Taskmaster Server Service to ensure that changes take effect and are not cached by Taskmaster Server. If all values specified are valid, then double-check file permissions for the application pool identity running Taskmaster Web, ensure that the error received is identical to that listed in the Symptom section of this Technote, and then engage IBM Support for further assistance as necessary.

Cannot get data from Application Service with Datacap

When attempting to run a task using Rulerunner, the task aborts. The quattro0.log shows:

Error: RunGrabbedQNRelease: Error preparing task. Cannot get data from Application Service. Key:[tasks/VScan:profile], attempt #[0]. Error from DCApp:[]

Reasons:

Rulerunner references configuration settings in the Quattro tab in Taskmaster Application Manager. If they are incorrect, this error will occur.

Solution:

To correct the configuration:

1. Run Taskmaster Application Manager.


2. Select the application on the left and click on the Quattro tab.


3. Locate the profile for the task that is failing.


4. Change the spelling of the Task and Task profile name to exactly match the name of the Task as shown in Datacap Studio. This name is case-sensitive. If there is no entry for the Task, then add it.


5. Exit Taskmaster Application Manager and restart Rulerunner.

Error starting client service in Taskmaster Client Service Manager - Cannot start service DCTMSub on computer

Reason:

This error message is commonly displayed if the account running the Datacap Taskmaster Client Service on the Rulerunner has insufficient permissions to the local machine, or if the service is disabled.

Solution:

Open the Services control panel from Administrative Tools:

1. If the service's start up mode is disabled, then change it to be automatic or manual.

2. Set the service account to a local administrator account that has sufficient permissions to network resources such as the batches directory and application rules files.

Note: Test after making required changes. If the problem persists, consider performing a repair or reinstall of the Taskmaster software using a local admin account.

Running a custom .NET Taskmaster action results in batch aborting with RRS log message "couldn't load needed object"

Signs:

Batch logging will state something similar to the following:

Error (385875972=hex:17000004). In CCom::Call: Couldn't load needed object: Datacap.Libraries.vScanSample.Actions into Datacap.Libraries. vScanSample.Actions instance [api source:]

Reason:

This issue can occur if the .NET action components are not installed properly.

Solution:

When using the vScanSample .NET template actions available from the IBM Datacap Taskmaster Capture 8.0.1 Publication Library, compiling the project will generate new files including interop DLL's, vScanSample.dll, vScanSample.tlb and vScanSample.pdb. Place vScanSample.dll into \Datacap\dcshared\NET and register it using regasm.exe and the /codebase flag:

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

Re-run the actions when finished to confirm the solution.Note: If the problem persists with a more customized project then unregister the main DLL and place it into a sub-folder along with all other compiled components (interops, main DLL and TLB file). Re-register vScanSample.dll using regasm.exe and the /codebase flag before reprocessing; the set of files specific to your project can be isolated afterward.

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.

No fingerprint/RulesDB connection Established error in Datacap

Cause

This error indicates that the software failed to connect to the Fingerprint/Rules Database. Typical causes are that the server which the Fingerprint/Rules Database resides on is disconnected from the network, the user attempting to access the database does not have sufficient permissions, or the database has been corrupted.

Solution:

If using an Access Database type for the Fingerprint/Rules Database, backup the database and then run a Compact and Repair on it to resolve the error.

When using Microsoft Access admin/engine databases in Datacap ,Applications are getting slow.

Clients such as Taskmaster Client and Taskmaster Web are slow in an environment containing one or more applications that have Microsoft Access admin and engine databases in IBM Datacap Taskmaster Capture

Latency may be apparent in client such as Taskmaster Client and Taskmaster Web when attempting to view the Job Monitor, Operations page, workflow, etc.

Reason:

Only Taskmaster Server communicates to the admin and engine databases. In cases where either database is large, communication may be slow, which may lead to other certain incoming requests (e.g. Job Monitor page, running a new batch) to become backed up. When using multiple applications, one application's databases may impact other applications if they share the same Taskmaster Server.

Solution:

Microsoft Access is not recommended in large scale environments, SQL Server or Oracle should be considered depending upon volume. However, even small volume systems using Microsoft Access may be affected over time if older batches and task statistics are not removed. Resolution steps A and B are recommended.

A) Decrease the size of the databases by removing or transferring any older unnecessary data. Deletion or transfer of database records is facilitated by NENU or AutoDelete, where NENU replaces AutoDelete in IBM Datacap Taskmaster Capture 8.0.0 and later. What data can or cannot be deleted or transferred will depend upon corporate policy and requirements:

1. Admin database - the [audit] table can be cleared if login and logoff records are not required.

2. Engine database - batches and task statistics can be removed based on a date range adequate for applicable retention policies.

i. Task statistics are contained in various tables such as [de2kst], [scan2kst], etc.

ii. Records for batches visible in the Job Monitor are stored in [queue], [qstats] and [tmbatch].

iii. The [debug] table will contain a record for each transaction that updates a batch status -- writing to debug is enabled on a

client basis and will quickly grow.
Note: if updating the engine database manually (e.g. external to NENU), it is generally recommended to keep the file system and database in sync in some manner.B) Compacting and repairing the Microsoft Access databases regularly during maintenance windows is recommended. It is feasible to automate compact and repair using some program or batch file. The databases should be compacted and repaired after using NENU or AutoDelete to clean up the databases.

 

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.

 

 

 

XML document must have a top level element error reported in Datacap

Description:

Message "Could not load application descriptionXML document must have a top level element" during rules execution or when running Setup on the task in Taskmaster Client:



Reason:

The workflow name is case and space sensitive and if the name is not synchronized in the environment then this message may result.

Solution:

Stop and close any open clients, including background services, before attempting resolution.

1. Open Taskmaster Application Manager and select your application

2. Place the cursor into the workflow name(s) and write down the name(s) exactly

3. Open your datacap.xml file using Notepad or any other text editor

- Exact path to datacap.xml is listed in the Service tab of Taskmaster Application Manager

4. Locate your application reference (there should only be one), ensure that the ref="path" is a valid relative or UNC path and write

down the 'app name' exactly as listed

5. Open the admin database's [dco] table and write down the values for the dco_id and dco_setup columns

Compare values retrieved from the admin database, datacap.xml file and the application file (Taskmaster Application Manager). The workflow name must be uniform across all entries, including case and space sensitivity. Update any values that require changes, save all modifications, and then open a new client to test and confirm resolution.

Note: It is recommended that to backup the database, datacap.xml file and application file (*.app inside the application folder) prior to any changes.

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.

 

 

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.

 

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.

 

Path1 cannot be NULL error received when calling the DeleteFingerprints Action

Abstract

When calling the Datacap DeleteFingerprints function, the following error is in the rss log:
System.ArgumentNullException: Value cannot be null. Parameter name: path1
at System.IO.Path.Combine(String path1, String path2)
at Datacap.Libraries.FingerprintMaintenance.Actions.DeleteFingerprint(String ID)

Signs

The application aborts when trying to delete fingerprint files and fingerprints from the fingerprint database. The fingerprint is deleted from the database, but the fingerprint files are not deleted from the fingerprint folder.

Reason & Solution


The path to the fingerprint folder does not exist.

To resolve this add the following call to the application:

SetFingerprintDir("@APPPATH(fingerprint)") --to set the path to the folder that contains the fingerprint files.

 

Rebuild button missing on Fixup window with IBM Datacap Taskmaster Capture

Rebuild button missing on Fixup window with IBM Datacap Taskmaster Capture

Abstract

When performing a Fixup operation, the Rebuild button is not visible.

Cause

Feature is not enabled in Task Settings.

Resolving the problem

To enable the Rebuild button:

1. In Taskmaster Client, select Settings, Workflow.


2. Expand the Fixup job, highlight the Fixup task, and select Setup.


3. Check Allow Assemble and click Done, Apply, Done.

 

Why is an error received when IBM Datacap Taskmaster Client Service VScan accesses a remote directory?

Why is an error received when IBM Datacap Taskmaster Client Service VScan accesses a remote directory?

Abstract

IBM Datacap Taskmaster Client Service reports 'Folder ... does not exist' on the VScan rule action SetSourceDirectory(), where the directory path is a remote shared directory.

Symptom

 

• Remote shared directory is specified using UNC path such as \\server\share.


• Remote directory does exist.


• Taskmaster Client (thick client) works (without reporting the error).


• Taskmaster Client Service Logon User is set to a user having full permission to read/write to the remote directory.


• Remote share is a Unix-hosted file system.


• vscan_rrs.log reports Error: Folder '\\server\share' does not exist.

Cause

The Logon ID format is not accepted by the remote host.

Environment

Windows 2008

Resolving the problem

Change the Taskmaster Client Service Windows service Logon ID from a "User1@Domain" format to a "Domain\User1" format. For example, use the format FINANCE\jdoe instead of jdoe@FINANCE.local.

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.

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.