Diagnostics - Application Enabler - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Premier - Essential - Standard

Application Enabler

Platform
OnBase
Product
Application Enabler
Release
Foundation 23.1
License
Premier
Essential
Standard

The Diagnostics page is used for troubleshooting.

In the Logging portion of the screen, enable logging by clicking On. Turn logging off by clicking Off. You can view the diagnostic log (AEVerbose.txt) by clicking View Log. This file also contains OCR result information.

CAUTION:

Each time you enable logging, the previous log file is overwritten in the workstation's TEMP directory (defined in the workstation's Environment Variables). To retain previous log files, open them and save them with a different file name.

Tip:

Since logging can impact performance, only enable it when necessary.

The Named Pipe portion of the screen displays the following:

Named Pipe

Description

Remote Mode

When true, Application Enabler is running in a Remote Desktop environment.

When false, Application Enabler is not running in a Remote Desktop environment.

Remote Session ID

The unique session identifier associated with the user when running in a Remote Desktop environment.

Pipe Count

The current number of clients being serviced by the named pipe server.

In the OCR portion of this screen, click Rebuild Font Database to rebuild the OCR font database, which the OCR engine requires to do OCR parsing. Once the font database is built, a file named OCRSDK.pat is generated in the %TMP% folder. %TMP% refers to the path specified by the TMP environment variable in Windows. The font database should be rebuilt each time users install new fonts on their workstations. For information about adding missing fonts, contact your solution provider.

In the Ping Automation portion of this screen, click HTTP to check the status of the HTTP Listener and verify it is functioning and ready to receive information. Click HTTPS to check the status of the HTTPS Listener and verify it is functioning and ready to receive information. If either the HTTP Listener or the HTTPS Listener become unresponsive, you can click HTTP in the Reset Automation section to reset them and restore functionality.