Issue:

In Ephesoft Transact, the batch instance status in the Batch Instance Management screen does not progress from New to Running. The batch instance status may also be stuck in Running where the folder import stage remains at 0%.

Solution:

To resolve this, perform the following steps to ensure the workflow of the batch class is deployed properly:

1. Stop the Ephesoft Transact service.
2. Browse to {Ephesoft Installation Directory}\WEB-INF\classes\META-INF\dcma-workflows\dcma-workflows.properties
3. Set the workflow.deploy parameter to true as shown in the following image:

4. Start the Ephesoft Transact service.

Note: This flag will change back to false on its own, and the service should start up.

5. Log in to Ephesoft Transact.
6. Verify if the batches are being processed.

The post KB00006858: Batch Stuck in New or Running Status in Batch Instance Management Screen appeared first on Ephesoft Docs.

Issue:

In Ephesoft Transact 2019.1 and 2019.2, an error occurs when importing an existing batch class with email configuration.

Solution:

1. Manually delete email configurations of the existing batch class.
2. Override the existing batch class with the new batch class.

The post Known Issue: Importing Existing Batch Class with Email Configuration Error appeared first on Ephesoft Docs.

Issue:

In Ephesoft Transact 4.5.X.X, 2019.1, and 2019.2, a batch error occurs while running the RECOSTAR_HOCR plugin. The error message says, “Uncaught Exception in readOCR method. Exception occurred while process PDF page for EText.”

This occurs when the batch class RECOSTAR_HOCR plugin parameter has Use EText Recostar Project File  set to Automatically. However, the same batch processes successfully when Use EText Recostar Project File is set to Never OR Use EText Recostar Project File is set to Always. The issue is caused by the third-party IText API.

Solution:

Ephesoft Support recommends upgrading the version of IText from 5.4.1 to 5.5.12.

1. Log in to the Customer Portal Downloads page

Note: A customer portal account will be required to access this page.

2. Locate and download the following hotfix: ITEXT 5.5.12 Library Upgrade.
3. Stop the Ephesoft Transact server.
4. Download and extract HOTFIX_EEN-24034_2019.1_ItextUpgrade_18Oct_2019.zip to a temporary location on your system.
5. Navigate to the following directory: [EPHESOFT_HOME]\Application\WEB-INF\lib\
6. Create a backup and delete the following:

• • itextpdf-5.4.1.jar
  • itext-pdfa-5.4.1.jar
  • itext-xtra-5.4.1.jar.

7. Copy the extracted files listed below to the following directory: [EPHESOFT_HOME]\Application\WEB-INF\lib\

• • itextpdf-5.5.12.jar
  • itext-pdfa-5.5.12.jar
  • itext-xtra-5.5.12.jar
  • commons-imaging-1.0-SNAPSHOT.jar

8. Start the Ephesoft Transact server.

The post KB00007045: Batch Error with RECOSTAR_HOCR Plugin appeared first on Ephesoft Docs.

Issue:

In Ephesoft Transact 2019.1, users are unable to change the batch instance priority on the Batch Instance Management page. When the field is edited, it turns red, and the following error message displays: “Value should not be empty. Priority should be between 1 and 100.”

Solution:

1. Log in to the Customer Portal Downloads page

Note: A customer portal account will be required to access this page.

2. Locate and download the following hotfix: Hotfix – Batch Priority Column Issue in BIM
3. Stop the Ephesoft Transact server.
4. Download and extract HOTFIX_EEN-24325_2019.1.zip to a temporary location on your system.
5. Navigate to the following directory: [EPHESOFT_HOME]\Application\WEB-INF\lib\HOT-FIXES
6. Copy the extracted *.jar to the following directory: [EPHESOFT_HOME]\Application\WEB-INF\lib\HOT-FIXES
7. Navigate to [EPHESOFT_HOME]\Application\
8. Create a backup of the existing batchInstance directory at a different location.
9. Delete the batchInstance folder under the following [EPHESOFT_HOME]\Application\.
10. Copy the extracted batchInstance directory to [EPHESOFT_HOME]\Application\
11. Start the Ephesoft Transact server.

Note: The solution is created over Ephesoft Transact 2019.1 generic hotfix. These changes are applied on all servers in the cluster.

The post Known Issue: Batch Instance Priority Error appeared first on Ephesoft Docs.

Issue:

Pre-request information is required in the Postman application for the Ephesoft UploadBatch web API.

Solution:

1. Open the Postman application.
2. In the POST field, enter a URL in the following format: http://<serverName/IP address>:<port>/dcma/rest/uploadBatch/<batchClassIdentifier>/<batchInstanceName>
   Figure 1 below uses the following URL as an example: http://192.168.0.144:8080/dcma/rest/uploadBatch/BC10/Test1

