Issue Description: When you are attempting to upgrade from 4.0.3.0 to 4.5.0.0, the mariaDB service is stuck and is in starting state forever.

This is a known issue and a hotfix is provided for this this problem.

Steps to deploy hotfix:
Steps for updating Ephesoft 4.0.3.0 to 4.5.0.0:

1.Download and Extract HotFix_VitalAire_EEN-18677_1.zip
2. Open my.ini file in notepad and update port= with database port number and datadir= with {EphesoftInstallationDirectory}/dependencies/mariadb/data
3. Stop Ephesoft Transact
4. Copy updated my.ini file inside directory {EphesoftInstallationDirectory}/dependencies/mariadb/data
5. Install/Upgrade Ephesoft 4.5.0.0

The post Known Issue: MariaDB breaks when upgrading from 4.0.3.0 to 4.5.0.0 appeared first on Ephesoft Docs.

Issue:
Ephesoft Transact v4.5.0.0 performs more slowly than Transact v4.1.2.0 when processing a small, 20-page PDF file using the Recostar SaveImage.exe files.

This is applicable only if you are using “Recostar” in Folder Import process. The slowness is observed only during PDF to TIFF conversion of folder import process.

Root Cause:
Ephesoft found that the duration of processing with the Recostar saveimage.exe files was five times longer than with the Transact v4.5.0.0 installation:

• The 20-page PDF file required 8 seconds of processing time on Transact v4.1.2.0.
• This same file required 32 seconds for processing on Transact v4.5.x.x.
• This issue also exists on Transact v4.5.0.1 and v4.5.0.2.

Solution: 

This issue is scheduled to be resolved in Ephesoft Transact v2019.1.

In the meantime, please use the following suggested workaround to address slower processing with the Recostar saveImage.exe files:

1. Copy the SaveImage.exe files located in the Ephesoft\Application\native\RecostarPlugin\bin directory of the Transact v4.1.2.0 installation.

You can also click this link to download the files: Recostar_v4120_files.zip

2. Copy and replace the files over to the Transact v4.5.0.0 installation, under the same directory.

3. Restart the Transact service.

These steps will improve the performance on the installation of Transact v4.5.0.0. This workaround can also be used for Transact v4.5.0.1 and v4.5.0.2.

The following snapshots illustrate the Recostar SaveImage files to be copied.

The post Transact v4.5.0.0 Performance is Slower than v4.1.2.0 when Using Recostar Saveimage appeared first on Ephesoft Docs.

Topic #24771 : How To Process Large Batches

Applicable Ephesoft versions: 4.5 onwards (previous versions may require slightly different settings)

Larger Batch Instances may require some additional configuration changes to process without timeouts.

Instructions:

1. Change process capacity
   • Larger batches should process fewer batches at the same time to avoid resources getting used up.
     • In the dcma-workflows.properties, you can change the server.instance.max.process.capacity.
2. Increase timeout times
   • Larger batches may take longer than the default Transact timeout time, causing Transact to restart batches prematurely
     • In the application.properties, you can adjust the wait times to stop these timeouts occurring.
       • # Wait time for GhostScript command in minutes
         gs.command.wait.time=30
         # Wait time for ImageMagik command in minutes
         imageMagik.command.wait.time=30
         # Wait time for Recostar command in minutes
         recostar.command.wait.time=30
         # Wait time for Tesseract command in minutes
         tesseract.command.wait.time=30
         # Wait time for LibTiff command in minutes
         lib_tiff.command.wait.time=30
     • In the dcma-workflows.properties, you can adjust the activity.restart.time
3. Alter the Advanced Barcode plugins
   • The Advanced Barcode plugins can take a longer time than other plugins.
     • In both the Reader and Extraction plugins, find the Barcode Methods and turn off as many as you’re not using.

 | Documentation Main Page | How To Articles | Downloads and Updates |

The post How To Process Large Batches appeared first on Ephesoft Docs.

Configuring and connecting to the MSSQL database over SSL connection

To configure the MSSQL database over SSL connection:

