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.

Unable to connect to admin database with IBM Datacap Taskmaster Capture

Unable to connect to admin database with

IBM Datacap Taskmaster Capture

Abstract

When attempting to login using Taskmaster Web or another Datacap executable,

and error occurs stating that the user is unable to connect to the admin database.

Cause

The application is not correctly configured.

Resolving the problem

To resolve, do the following:

• 
  

  Ensure the application name is the same and each character is of the same case in all locations.

  
  
  
  
  • On the shared drive, usually the Taskmaster Server - \datacap\Datacap.xml, \datacap\appName\appName.app. Use a text editor to view these files.
  
  
  
  


• 
  

  Ensure \datacap\datacap.xml has the retry attribute <k name="tms" ip="127.0.0.1" port="2402" retry="3"/>.

  
  


• 
  

  On the web server check \datacap\tmweb.net\apps.ini.

  
  
  
  
  • In the following example, ensure the DateTimeSeparator is set to a pound symbol (#) for SQL or Oracle, and that Oracle=1 for Oracle. It should not include connection strings. Also ensure the application name is correct and each character has the correct case.
    [1040EZ]
    DateTimeSeparator=#
    Delay=20
    Retries=3
    BatchSelectionCustomFields=
    Debug=0
    Oracle=0
  
  
  
  


• 
  

  Ensure the Taskmaster Application Manager’s Service tab points to the shared \datacap.xml unless you are duplicating Datacap.xml and appName.xml locally on the web server.

  
  


• 
  

  If using Datacap.xml on a shared drive, ensure the user set as the identity of the Application Pool has permission to the share and to read the files.

  
  


• 
  

  Taskmaster Client and Quattro

  
  
  
  
  • Ensure the user set as the identity of the Application Pool has permission to the share and to read the files.
  
  
  
  


• 
  

  Taskmaster Server

  
  
  
  
  • The Windows user specified to run the Datacap Taskmaster Server Service is generally the only user that connects to the admin and engine databases. The clients read the connection strings from appName.app and pass them to Taskmaster Server.
  
  
  
  


• 
  

  If everything looks correct:

  
  
  
  
  • Create a Taskmaster Server log. Look for the connection string that was used. See if there are errors explaining why the connection failed. Test a thick client application on the Taskmaster Server machine using a local Administrator account.
  
  
  • Use the included demo applications e.g. APT, that use Microsoft Access databases to identify the problem as related to connecting to the admin and engine databases.
  
  
  • Applications such as APT store additional connection strings and file locations in the following files. These paths and connection strings will not be used for the admin, or engine databases when logging into a client. The best practice is to store connection strings and file locations using the Taskmaster Application Manager.
    
    
    
    • 
      

      \datacap\appName\dco_appName\paths.ini

      
      
    
    
    • 
      

      \datacap\appName\dco_appName\settings.ini

      
      
    
    
    
    
  
  
  
  

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.

IBM Datacap Taskmaster Capture RV2 Error 500.19

Abstract

When accessing the RV2 home logon aspx, after entering the user name and

password a 500.19 Internal Server Error is received.

Cause

Cannot read configuration file due to Process Model identity containing incorrect permission privileges.

Environment

IIS 7.0

Resolving the problem

To resolve this issue:

• 
  

  From the Windows Start menu, select Control Panel, select Administrative

  
  

           Tools,and select Internet Information Services Manager. The Internet

            InformationServices (IIS) Manager window opens.

• 
  

  In the Actions pane, select Set Application Pool Defaults. The Application Pool Defaults window opens.

  
  

• 
  

  Ensure the Process Model Identity is set to the Windows account which has

  
  

            Administrative privileges on this machine.

• 
  

  Click OK. The Internet Information Services (IIS) Manager window is displayed.

  
  

IO14818: ROMANIAN LANGUAGE ENABLED IN DSTUDIO FOR ICR/C, OCR/A AND OCR/S

IO14818: ROMANIAN LANGUAGE ENABLED

IN DSTUDIO FOR ICR/C, OCR/A AND OCR/S

Error description

• 
  

  ROMANIAN LANGUAGE ENABLED IN DSTUDIO FOR ICR/C, OCR/A AND OCR/S

  
  

Problem conclusion

• 
  

  fix included into FixPack2

  
  

IO14880: OUTLOOK.CONVERTTOIMAGEANDATTACHMENT EXCEPTION: THE SPECIFIED CONTENT TYPE IS INVALID

IO14880: OUTLOOK.CONVERTTOIMAGE AND

ATTACHMENT EXCEPTION: THE SPECIFIED

CONTENT TYPE IS INVALID

Error description

• 
  

  Outlook.ConvertToImageAndAttachment exception: The specified

  
  

content type is invalid

Problem conclusion

• 
  

  fix included into FixPack2