Assorted Issues - Application Enabler - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Application Enabler

Application Enabler
Foundation 23.1
  1. After Installation I can log on to the Web Client, but not Application Enabler .

    Exception thrown calling Open. Description is: Could not connect to data source. Source is IDMDesktop:: Open

    There are several potential causes for this error.

    • Invalid login information. Login with valid credentials and a valid ODBC source.

    • Concurrent licenses exceeded. You cannot run the OnBase Web Client and Application Enabler at the same time using a Sybase standalone database.

    • Running Application Enabler with the -AE:DEMO command line switch with the Web Server running on the same machine.

    • The exe_dmwebsvcmgr service uses a database connection that allows only one connection with a standalone database.

    Once you have logged into the Web Server and wish to close it in order to log into Application Enabler, you must stop the exe_dmwebsvcmgr.

    • Improper termination of a program.

    It may be necessary to end the DBEngine50.exe process via Windows Task Manager.

  2. Why do errors initializing one of the ActiveX components (Select list, Retrieval dialog box, Viewer window, Keyword panel) occur?

    A number of issues can prevent the ActiveX components from functioning correctly:

    • Verify that Internet Explorer will permit components to initiate and use scripting.

    • Verify that the correct versions of the components are installed.

    • Verify that Internet Explorer does not have an earlier version installed as a web component.

  3. Why does Application Enabler not respond well on some workstations?
    Any VB application that uses Mouse Hooking Technology must be running service pack 5 or above of the Microsoft Visual Basic Runtime Engine (Msvbvm60.dll). See M icrosoft KB Article 238672 for further information.
  4. I receive a message stating The following function generated an unknown exception: CAEClientApp::InitInstance.
    When this message is encountered, the Hyland.Applications.AppEnabler.Connector.dll file has not been installed in the correct location. See Installation Requirements for Applications Using Named Pipes for more information.
  5. I receive a “Textract error -992: Initialization failed” in AEClient.
    This is an issue with Application Enabler and Windows Data Execution Prevention (DEP). To resolve, follow the steps in Application Enabler and Data Execution Prevention (DEP).
  6. I receive a "Exception in Module: (null) - Message: Unknown error 0x800704A6" error when attempting to scrape in Demo Mode.
    This issue is caused if components of Internet Explorer that Application Enabler uses for Demo Mode became corrupt. Reinstalling Internet Explorer will resolve this issue.
  7. I receive a "Exception in Module: (null)... Function: LoadXML" error when attempting to launch Application Enabler Client.
    This issue is caused if Application Enabler is configured to load a specific XML configuration file by default, but that file is either missing, corrupt, or the user does not have permissions to it. The path to the XML configuration file can be specified in the Application Enabler executable shortcut's Properties. To resolve this error, verify that the XML configuration file exists, is accessible by the user(s), and is not corrupt.
  8. I cannot properly configure a line-of-business application containing buttons that appear or disappear depending on whether a field is selected.
    This issue occurs because the appearance of the button in the line-of-business application causes subsequent fields to be shifted down to accommodate the presence of the new button. To properly configure Application Enabler to handle these kinds of buttons, you must anchor the cursor by placing it in a field within the line-of-business application that does not cause a button to appear. Map the Keyword Value to the line-of-business application by clicking in the desired field. After mapping and verifying each keyword, return the cursor to the anchor location. You can also attempt to configure the line-of-business application as a smart-screen application.
  9. The dialog box to choose between multiple Document Types is inactive or appears behind the Unity Client on some Windows machines when performing the Application Enabler - Index context event when more than one Document Type is configured.
  10. Concurrent Client licenses are still consumed even though Application Enabler users have shut down their workstations. IIS must be reset in order to release these licenses.
    This issue occurs because the workstations were shut down prior to closing Application Enabler. To resolve this issue, users must close Application Enabler prior to shutting down a workstation. You can also change the session enableTimeout setting to true in the Application Server's web.config file. This will allow the Application Server to disconnect abandoned sessions. The default interval is 20 minutes. To specify a different interval, edit the timeout value to reflect the number of minutes an abandoned session should remain open. The timeout value is located in the sessionState element of the Application Server's web.config. For more information on Application Server settings, see the Web Server module reference guide.
  11. When using the Unity Client with Application Enabler , a Concurrent Client license is still consumed after the Unity Client is closed with the Close button.
    This occurs because the Unity Client is still running. To close the Unity Client, right-click the system tray icon and select Exit OnBase.
  12. Mouse and keyboard events are generating duplicate events, regardless of which configured context is being used. For example, performing the mouse event for the Barcode Rendering context generates duplicate bar code pages.
    This occurs because of the way the line-of-business application is recognizing keyboard and mouse events. To resolve this issue, enable Low Level Detection Mode in Application Enabler Configuration.
  13. A Windows-based line-of-business application is unable to be successfully configured using the Windows configuration process.
    Attempt to configure the application using the Smart-Screen configuration process. If that is unsuccessful, attempt the text-based configuration process. If that also proves unsuccessful, use Application Enabler 's OCR functionality.
  14. When attempting to enable an application, an Invalid hook handle message is displayed:

    Ensure that the third-party application is running at the same UAC level as Application Enabler. If this does not work, restart Application Enabler and the line-of-business application.

  15. When using Application Enabler Live on an enabled HTML-screen, sporadic exception messages are displayed.
    Enabling Silent Mode can suppress these exception messages if they are not interfering with your business process. For more information about enabling Silent Mode, see Application Enabler Live Configuration
  16. I need to enable an HTML-screen, but I do not want to disable Internet Explorer's Protected Mode.

    Protected Mode does not have to be disabled for all sites in Internet Explorer, only the site that Application Enabler is enabling. This can be accomplished by adding the site to a security zone in Internet Explorer which does not have Protected Mode enabled.

    For more information about Protected Mode, see

    For more information about security zones in Internet Explorer, see