a. Stop the Ephesoft Transact server.

b. Download the jtds-1.3.1.zip file.

c. Extract jtds-1.3.1.zip into a temporary location.

• JavaAppServer Changes

d. Go to [Ephesoft_home]\JavaAppServer\lib\* directory.

e. Take backup of any existing jtds-*.jar before deleting the same.

f. Copy extracted jtds-1.3.1.jar to the lib folder.

g. Add below parameter in ‘Java Options’ inside Java tab after opening EphesoftEnterprise.exe (present inside [Ephesoft_home]\JavaAppServer\bin\) -Djsse.enableCBCProtection=false

• Application Changes

h. Go to [Ephesoft_home]\Application\WEB-INF\lib\* directory.

i. Take backup of any existing jtds-*.jar before deleting the same.

j. Copy extracted jtds-1.3.1.jar to lib folder.

• Server XML Changes

k. Take backup of server.xml located in [Ephesoft_home]\JavaAppServer\conf\ directory.

l. Update connection string (Append ssl=require as show below) :

jdbcUrl=”jdbc:jtds:sqlserver://localhost:1433;databaseName=ephesoft;sendStringParametersAsUnicode=true;prepareSQL=3;ssl=require;”

• Certificate Import

m. Import the certificate in java key store.

Note: Make sure that database is configured properly for encryption:

https://support.microsoft.com/en-in/help/316898/how-to-enable-ssl-encryption-for-an-instance-of-sql-server-by-using-microsoft-management-console

The post Connecting to MSSQL database over SSL connection appeared first on Ephesoft Docs.

Applies to: All Versions of Ephesoft Transact

Issue:

Ephesoft Transact does not have an out-of-the-box option to connect to a secure socket layer (SSL)-enabled database, but you have the option of manually configuring such settings.

Root Cause: n/a

Solution:

Add ssl=true in the Connection URL string to resolve this issue.

Perform the following steps to add this setting in SQL Account Authentication:

1. Open the Edit Connection dialog.

2. In the Connection URL field, add ;ssl=true, as illustrated below with two examples.

• The following example illustrates the connection URL for FuzzyDB:
  • jdbc:jtds:sqlserver://localhost:1433;databaseName=Health;ssl=true

• The following example illustrates this setting in the Server.xml file:
  • jdbc:jtds:sqlserver://localhost:1433;databaseName=ephesoft;sendStringParametersAsUnicode=true;prepareSQL=3;ssl=true

The post KB00024806: Issues connecting to an encrypted MS SQL database for APP or FuzzyDB connections appeared first on Ephesoft Docs.

Applies to: Ephesoft Transact v4.5.x.x

Topic/Category: Logging

Issue:

By default, the size of the Ephesoft Transact log file is set to 2MB. Also by default, the maximum number of archived files is set to archive only the last 20 log files per day.

In some cases, the user may wish to increase one or both of these settings. This article describes how to increase the maximum log file size and the maximum number of archived log files per day.

Root Cause: n/a

Solution:

Ephesoft defines the log file size and the number of log files to be generated in the log4j.xml file. This file is located in the Ephesoft\Application folder.

Within this file, you can reconfigure the SizeBasedTriggeringPolicy size property and DefaultRolloverStrategy max property for the number of files you want to generate per day.

Please note that after you change these settings in the log4j.xml file, you must restart the Ephesoft service.

Default Values:

The following snapshot illustrates these default values:

The following snapshot illustrates how the log file size and number of archive files to be generated has been modified (increased in both cases):

Note:

Please note that increasing the log file size will increase number of I/O operations that are required to read, write and append the logs. If you must increase one or both of these values, ensure that you use a higher number only when there are abundant system resources for such increased processing requirements.

The post KB00026123: Increasing log file size and archived log files appeared first on Ephesoft Docs.

Question

Why am I getting zero confidence when testing table extraction

Answer

Check if you are using Tesseract OCR plugin. Switching to Recostar appears to have resolved the problem

Our engineering is working with our vendor to get this addressed in future release

