Skip to content
Go to Customer Portal
  • There are no suggestions because the search field is empty.

AppEnhancer - Address full-text license checkout errors in REST integrations

After upgrading to AppEnhancer, you may see full-text license checkout errors in Windows Event Viewer during REST activity, even when your environment does not have full-text licensing and your integration does not intentionally submit documents for full-text processing.

Versions
  • AppEnhancer 25.4
  • Environments that do not use full-text functionality

Applicability to other versions or REST endpoints has not been established by this case.

Symptoms

Windows Event Viewer records the following error:

CheckOut license for feature AX_xPlore_Users with count 1 failed due to error (-5) Feature does not exist..

In the reported case, the error appeared after an upgrade to AE 25.4. The customer reported having no full-text licensing and believed automatic full-text submission was disabled.

Cause

The error identifies an attempted checkout of the AX_xPlore_Users license feature, which was unavailable in the reported environment. The error was filling up the event logs.

Disabling automatic full-text submission alone did not address the customer’s reported REST-related behavior.

Resolution:
Explicitly disable full text in the affected REST request.

Use this workaround only when your integration does not require full-text functionality.

  1. Identify the REST request associated with the license checkout errors.
  2. Add the query parameter requestft=false to the affected request URL.
  3. Retest the operation and review newly generated Event Viewer entries.

The customer supplied a POST request with this structure. The data source and application values below are placeholders for your environment:

/AppEnhancerReST/api/AXDataSources/{DataSource}/AXDocs/{ApplicationId}?requestft=false

Implementation notes:

  • Replace {DataSource} and {ApplicationId} with your existing request values.
  • If your URL already has a query string, append &requestft=false rather than adding a second ?.
  • The customer described the change as disabling full text during login, but supplied the AXDocs request example above. Validate the affected request in your integration before applying the change more broadly.
Additional recommendation: Review full-text privileges

If your environment does not use full text at all, review the full-text submission and query privileges granted to groups or individual users at the global profile level, depending on how your system assigns privileges.

Technical Support recommended disabling both privileges for applicable groups or users to reduce or potentially eliminate the related event-log errors and warnings.

Important: Review the impact before removing privileges, and do not remove access needed by users or integrations that rely on full text.

Verify the result

After applying the change:

  1. Repeat the REST operation that previously coincided with the error.
  2. Confirm that the intended integration operation still completes successfully.
  3. Check Event Viewer for new occurrences of the AX_xPlore_Users checkout error.
  4. If the error continues, identify whether another REST request or a remaining full-text privilege is involved.