{"id":31767,"date":"2018-09-26T16:32:28","date_gmt":"2018-09-27T00:32:28","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/2019-1-2\/release-notes-2019-1\/transact-2019-1-workarounds\/"},"modified":"2020-05-19T12:25:32","modified_gmt":"2020-05-19T19:25:32","slug":"transact-2019-2-workarounds","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/","title":{"rendered":"Ephesoft Transact 2019.2 Known Issues & Workarounds"},"content":{"rendered":"

 <\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Category<\/th>\nIssue<\/th>\nWorkaround<\/th>\n<\/tr>\n<\/thead>\n
Installation and Upgrade:<\/p>\n

Windows<\/td>\n

After upgrading from Ephesoft Transact 2019.1 to version 2019.2 on a Windows system, the Windows Service account for Ephesoft Transact reverts back to the Local System<\/strong> account, and not to the Transact Windows Service<\/strong>.<\/td>\nThe workaround for this issue is to run the Upgrade Wizard for Ephesoft Transact 2019.2, then manually add again the Transact Windows Service on this Windows system.<\/p>\n

For additional information, refer to the following documents:<\/p>\n

Upgrading to Ephesoft Transact 2019.2 on Windows<\/a><\/p>\n

Installing Ephesoft Transact as a Windows Service<\/a><\/td>\n<\/tr>\n

Installation and Upgrade:
\nWindows, Silent<\/td>\n
The Windows Silent Install Wizard fails to configure logon information for the Ephesoft Transact service.<\/td>\nThis issue is observed after installation. Windows displays the following error message:<\/p>\n
\"\"
Services logon error message<\/figcaption><\/figure>\n

To resolve this issue, edit the Logon<\/strong> field manually from the Services console.<\/p>\n

The user should avoid using symbols such as %<\/strong> (percent) in the logon password.<\/td>\n<\/tr>\n

Installation and Upgrade:<\/p>\n

CentOS<\/td>\n

When installing Ephesoft Transact on a CentOS system with IP tables (iptables<\/strong>) configured as part of the firewall rules, the installer incorrectly changes the IP tables. This issue pertains to the following versions:<\/p>\n

Ephesoft Transact 4.5<\/p>\n

Ephesoft Transact 2019.1<\/p>\n

Ephesoft Transact 2019.2<\/td>\n

This issue will be resolved with an upcoming software release.<\/p>\n

To resolve this issue in Ephesoft Transact 4.5, 2019.1 or 2019.2, perform these steps:<\/p>\n

1. Determine if the \/etc\/sysconfig\/iptables<\/strong> file exists.<\/p>\n

2. If this file exists, edit the file to move the following rule in it above any REJECT rule:<\/p>\n

-A INPUT -m state –state NEW -m tcp -p tcp –dport 8080 -j ACCEPT <\/strong><\/p>\n

3. Run the following command:<\/p>\n

sudo iptables -L<\/strong><\/p>\n

4. Check to verify if the following rule is defined after a REJECT rule:<\/p>\n

ACCEPT tcp \u2013 anywhere anywhere state NEW tcp dpt:http-alt <\/strong><\/p>\n

5. If this is the case, perform the following additional steps.<\/p>\n

a. Run the following command:<\/p>\n

sudo iptables -L –line-numbers<\/strong><\/p>\n

b. Check the number in front of the following rule:<\/p>\n

ACCEPT tcp \u2013 anywhere anywhere state NEW tcp dpt:http-alt<\/strong><\/p>\n

c. Run the following command, where the <number found in above step> is the number shown after performing step 5b:<\/p>\n

sudo iptables -D INPUT <number found in above step><\/strong><\/p>\n

for example, sudo iptables -D INPUT 5<\/strong><\/p>\n

d. Run the following command:<\/p>\n

sudo iptables -I INPUT -m state –state NEW -m tcp -p tcp –dport 8080 -j ACCEPT<\/strong><\/p>\n

e. Run the following commands:<\/p>\n

sudo service iptables save<\/strong><\/p>\n

sudo service iptables restart<\/strong><\/td>\n<\/tr>\n

Installation and Upgrade:<\/p>\n

SAML SSO Configuration During Upgrade (Infor)<\/td>\n

The SAML-SSO bean entry is not updated when upgrading to Ephesoft Transact 2019.2.<\/td>\nResolve this issue by performing the following steps:<\/p>\n

1. Back up the original applicationContext-security.xml file (<Ephesoft Installation Directory>\\Application\\WEB-INF\\classes\\META-INF) before performing the upgrade from previous version of Ephesoft Transact.<\/p>\n

2. Complete the upgrade to Ephesoft Transact 2019.2.<\/p>\n

3. After the upgrade is complete, manually add the metadata bean entry from the original applicationContext-security.xml <\/strong>file into the current applicationContext-security.xml<\/strong> file.<\/p>\n

4. Restart the Ephesoft Transact server.<\/td>\n<\/tr>\n

Installation and Upgrade:<\/p>\n

Server Startup Failure after Upgrade (Infor)<\/td>\n

The Ephesoft Transact server fails startup after upgrading to version 2019.2. Note that this issue occurs specifically with the Infor Auto_SSO_9 installer.<\/td>\nPrevent this issue by performing the following steps:<\/p>\n

1. After installing any earlier version of Transact, uncomment the line for configuring HTTPS in the server.xml file (<Ephesoft Installation Directory>\\JavaAppServer\\conf) as shown below.<\/p>\n

<Connector port=”8443″ protocol=”org.apache.coyote.http11.Http11Protocol” maxThreads=”150″ SSLEnabled=”true” scheme=”https” secure=”true” keystoreFile=”C:\\Ephesoft\\servercert.jks” keystorePass=”xxxxxxx” clientAuth=”false” sslProtocol=”TLS” maxPostSize=”4194304″ \/><\/p>\n

2. Perform the upgrade to Ephesoft Transact 2019.2 using the 2019_2_Infor_Auto-SSO_9 installer. During this step, you will observe that the server startup fails.<\/p>\n

3. Manually change the protocol attribute value in the server.xml file to org.apache.coyote.http11.Http11NioProtocol<\/strong>.<\/p>\n

As a result, the Connector appears as follows:<\/p>\n

<Connector port=”8443″ protocol=”org.apache.coyote.http11.Http11NioProtocol” maxThreads=”150″ SSLEnabled=”true” scheme=”https” secure=”true” keystoreFile=”C:\\Ephesoft\\servercert.jks” keystorePass=”xxxxxxx” clientAuth=”false” sslProtocol=”TLS” maxPostSize=”4194304″ \/><\/p>\n

4. Start the Ephesoft Transact server.<\/td>\n<\/tr>\n

Installation and Upgrade:<\/p>\n

LibreOffice<\/td>\n

After installing Ephesoft Transact 2019.2, the Transact server fails at start-up due to soffice.bin application error.<\/td>\nThe issue occurs as some LibreOffice files are not being copied by the installer during installation. To fix this problem, download\u00a0libreoffice.zip<\/a>\u00a0file, unzip and place the folder in the Ephesoft Transact installation directory.<\/td>\n<\/tr>\n
Batch Class Management<\/td>\nAfter a few days of heavy document processing, the Ephesoft Transact Pickup service stops picking up batches.<\/td>\nTo resolve this issue, perform the following steps:<\/p>\n

1. Disable JNotify on all servers. Adjust the following setting to be as shown:<\/p>\n

foldermonitor.jnotify_switch=false <\/strong><\/p>\n

2. Enable INFO-<\/strong>level logging on all the servers.<\/p>\n

3. Restart the entire cluster.<\/td>\n<\/tr>\n

Batch Instance Management<\/td>\nWhen the Session Expiration<\/strong> dialog appears during batch class operations, the dialog is locked in the background. As a result, the user cannot click Continue<\/strong> and the work may be lost.<\/td>\nThere are two workarounds for this issue, as follows:<\/p>\n

1. For environments that typically have large processing tasks, the Administrator can increase the screen timeout period. Additional information about adjusting the timeout period is available in the following document:<\/p>\n

Session Timeout<\/a><\/p>\n

2. When the issue occurs, open another browser tab and open any Transact screen (such as the Batch Instance Management<\/strong> screen). This approach ensures that the session continues. The Session Expiration<\/strong> popup dialog on the initial screen will also disappear.<\/td>\n<\/tr>\n

Review-Validate<\/td>\nIf two document types share the same Index Field <\/strong>property name (name and description), and the Sticky Index Field Switch<\/strong> is enabled (set to ON<\/strong>), then when the user changes document type, the index values for the previous document type persist with the new document type.<\/td>\nThe workaround for this issue, when using the Sticky Index Field Switch under the VALIDATE_DOCUMENT plugin, is to create index fields for each document type to have a different name and description.<\/td>\n<\/tr>\n
Review-Validate:<\/p>\n

Keyboard Shortcuts<\/td>\n

When performing validation in a batch instance that contains two or more documents with tables, the screen may freeze when using the Ctrl + Shift + M keyboard shortcut to change from the current document\u2019s table view to the previous document\u2019s table view.<\/td>\nTo prevent this issue from occurring, when there are two or more documents with tables in the batch instance, use the Field View <\/strong>and Table View<\/strong> buttons on the Validation<\/strong> screen to display the table view for any document.<\/td>\n<\/tr>\n
Review-Validate:<\/p>\n

Zoom Overlay<\/td>\n

When enabling or disabling the Zoom Overlay feature in the Review-Validate screen, alternating between the shortcut of Ctrl + Shift + X and the Image icon does not function as expected.<\/td>\nThe workaround for this issue is to use only one method to enable and disable the Zoom Overlay feature. Either use the image icon, or the Ctrl + Shift + X <\/strong>keyboard shortcut, but not a combination of the two.<\/td>\n<\/tr>\n
Review-Validate:<\/p>\n

Zoom Overlay<\/td>\n

The image icon does not function properly for Zoom Overlay, such as zoom in or out, pop-out, fit-to-size, or rotate.<\/td>\nTo avoid this issue, use keyboard shortcuts to make use of other functionalities with Zoom Overlay feature.<\/td>\n<\/tr>\n
Review-Validate:<\/p>\n

Zoom Overlay<\/td>\n

An overlay appears on an expanded, \u201cpopped-out\u201d image if Zoom Overlay is enabled.<\/td>\nThe workaround for this issue is to disable Zoom Overlay, then directly click on a pop-out image icon. With this approach, the overlay does not appear on the image.<\/td>\n<\/tr>\n
Review-Validate:<\/p>\n

Fuzzy DB<\/td>\n

On the Validation screen, when attempting to search using the Fuzzy Search feature, the Cancel<\/strong> button does not operate in the FuzzyDB<\/strong> pop-up dialog.<\/td>\nAs a workaround, instead of using the Close<\/strong> button, click the X<\/strong> icon at the top of the browser window to close the pop-up dialog.<\/td>\n<\/tr>\n
Plugins:<\/p>\n

Cloud HyperExtender<\/td>\n

“All Validated Documents” option of the Expedite Export feature does not work correctly with the Cloud HyperExtender plugin leaving some of the validated documents un-exported in the batch and requiring manual validation.<\/td>\nThe resolution for this issue is to export each document type in the batch instance individually. Perform these steps:<\/p>\n

1. Process the batch instance and prepare for export.<\/p>\n

2. When exporting the batch instance, export only one document type at a time. The All Validated Documents<\/strong> button operates in this method.<\/td>\n<\/tr>\n

Plugins:<\/p>\n

Cloud HyperExtender<\/td>\n

When a batch class uses the Ephesoft Cloud HyperExtender plugin, batch instances experience an error if configured to perform image classification.<\/td>\nThe resolution to this issue is to configure the CREATE_THUMBNAILS plugin as follows:<\/p>\n

1. Log in to Ephesoft Transact as Administrator, and go to the Batch Class Management<\/strong> screen.<\/p>\n

2. Open the batch class that contains the issue, which has the Ephesoft Cloud HyperExtender plugin configured.<\/p>\n

3. Open the Page Process module. Configure and position the CREATE_THUMBNAILS plugin to be before the CLASSIFY_IMAGES plugin.<\/p>\n

4. Save and deploy the changes to restart the batch. Batch instances should now perform image classification without error.<\/td>\n<\/tr>\n

Plugins:<\/p>\n

CREATEMULTIPAGE_FILES<\/td>\n

When importing batch classes from older versions of Transact to Transact 2019.2, the PDF Optimization Parameters in the CREATEMULTIPAGE_FILES plugin get changed and batch export fails.<\/td>\nTo resolve the issue, make sure to change the first word of the PDF Optimization Parameters to: -dQUIET<\/em><\/p>\n
\"\"
CREATEMULTIPAGE_FILES plugin configuration prior to version 2019.2<\/figcaption><\/figure>\n

 <\/td>\n<\/tr>\n

Web Scanner:<\/p>\n

Image Conversion<\/td>\n

The GraphicsMagick component in Ephesoft Transact is not able to rotate images on the server side. The issue is caused by a non-standard installation location for GraphicsMagick.<\/td>\nThe workaround for this issue resolves a non-standard installation location for GraphicsMagick 1.3.22.<\/p>\n

By default, Ephesoft Transact installs GraphicsMagick 1.3.22 in the following location:<\/p>\n

\/usr\/local\/bin<\/p>\n

If GraphicsMagick 1.3.2.2 or another version has been installed in an alternate location, the administrator must create a soft link to the alternate location.<\/p>\n

Use the following command to create a soft link to a non-standard location for GhostMagick.<\/p>\n

ln -s \/usr\/bin\/gm \/usr\/local\/bin\/gm<\/strong><\/p>\n

In this command example:<\/p>\n

\/usr\/bin\/gm<\/strong> \u2014 This is the non-standard location for GhostMagick, as an example. Your location may differ.<\/p>\n

\/usr\/local\/bin\/gm<\/strong> \u2014 This is the default GhostMagick location in a standard installation of Ephesoft Transact.<\/td>\n<\/tr>\n

EText:<\/p>\n

ZIP files<\/td>\n

An exception error may occur while processing zip files with EText feature.<\/td>\nThe issue is observed if the input files are first placed in a folder and then zipped.<\/p>\n

To avoid EText processing errors, zip the files directly, without placing them in the folder before compression.<\/p>\n

Alternatively, the files\/folder can be unzipped before processing.<\/td>\n<\/tr>\n

LIM:<\/p>\n

Table views on Oracle<\/td>\n

LIM query results generate a mis-formatted table view.<\/td>\nWhen using query with Line Item Matching (LIM), the table view returns mis-formatted results. This issue occurs only with the Oracle database.<\/p>\n

If the user experiences corrupted table views on Oracle, contact Ephesoft Support, who will provide information about the schemaname.tablename for the PO-TABLE.<\/td>\n<\/tr>\n

Custom Export:<\/p>\n

Ubuntu 16.04 with Ghostscript<\/td>\n

The Custom Export plugin creates a Ghostscript error on Linux Ubuntu 16.04.<\/td>\nThis issue is observed if the higher version of Ghostscript has been installed on the server than supported by Ephesoft Transact.<\/p>\n

To resolve this, the Ghostscript needs to be downgraded to version 9.25 which comes bundled with the Transact installer by default. The workaround steps are described below.<\/p>\n

1. Remove Ghostscript:<\/p>\n

apt-get remove -y ghostscript<\/strong><\/p>\n

2. Install the supported Ghostscript version by performing the following steps:<\/p>\n

Download Ghostscript version 9.25 Q8 (it is recommended to use the Ephesoft_2019.2.tar.gz, navigate to the Ephesoft\/Dependencies folder and search ghostscript.tar.gz)<\/p>\n

Extract the tar file with the following commands:<\/p>\n

Tar -xvzf ghostscript.tar.gz<\/strong><\/p>\n

Go to Ghostscript extracted folder:<\/p>\n

cd ghostscript-9.25<\/strong><\/p>\n

Run the .\/configure <\/strong>command<\/p>\n

<\/p>\n

Run the following command:<\/p>\n

make -s<\/strong><\/p>\n

<\/p>\n

Run the following command:<\/p>\n

checkinstall -y<\/strong><\/p>\n

<\/p>\n

Run the following command:<\/p>\n

checkinstall -R -y -install –exclude=\/selinux,\/selinux\/context<\/strong><\/p>\n

<\/p>\n

Run the following command:<\/p>\n

ldconfig \/usr\/local\/bin<\/strong><\/p>\n

<\/p>\n

Verify the path and version of Ghostscript. Use the following commands:<\/p>\n

which gs<\/strong><\/p>\n

gs -version<\/strong><\/p>\n

<\/p>\n

If needed, additional information about when a user may experience this issue is available from Ephesoft Support.<\/td>\n<\/tr>\n

Expedite Export<\/td>\nWhen moving a validated part of the batch forward in the processing workflow using the Expedite Export functionality, the validated part does split from the original batch, however fails to export as configured.<\/td>\nThis issue is observed only for searchable PDF when using IText-Searchable tool. To resolve this problem, Recostar tool can be used to generate searchable PDF.<\/td>\n<\/tr>\n
JExplorer on Windows<\/td>\nLaunching the JExplorer.bat file does not bring up JExplorer.<\/td>\nEnsure that java path is correct in the Environment Variables. For that:<\/p>\n

– On the Control Panel, select System<\/strong><\/p>\n

– On the System<\/strong> screen, click Advanced system settings<\/strong><\/p>\n

– Select Environment Variables\u2026<\/strong><\/p>\n

– Edit the JAVA_HOME variable value to show the correct path (<Ephesoft Installation Directory>\\\\Dependencies\\\\jdk\\\\)<\/p>\n

– Check that there is the %JAVA_HOME%\\bin path under the System variables<\/strong>:<\/p>\n

\"\"
Environment Variables screen<\/figcaption><\/figure>\n

– Check the java version by opening Command Prompt and running the following command: java -version<\/strong><\/td>\n<\/tr>\n

Format Conversion<\/td>\nDate format conversion is not working when the values are entered in capital letters.<\/td>\nTo resolve this issue, enter the values in the lower-case letters, for example, mm\/dd\/yyyy.<\/td>\n<\/tr>\n
JAVA<\/td>\nThe tool used to read fuzzy index to debug issues is not opening (<Ephesoft Installation Directory>\\Dependencies\\luke.bat).<\/td>\nThis problem can be observed when the JAVA_HOME environment variable is not set correctly after installation. To fix the issue, reboot the machine and check if the JAVA_HOME variable is set correctly by launching the Admin Command Prompt and typing java -version. This should give you the java version. Now, you can run the luke.bat file (<Ephesoft Installation Directory>\\Dependencies\\luke.bat) and access the tool UI.<\/td>\n<\/tr>\n
Web Services<\/td>\nThe error is returned when trying to use ocrClassifyExtracV2 and OcrClassifyExtractBase64V2 web services for machine learning based extraction.<\/td>\nWhen configuring the batch class, use SearchClassification or MultiDimensionalClassification method instead of the default OneDocumentClassification in the DOCUMENT_ASSEMBLER plugin.<\/td>\n<\/tr>\n
Other<\/td>\nWhen trying to stop the Ephesoft Transact service, it hangs.<\/td>\nTo stop the Transact service, open the Windows Task Manager and end the \u201ctomcat9\u201d task manually.<\/td>\n<\/tr>\n
FuzzyDB Extraction Configuration<\/td>\nWhen mapping a certain index field to a database field, 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.<\/td>\nTo resolve this issue, deploy the hotfix provided in this article<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":0,"parent":31761,"menu_order":4,"comment_status":"closed","ping_status":"open","template":"","doc_tag":[],"yoast_head":"\nEphesoft Transact 2019.2 Known Issues & Workarounds | Ephesoft Docs<\/title>\n<meta name=\"robots\" content=\"noindex, follow\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Ephesoft Transact 2019.2 Known Issues & Workarounds\" \/>\n<meta property=\"og:description\" content=\"  Category Issue Workaround Installation and Upgrade: Windows After upgrading from Ephesoft Transact 2019.1 to version 2019.2 on a Windows […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/\" \/>\n<meta property=\"og:site_name\" content=\"Ephesoft Docs\" \/>\n<meta property=\"article:modified_time\" content=\"2020-05-19T19:25:32+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/06\/word-image-175.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"12 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/\",\"url\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/\",\"name\":\"Ephesoft Transact 2019.2 Known Issues & Workarounds | Ephesoft Docs\",\"isPartOf\":{\"@id\":\"https:\/\/ephesoft.com\/docs\/#website\"},\"datePublished\":\"2018-09-27T00:32:28+00:00\",\"dateModified\":\"2020-05-19T19:25:32+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/ephesoft.com\/docs\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Transact\",\"item\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Release Notes and Software Updates\",\"item\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"2019.2\",\"item\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/\"},{\"@type\":\"ListItem\",\"position\":5,\"name\":\"Ephesoft Transact 2019.2 Known Issues & Workarounds\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/ephesoft.com\/docs\/#website\",\"url\":\"https:\/\/ephesoft.com\/docs\/\",\"name\":\"Ephesoft Docs\",\"description\":\"Intelligent Document Processing Made Easy\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/ephesoft.com\/docs\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Ephesoft Transact 2019.2 Known Issues & Workarounds | Ephesoft Docs","robots":{"index":"noindex","follow":"follow"},"og_locale":"en_US","og_type":"article","og_title":"Ephesoft Transact 2019.2 Known Issues & Workarounds","og_description":"  Category Issue Workaround Installation and Upgrade: Windows After upgrading from Ephesoft Transact 2019.1 to version 2019.2 on a Windows […]","og_url":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/","og_site_name":"Ephesoft Docs","article_modified_time":"2020-05-19T19:25:32+00:00","og_image":[{"url":"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/06\/word-image-175.png"}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/","url":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/","name":"Ephesoft Transact 2019.2 Known Issues & Workarounds | Ephesoft Docs","isPartOf":{"@id":"https:\/\/ephesoft.com\/docs\/#website"},"datePublished":"2018-09-27T00:32:28+00:00","dateModified":"2020-05-19T19:25:32+00:00","breadcrumb":{"@id":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-2019-2-workarounds\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/ephesoft.com\/docs\/"},{"@type":"ListItem","position":2,"name":"Transact","item":"https:\/\/ephesoft.com\/docs\/products\/transact\/"},{"@type":"ListItem","position":3,"name":"Release Notes and Software Updates","item":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/"},{"@type":"ListItem","position":4,"name":"2019.2","item":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/"},{"@type":"ListItem","position":5,"name":"Ephesoft Transact 2019.2 Known Issues & Workarounds"}]},{"@type":"WebSite","@id":"https:\/\/ephesoft.com\/docs\/#website","url":"https:\/\/ephesoft.com\/docs\/","name":"Ephesoft Docs","description":"Intelligent Document Processing Made Easy","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/ephesoft.com\/docs\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/31767"}],"collection":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/comments?post=31767"}],"version-history":[{"count":0,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/31767\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/31761"}],"next":[{"title":"Ephesoft Transact 2019.2 Service Pack","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/ephesoft-transact-2019-2-service-pack\/","href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/35554"}],"prev":[{"title":"Ephesoft Transact Release Support","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/release-notes\/release-notes-2019-2\/transact-release-support\/","href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/31766"}],"wp:attachment":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/media?parent=31767"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/doc_tag?post=31767"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}