The post KB00027566: Table is extracted with zero confidence using Tesseract appeared first on Ephesoft Docs.

KB Article#: KB00026393

Topic/Category:  Auto save or Ctrl +E does not work in review module

Ephesoft version(s) affected: Ephesoft Transact 4.5.0.0 

Issue: After a user partially reviews a batch instance and then exits or closes the Review tab, the changes made or the work done does not get saved by the Auto-Save function or by pressing Ctrl+E.

Solution: Resolve this issue by updating to Ephesoft Transact 4.5.0.2.

The post KB00026393: Auto-Save or Ctrl +E does not work in Review module in Ephesoft Transact 4.5.0.0 appeared first on Ephesoft Docs.

KB Article #: KB00026054

Applicable Ephesoft Transact versions: 4.1.2.0, 4.1.3.0, 4.5.0.0, 4.5.0.1, 4.5.0.2

Instructions: Throughput Reports and Time Format

This document describes how to define the time format for reports in Ephesoft Transact to 12-hour or 24-hour method.

The following snapshots illustrate the 12-hour and 24-hour time formats for Throughput reports:

12-hour Time Format

24-hour Time Format

Changing the Time Format in Throughput Reports

Batch Size Throughput — Perform the following steps in Batch Instance Report Data to change the time format for the Batch Size Throughput.

Master Procedure — This is also the master procedure on which other procedures in this section are based.

1. Open the following file using Notepad or a similar text file editor:

{Ephesoft_Home}/EphesoftReports/_Definitions/_Reports/Throughput_Reports.Per_Batchsize.lgx

2. Find the following two XML tags with the ID : lblstart_time and lblend_time

3. Within these tags, the following property needs to be modified: Format

4. To make the time displayable in 24-hour format, replace the format values to yyyy/MM/dd HH:mm:ss in both the XML tags mentioned above, changing hh to HH or vice versa.

• • To use 12-hour format, use hh (lower case).
  • To use 24-hour format, use HH (upper case).

5. Refresh the browser session.

Batch Class Throughput

Perform the following steps in Batch Instance Report Data to change the time format for the Batch Class Throughput:

a. Open the following file using Notepad or a similar text file editor:

{Ephesoft_Home}/EphesoftReports/_Definitions/_Reports/Throughput_Reports.Per_Batchclass.lgx

b. Repeat steps 2 through 5 from the master procedure.

Week Day Throughput

Perform the following steps in Batch Instance Report Data to change the time format for the Week Day Throughput:

a. Open the following file using Notepad or a similar text file editor:

{Ephesoft_Home}/EphesoftReports/_Definitions/_Reports/Throughput_Reports.Per_Weekdays.lgx

b. Repeat steps 2 through 5 from the master procedure.

Hourly Throughput

Perform the following steps in Batch Instance Report Data to change the time format for the Hourly Throughput:

a. Open the following file using Notepad or a similar text file editor:

{Ephesoft_Home}/EphesoftReports/_Definitions/_Reports/Throughput_Reports.Per_Hourly.lgx

b. Repeat steps 2 through 5 from the master procedure.

Time-Based Throughput

Perform the following steps in Batch Instance Report Data to change the time format for the Time-Based Throughput:

a. Open the following file using Notepad or a similar text file editor:

{Ephesoft_Home}/EphesoftReports/_Definitions/_Reports/Throughput_Reports.Per_Weekly.lgx

b. Repeat steps 2 through 5 from the master procedure.

Monthly Based Throughput

Perform the following steps in Batch Instance Report Data to change the time format for the Monthly Based Throughput:

a. Open the following file using Notepad or a similar text file editor:

{Ephesoft_Home}/EphesoftReports/_Definitions/_Reports/Throughput_Reports.Per_Monthly.lgx

b. Repeat steps 2 through 5 from the master procedure.

Module Based Throughput

Perform the following steps in Batch Instance Report Data to change the time format for the Module Based Throughput:

a. Open the following file using Notepad or a similar text file editor:

{Ephesoft_Home}/EphesoftReports/_Definitions/_Reports/Throughput_Reports.Per_Module.lgx

