How To
Summary
Datacap Navigator or TMWeb takes too long for executing validation rules, also the users are being kicked out randomly. The issue is more visible when the user load increases.
This happens because the application pool running the validations is the process which executes it for all the users running the verify task on thin clients, besides attending other calls like logins and other requests to the site, if the application has too many validation rules the application pool get's exhausted.
Steps
To enable the eRRO feature within Datacap, follow the steps described here.
When using the transaction or executing endpoint of Datacap Web Services, for example, when using Navigator Scan or Verify, it is required to set a mandatory registry key to enable the eRRO. If the registry key is not set, the Datacap Webserivce can crash while transactions are made.
Enabling the eRRO registry for Datacap thin clients will allow a new separated process to execute the validation rules called eRRo.exe, this setting will create a separated process for each user running the verification view on TMWeb, and for Datacap Navigator will be generated while clicking submit on the verify.js page
On above image we can see how 2 sessions are running validations and how each of them has it's own eRRO.exe process.
For enabling this setting you need to set the following registry key to 1:
"[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\RRS] "Use eRRO"=dword:00000001"
Was this topic helpful?
Document Information
Modified date:
22 February 2024
UID
ibm10792169