Figure 1: POST Field Entry

3. Select Basic Auth from the TYPE drop-down list.
4. Enter the following credentials:

• • Username: ephesoft
  • Password: demo

Figure 2: Authorization Options

5. Leave the fields in the Headers tab blank.

Figure 3: Headers Tab

6. In the Body tab, create the following two keys:
   a. Key 1 – File option: Ensure that you mapped where the TIF file is located:

Figure 4: Key 1

b. Key 2 – Test option: Ensure that you enter the correct DropFolder path according to your batch class Drop Folder path that has been defined in the Batch Class Management.

Figure 5: Key 2

Figure 6: Keys 1 and 2

7. Leave the fields in the Pre-request Script tab blank.

Figure 7: Pre-request Script Tab

8. Leave field in the Tests tab blank.

Figure 8: Tests Tab

9. Click Send.

Figure 9: Click Send

10. Verify that the Batch Instance is created successfully.

Figure 10: Batch Instance

The post KB00007089: Pre-request Information is Required in the Postman Application for the Ephesoft UploadBatch Web API appeared first on Ephesoft Docs.

Issue:

Ephesoft Transact does not extract Chinese characters from the PDF417 barcode format.

Ephesoft Transact Barcode Engines currently do not support Chinese characters; therefore, incorrect results are populated in Validation module. This is because Chinese is implemented at the OCRing level.

A feature request (TRAN-I-664) was submitted to support Chinese characters in the PDF417 barcode format.

Solution:

To resolve this issue, use other APIs that support Chinese characters from the PDF417 barcode format to populate the correct values in the Validation module.

The post KB00007088: Ephesoft Transact Does Not Extract Chinese Characters from the PDF417 Barcode Format appeared first on Ephesoft Docs.

Issue:

Users cannot uninstall Ephesoft Transact by using a normal user ID instead of a root account for Linux operating systems.

Solution:

It is not recommended to remove or uninstall Ephesoft Transact using a normal user ID. Ephesoft Support recommends using a root account to prevent permission issues such as removing and deleting Ephesoft’s files or folders during uninstalling activity for Linux.

The post KB00007087: Users Cannot Uninstall Ephesoft Transact with a Normal User ID appeared first on Ephesoft Docs.

Issue:

Users cannot log into Ephesoft Transact after integrating with Microsoft Active Directory authentication as shown below:

The following error is the INFO log file: java.net.UnknownHostException: DomainDnsZones.<domain name>.com. This occurs because the Ephesoft Transact server is running in work-group setup instead of joining or being a part of the domain setup.

Solution:

The Ephesoft Transact server is required to join or be a part of the domain.

The post KB7092: Login Failure Occurs after Integrating with Microsoft Active Directory Authentication appeared first on Ephesoft Docs.

Component: KV Page Process

Impact: High

Affected Version: Ephesoft Transact 4.5.0.1

Issue:

After upgrading from Ephesoft Transact 4.5.X.X to Ephesoft Transact 4.5.0.1, the page level fields in the Field Name column may get replaced with KV Page Process if there are KV_PAGE_PROCESS rules step up in the batch class. This impacts classification because of the changes in the field name.

Solution:

Perform the following steps in either workaround:

Workaround 1:

1. Install Ephesoft Transact 4.5.X.X or a current version.
2. Configure page level fields in the KV_PAGE_PROCESS plugin as necessary.
3. Upgrade to Ephesoft Transact 4.5.0.1 or a new version as applicable.
   Note: A hotfix is needed when the newer version is before Ephesoft Transact 4.5.0.2. This issue has been fixed in Ephesoft Transact 4.5.0.2 and newer versions.
4. Before starting the server, on the first time after upgrading, navigate to the following folder: <installation-directory>\Ephesoft\Application\WEB-INF\classes\META-INF\dcma-data-access
5. Replace the existing pre-schema.sql with the following:
   • pre-schema.sql for upgrades to 4.5.0.1
   • pre-schema_4500.sql for upgrades to 4.5.X.X (Note: Rename this file to pre-schema.sql before using)
     

Workaround 2:

1. Instead of replacing the files, edit the following file: <installation-directory>\Ephesoft\Application\WEB-INF\classes\META-INF\dcma-data-access\pre-schema.sql
2. Remove and comment the following query: update kv_page_process set page_level_field_name=(select plugin_config_value from batch_class_plugin_config where batch_class_plugin_config.id=kv_page_process.batch_class_plugin_config_id);”
3. Start the Ephesoft Transact server.