b. Repeat steps 2 through 5 from the master procedure.

User Based Throughput 

Perform the following steps in Batch Instance Report Data to change the time format for the User Based Throughput:

a. Open the following file using Notepad or a similar text file editor:

{Ephesoft_Home}/EphesoftReports/_Definitions/_Reports/Throughput_Reports.Per_Module.lgx

b. Repeat steps 2 through 5 from the master procedure.

Dashboard Reports and Time Format

The following snapshots illustrate the 12-hour and 24-hour time formats for Dashboard reports:

12-hour Time Format

24-hour Time Format

Changing the Time Format in Dashboard Reports

Server and Services

Perform the following steps in to change the time format in the Server and Services in System Health:

1. Open the following file using Notepad or a similar text file editor:

• {Ephesoft_Home}/EphesoftReports/_Definitions/_Reports/Dashboard.serverStatus.lgx

2. Find the following all the XML tags with the following ID:

• lbllast_down_time

3. Within these tags, the following property needs to be modified:

• Format

4. To make the time displayable in 24-hour format, replace the format values to yyyy/MM/dd HH:mm:ss in the XML tag mentioned above, changing hh to HH or vice versa.

• To use 12-hour format, use hh (lower case).
• To use 24-hour format, use HH (upper case).

5. Refresh the browser session.

Sync for Dashboard and Throughput Reports

The following snapshots illustrate the 12-hour and 24-hour time formats for the Last Sync feature of Ephesoft reports:

12-hour Time Format

24-hour Time Format

Changing the Time Format for Last Sync

Perform the following steps to change the time format in the Last Sync feature of Dashboard and Throughput Reports:

1. Open the following file using Notepad or a similar text file editor:

{Ephesoft_Home}/EphesoftReports/_Definitions/_Reports/ sharedElements.lgx

2. Find the following two XML tags with the respective ID :

• • lastsyncTimeSharedElement
  • lastsyncTimeSharedElementForInit

3. Within these tags, the following property needs to be modified:

• • Format

4. To make the time displayable in 24 format, replace the format values to yyyy/MM/dd HH:mm:ss in both the XML tags mentioned above, changing hh to HH or vice versa.

• • To use 12-hour format, use hh (lower case).
  • To use 24-hour format, use HH (upper case).

5. Refresh the browser session.

The post KB00026054: How to Change to 12 or 24-hour Format in Reports appeared first on Ephesoft Docs.

KB Article: KB00027586

Applies to: All Ephesoft Transact versions

Issue: Transact does not have an out-of-the-box option to connect to a database that is enabled for Secure Socket Layer (SSL).

Root Cause: n/a

Solution:

You can configure connections for Ephesoft Transact or FuzzyDB to the MS SQL Server database.

Define these settings in the connection URL string.

Perform the following steps to add ssl=true in the connection URL string:

1. Add ssl=true to the string for MS SQL Server account authentication.

•  The following example illustrates this string for a FuzzyDB connection:

jdbc:jtds:sqlserver://localhost:1433;databaseName=Health;ssl=true

• The following example illustrates the connection string for the Server.xml file:

jdbc:jtds:sqlserver://localhost:1433;databaseName=ephesoft;sendStringParametersAsUnicode=true;prepareSQL=3;ssl=true

The post KB00027586: Setting Connection to an Encrypted MS SQL Database from App or FuzzyDB appeared first on Ephesoft Docs.

KB00027825 – Is there a way to disable HTTP after we have enabled SSL

Question: I have enabled SSL following this doc – https://ephesoft.com/docs/enable-ssl/. Is there a way that we can disable HTTP since we have HTTPS running successfully?

Answer: Certainly yes. There are a few steps required, which are listed below.

– Save the file

– Save the file

3. httpd.conf (<Ephesoft Installation Directory>\Apache24\conf)
– Look for the “Listen 80”, in this case, at line 60, comment it out by putting # in front of “Listen 80”, as shown below:
#Listen 80
– Look for the “ServerName”, in this case, at line 251, comment it out by putting # in front of the “ServerName localhost:80”, as shown below:
#ServerName localhost:80
– Save the file

Once you have completed these steps, restart both the Ephesoft Transact Service and the Ephesoft Web Service
You should now only be able to access the page using https, but not the http. Trying to access the page with http will give you the following error:

The post KB00027825 – Is there a way to disable HTTP after we have enabled SSL appeared first on Ephesoft Docs.

Process Execution Time-out Error

Issue: The following error occurs when trying to manually upload a supported file type:

“Failed to execute successfully due to: Process execution Time-out due to incorrect drop folder…”

Solution/explanation: It is a product bug due to incorrect definition of the Drop Folder path on the Batch Class Management screen of the Transact UI and will be resolved in future releases of Ephesoft Transact.

The solution is to define the correct Drop Folder path that is readable or accessible by Windows, for example, <Drive>:\WatchFolder.

The post Process Execution Time-out Error appeared first on Ephesoft Docs.

Issue:

When adding fields to the format conversion, the order that the rules are added is not the order that the rules are run. When you save the rules and come back, the true order of the rules will be shown. Before saving and reloading, the order of the fields displayed below isn’t the true order that the format is run.

After saving and reloading, the true order of the Format Options screen is shown below.

Solution:

No current workaround exists. A fix for this issue is in progress.

The post Known Issue: Format Options appeared first on Ephesoft Docs.

This article describes how to remove blank white pages from document files in all Ephesoft Transact versions. Blank pages can be removed from documents contained in batch instances when processing documents in the Ephesoft Transact workflow.

• This capability is not enabled by default with Ephesoft Transact, but is available with a basic script that reads the HOCR.xml file associated with blank pages. This file is located at the following path:

<SharedFolders>\ephesoft-system-folder\<batchInstance>\<batchInstance>_PG<x>_HOCR.xml

• To create a custom script for this purpose, the script must parse the HOCR.xml file and find the HocContent tags.
• If these HocContent tags in the HOCR.xml file are empty, this means there is no text extracted from the page. Therefore, any such page is a blank page and can be removed.

The post KB00027534: How to Create a Script to Remove Blank Pages appeared first on Ephesoft Docs.

Issue: The description of document index fields in Transact gets truncated.

Solution: To fix this issue, follow the steps below:

1. Navigate to <Ephesoft Installation Directory>/Ephesoft/Application/css.
2. Back up the existing ReviewValidate.css file.
3. Open this .css file with the root or equivalent account.
4. Search for existing .dlfViewLabel
5. Replace with following:
   .dlfViewLabel {
   text-overflow: ellipsis !important;
   white-space: nowrap !important;
   width: 1990px !important;
   overflow: hidden;
   }
6. Clear existing browser and the cache.
7. Restart the Ephesoft Transact service.

Note: The solution above is applied globally and will impact all index fields.

The post Known Issue: Index Field Description Length appeared first on Ephesoft Docs.

Issue: After initial installation of Ephesoft Transact, JXplorer does not start. The message “‘java’ is not recognized as an internal or external command” displays.

Ephesoft Transact Version(s) Affected: Any version of Ephesoft Transact on Windows 2016 server

Solution:

1. Navigate to the Java_Home variable.
2. Locate the following line:
   C:\\Ephesoft\\Dependencies\jdk\
3. Replace the backwards slashes \\ with a single backwards slash \.
4. Launch the JXplorer.

The post Known Issue: JXplorer appeared first on Ephesoft Docs.

Issue: JConsole will not connect to port 8900 in Ephesoft Transact 2019.2. The following error message displays:

Description:

For Ephesoft Transact versions before 2019.1, users configured dynamic logging by following the instructions in How to Configure the New Dynamic Logging Feature. With Ephesoft Transact 2019.2, JMX connections are completely disabled due to a security risk and reported vulnerability.

Solution:

Perform the following steps to dynamically change log-levels from local machine in Ephesoft Transact 2019.2:

1. Open the Task Manager by clicking Ctrl + Alt + Del.
2. Locate the processID (PID) for the Ephesoft Transact service (“EphesoftTransact”) in the Task Manager. In the example below, the PID is 1696.
   