The post KB00022586: KV Page Process Error from Upgrade Issue from Ephesoft Transact 4.5.X.X to 4.5.0.1 appeared first on Ephesoft Docs.

Issue:

In Ephesoft Transact 2019.2, when customizing an export script to export all the metadata into a .csv file, the batch instance is stuck at the export’s cleanup stage. The following error displays: com.ephesoft.dcma.core.exception.ScriptNotFoundException: Failed to load DynaCode class [Ephesoft installed path]:\Ephesoft\SharedFolders\BC70\scripts\ScriptExport.java

This error occurs when the user is using a legacy version of POI jar file.

Solution:

1. Download the following latest POI file.
2. Unzip the zip file.
3. Copy the poi-4.1.1.jar and commons-math3-3.6.1.jar files into the lib folder.
4. If you do not have any customized built-in packages defined in the export script, skip this step and proceed to step 5.
   1. Open the export script with Eclipse, a third-party application.
   2. Temporarily comment out any customized built-in package to eliminate customized script issues.
5. Navigate to <Ephesoft installed path>:\Ephesoft\JavaAppServer\temp directory.
6. Empty this folder.

Note: Skip this step if a pop-up window displays with a message that the file is being used by Ephesoft Transact.

7. Restart Ephesoft Transact services.
8. Restart the problematic batch instance from the Batch Instance Management screen.

The post KB00007543: Batch Instance Stuck at Export Cleanup Stage appeared first on Ephesoft Docs.

Issue:

In Ephesoft Transact 2019.2, when mapping a certain index field to a database field in FuzzyDB Extraction Configuration, the following error message displays: Unable to Learn databases. An issue in learning occurs when the primary key column mapped in the document fuzzy is used in mapping fields and is marked as searchable.

Solution:

To fix this issue, perform the following:

1. Stop the Ephesoft Transact server.
2. Download this hotfix.
3. Extract this hotfix to a temporary location
4. Navigate to the following directory: [EPHESOFT_HOME]\Application\WEB-INF\lib\HOT-FIXES
5. Ensure there is no JAR named dcma-fuzzydb. If there is, take a backup and remove it from this directory.
6. Copy the extracted JAR dcma-fuzzydb_EEN-22768_30_July_2019.jar to the following directory: [EPHESOFT_HOME]\Application\WEB-INF\lib\HOT-FIXES
7. Start Ephesoft Transact server.
8. Test and verify if you can successfully perform the LearnDB task.

Note: This issue will be resolved in a future release.

The post Known Issue: Learn Databases Error in Ephesoft Transact 2019.2 appeared first on Ephesoft Docs.

Issue:

Users want to configure the Thai language for Tesseract in Ephesoft Transact 2019.2.

Solution:

1. Download the Thai Tesseract data.
2. Right-click the file and unblock the security option.
3. Unzip the file.
4. Navigate to the tessdata
5. Copy the traineddata file into the following folder: [Ephesoft installed path]:\Ephesoft\Application\native\Tesseract-OCR\tessdata

6. Open the batch class.
7. Navigate to the page process workflow.
8. Remove the Recostar HOCR and replace with Tesseract HOCR.
9. Turn on Tesseract HOCR.
10. From the Tesseract HOCR’s OCR language option, manually add the Thai language.

11. Click Apply and Deploy.
12. Click the View OCR to test with the sample images. View the results in the Validation module.

The post KB00007654: Configure the Thai language for Tesseract in Ephesoft Transact 2019.2 appeared first on Ephesoft Docs.

Issue:

Some PDFs cannot be extracted using EText mode. When EText is enabled in the batch class, Ephesoft Transact uses Recostar’s EText .rsp file to OCR any documents for extraction. EText mode will fail if the headers and labels inside the PDF are not editable or cannot be copied to notepad.

Solution:

1. Go to the FPR.rsp file
2. Find the xml tag that ends with </ImageSequence2Operator>
3. Add <LayoutOperator FindTextBlocks=”true” Name=”LayoutOperator”/> after the xml tag
4. Update the FRP_EText.rps by changing the ProcessingMode option from ExtractfromEText to VoteOCRAndEText.

The post KB00010300: EText Limitations appeared first on Ephesoft Docs.

Environment:

Ephesoft Transact 2019.1 on Windows with MSSQL database.

Issue:

There is an issue in Ephesoft Transact 2019.1 where the FINISHED batches in the Batch Instance Management screen do not get cleaned up using the CLEANUP job. The following error appears in the dcma-report-all.log

com.ephesoft.dcma.report.service.EtlServiceImpl – ess-sync_hist_manual_steps_in_workflow – An error occurred, processing will be stopped:

Couldn't execute SQL : MERGE hist_manual_steps_in_workflow AS TARGET

The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row. A MERGE statement cannot UPDATE/DELETE the same row of the target table multiple times. Refine the ON clause to ensure a target row matches at most one source row, or use the GROUP BY clause to group the source rows.

Solution:

A Hotfix has been deployed to resolve this issue. Download the hotfix and follow the steps below to deploy:

1. Stop the Ephesoft Transact Service.
2. Download and extract the HOTFIX_EEN-22958_2019.1_DB_MSSQL.zip to a temporary location.
3. Navigate to the <ephesoft_home>\Application\WEB-INF\classes\META-INF\dcma-reporting\Migration

    Note: Replace <ephesoft_home> with the location where the Ephesoft Transact service is located.

4. Backup the existing .ktr file and delete the original.
5. Copy the backup .ktr file to the <ephesoft_home>\Application\WEB-INF\classes\META-INF\dcma-reporting\Migration
6. Navigate to the <ephesoft_home>\Application\WEB-INF\classes\META-INF\dcma-reporting\Dashboard
7. Backup the existing .ktr file and delete the original.
8. Copy the extracted .ktr file to <ephesoft_home>\Application\WEB-INF\classes\META-INF\dcma-reporting\Dashboard
9. Start the Ephesoft Transact service.
10. Verify the batches in FINISHED state no longer appear on the Batch Instance Management You have successfully applied the hotfix.

The post KB00010399: Cleanup Issue for FINISHED Batches in 2019.1 appeared first on Ephesoft Docs.

KB00010723: Date Regex Expression Validation Error

Issue:

The error “Date could not satisfy the validation pattern” (Figure 1) may occur when a date regex expression has been defined in Validation Rules (Figure 2) but is already functioning in Regex Builder (Figure 3). This issue applies only to 2019.2.

Figure 1: Validation Pattern Error

Figure 2: Date Regex Expression in Validation Rules

Figure 3: Regex Builder Screen

Solution:

To resolve this issue, implement the following script to set the field value to lower case.

if (currentFieldName.equals("Document Date")){

dlfValueDoc.setText(currentFieldValue.toLowerCase());

This will verify the date format of manual user entry without using the Date regex expression in Validation Rules.

Important: You will need to click Validate twice.

The post KB00010723: Date Regex Expression Validation Error appeared first on Ephesoft Docs.

Issue:

In Ephesoft Transact 2019.1 or above, a large batch class fails to import in the Batch Class Management screen when your Ephesoft Transact environment is set up as the following:

• HAProxy server (Open source software that provides a high availability load balancer and proxy server for TCP and HTTP-based applications that spreads requests across multiple servers).
• Use Haproxy feature to redirect to Ephesoft Transact’s Apache 2.x port 443.
• Ephesoft Transact application server is integrating with the WSO2 server for Single Sign On Authentication.
• The WSO2 server is redirect to the Ephesoft Transact Apache2.x port 443 after Authentication activity.

This error occurs when the limitation of Apache’s body timeout for RequestReadTimeout is too short.

The following error displays in the DCMA-ALL INFO log:

2019.1 Windows Server 2012 R2 2020-01-27T20:52:10,206 ERROR ajp-nio-8009-exec-4 com.ephesoft.gxt.admin.server.ImportBatchClassUploadServlet - Unable to read the form contents.org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processing of multipart/form-data request failed. null

org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processing of multipart/form-data request failed. null

     at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:351) ~[commons-fileupload-1.3.3.jar:1.3.3]

     at org.apache.commons.fileupload.servlet.ServletFileUpload.parseRequest(ServletFileUpload.java:115) ~[commons-fileupload-1.3.3.jar:1.3.3]

     at com.ephesoft.gxt.admin.server.ImportBatchClassUploadServlet.attachFile(ImportBatchClassUploadServlet.java:86) [gxt-admin_EEN-20725_Generic_2019.1.jar:?]

Solution:

1. Navigate to the following folder: [Ephesoft Installed path]:\Ephesoft\Apache24\conf
2. Open the conf file in a code editor like Notepad++.

Note: Back up the original file before any changes.

3. Locate the following RequestReadTimeout variable for body header:
   RequestReadTimeout header=20-40,MinRate=500 body=20-40,MinRate=500
4. Edit the RequestReadTimeout variable to the following:
   RequestReadTimeout header=20-40,MinRate=500 body=20,MinRate=500
5. Restart Apache.

The post KB00010775: Batch Class Import Error appeared first on Ephesoft Docs.

KB00010248: Incorrect URL After Logging Out

Issue:

When logging out of Ephesoft Transact 2019.1, the page incorrectly directs to the Ephesoft Transact home page instead of the login screen.

Solution:

To resolve this issue, you will need to manually change the URL you want to be directed to upon logging out.

1. Navigate to \Ephesoft\Application\WEB-INF\classes\META-INF and open the applicationContext-security.xml
2. Locate the following line <property name=”defaultTargetUrl” value=”/home.html” />
3. Change the “defaultTargetUrl” value=”/home.html” to set the value to the page you want to be directed to upon logging out.

For example: “defaultTargetUrl” value=”http://localhost:8080/dcma/BatchClassManagement.html”

The post KB00010248: Incorrect URL After Logging Out appeared first on Ephesoft Docs.

How to Manually Install Microsoft’s TrueType Core Fonts

Affected Ephesoft Transact versions: 2020.1 or above

Affected operating systems: Linux

Ghostscript is no longer supported in Ephesoft Transact 2020.1 or above for Linux and has been replaced with Nuance features. Due to this change, Ephesoft Transact requires Microsoft’s TrueType Core (msttcore) fonts to be installed when converting PDF to TIFF files. These fonts were previously included within Ghostscript.

If you are installing Ephesoft Transact 2020.1 or above for the first time, you will need to manually install the msttcore fonts, which must be installed on every processing server of Ephesoft Transact.

Follow the steps below to manually install these fonts:

RHEL

1. Download the epel-release repository, which is required to download dependencies:

wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm

2. Install the downloaded epel-release repository:

rpm -i epel-release-latest-7.noarch.rpm

3. Install required packages that support msttcore font installation:

yum install cabextract wget xorg-x11-font-utils fontconfig

4. Download the msttcore fonts package:

wget https://downloads.sourceforge.net/project/mscorefonts2/rpms/msttcore-fonts-installer-2.6-1.noarch.rpm

5. Install the downloaded msttcore fonts package:

-rpm -i msttcore-fonts-installer-2.6-1.noarch.rpm

6. You have successfully installed Microsoft’s TrueType Core fonts

The post How to Manually Install Microsoft’s TrueType Core Fonts appeared first on Ephesoft Docs.

How to Update to a Previous Version of RHEL

Affected version: Ephesoft Transact 2020.1
Operating systems: Linux
Linux distributions: Red Hat Enterprise Linux (RHEL)

This article provides information on the two-part process of how to update your version of Red Hat Enterprise Linux to a supported previous release. Refer to Platform Configuration and Third-Party Integrations 2020.1 for more information on supported environments.

Note: Ephesoft Transact 2020.1 only supports RHEL 7.5 and 7.6.

Prerequisites

1. You must have a fresh server of RHEL.
2. You must be a root user.

Note: If you are not the root user, execute the following command:

sudo su root

Upgrade to Current Release

Perform these steps to upgrade to the latest version of RHEL. These instructions refer to RHEL 7.7 as the latest version.

1. Verify your Linux kernel version:

uname -r

Sample output for RHEL 7.3:

3.10.0-514.21.2.el7.x86_64

2. Update all packages with available updates:

yum update

3. Reboot the server to complete the upgrade:

reboot

Note: You will be logged out upon reboot. Log back in to continue.

4. Verify your updated Linux kernel version:

uname -r

Sample output for RHEL 7.7:

3.10.0-1062.9.1.el7x86_64

Downgrade to Supported Release

5. Downgrade to an earlier version of RHEL:

yum downgrade redhat-release

Note: This will downgrade by one release version of RHEL. For example, if your current distribution is RHEL 7.7, it will take you to RHEL 7.6.

6. Reboot the server to complete the downgrade:

reboot

Note: You will be logged out upon reboot. Log back in to continue.

7. Verify the updated Linux kernel version:

uname -r

Sample output for RHEL 7.6:

3.10.0-957.el7.86_64

Note: If your kernel downgrade fails when downgrading to RHEL 7.6, repeat steps 5-7 to downgrade again to RHEL 7.5.

8. Install the kernel version required to run RHEL 7.5 or 7.6:

yum install <kernel version>

Note: Check for the latest stable kernel version from Red Hat before upgrading. The following is an example command for RHEL 7.6:

yum install kernel-3.10.0-957.el7

9. Reboot the server to complete the download:

reboot

10. Verify your Linux version:

cat /etc/redhat-release

11. Verify your Linux kernel version:

uname -r

You have successfully updated your Linux distribution to a supported previous version.

The post How to Update to a Previous Version of RHEL appeared first on Ephesoft Docs.

The post Known Issue: Locked Batch Classes in Ephesoft Transact appeared first on Ephesoft Docs.