3. Open the Command Prompt.
4. Browse to the following:

   C:\Ephesoft\Dependencies\jdk\bin

5. Enter the following command to open JConsole:

   jconsole processID

6. The JConsole connection is successful.
   

The post Known Issue: JConsole Connection Error in Ephesoft Transact 2019.2 appeared first on Ephesoft Docs.

In all versions of Ephesoft Transact 4.5.X.X and above, a new feature is added where a dialog box with a master subscription agreement (MSA), end user license agreement (EULA), and a United States Department of Defense (DoD) banner can be displayed to users before they could access the system management interface. The requirement for the banner is for websites with security and access controls.

The following steps describe how to configure Ephesoft Transact to display the required DoD banner when authentication is required for user access. To activate this feature, follow these steps:

1. Open the following file: \Ephesoft\Application\WEB-INF\classes\METAINF\notice.properties.
2. Change the value of notice_display=2. Refer to the following screenshot.
   

3. Save the file.
4. Restart Ephesoft Transact.
5. Log in to Ephesoft Transact. The DoD message displays as shown in the screenshot below:
   

Note: The displayed message can be modified. To modify locate the file locale.js at the following: \Ephesoft\Application\i18n\common directory.

The post How to Activate the DoD Banner Feature appeared first on Ephesoft Docs.

Issue:

The following message displays after starting Ephesoft Transact 2019.2. This issue is caused by multiple attempts of running database upgrade patches on Ephesoft Transact 2019.2.

The following is the error in logs:

2019.2 Windows Server 2012 R2 2019-10-02T23:48:36,934 ERROR main 
org.springframework.web.context.ContextLoader - Context initialization failed 
org.springframework.jdbc.IncorrectResultSetColumnCountException: Incorrect column count: 
expected 1, actual 2

Solution:

1. Log in to the Ephesoft Transact database.
2. Run the following query:

   Select * from cluster_property;

   The output of this query will display duplicate rows in this table as shown in the image below.
   

3. If there are duplicate entries in the cluster_property table, run the following query in the image below to remove the duplicated entries:
   Note: Delete the new entries from the table. Keep the old entries.
   

4. Ensure the final output of the table cluster_property is similar to the image below.
   
5. Restart the Ephesoft Transact service. The login page displays.
   

The post Known Issue: HTTP Status 404 – Not Found Error after Starting Ephesoft Transact 2019.2 appeared first on Ephesoft Docs.

Issue: In Ephesoft Transact 2019.2, a blank screen displays after logging in using SSO and selecting any administrator or operator option.

Solution:

1. Remove the security constraint .xml tags by commenting them out as shown in the following image.

2. When upgrading to Ephesoft Transact 2019.2 from previous versions, ensure the SSO configuration files are backed up if the environment is configured to use SSO. Once the upgrade is complete, verify the following SSO Configuration files are available:

• • Ephesoft\JavaAppServer\conf\server.xml
  • Ephesoft\Application\applicationContext.xml
  • Ephesoft\Application\WEB-INF\web.xml
  • Ephesoft\Application\WEB-INF\classes\META-INF\application.properties
  • Ephesoft\Application\WEB-INF\classes\META-INF\applicationContext-security.xml
  • Ephesoft\Application\WEB-INF\classes\META-INF\dcma-batch\dcma-batch.properties
  • Ephesoft\Application\WEB-INF\classes\META-INF\dcma-workflows\dcma-workflows.properties

3. Compare these files to the previous version.
4. Verify the SSO related information with the files in the upgraded version.

Important: Do not copy files from previous versions to the new version. This may cause failures to start the Ephesoft Transact service.

For more information about SSO, refer to the following articles:

1. Manually Configuring SAML 2.0 SSO for Ephesoft Transact 4.5.0.x and 2019.1
2. Ephesoft Transact Configuration with ADFS over SAML 2.0

The post Known Issue: Blank Screen Displays after SSO Login appeared first on Ephesoft Docs.