This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Troubleshooting FTS searching issues

When you configure the AR System Server for full text search (FTS) or Global search, you might encounter issues regarding FTS searching.  Use this information to understand and resolve the problem or to create a BMC Support case.


  • You do not get any results when you perform an FTS search.
  • You get incorrect results from the Global searches.
  • You receive error messages while performing an FTS or Global search.
  • You encounter a performance issue while performing the search.


In a server group environment, this might impact one or more servers.


Perform the following steps to troubleshoot the FTS searching issues:





Determine if the search is performed on the indexer server or searcher server (user-facing server)


Enable API and SQL logging on the server performing the search

See the steps described in the Enabling server-side AR System logs topic.

For load-balanced environments, enable the API and SQL log from all user-facing servers in the server group.    

Perform the following steps to enable debug searcher logging from the indexer server:

  • Remove previous log entries from the ..\db directory to reduce the log file size.
  • Rename log files to make it easier to identify.
  • Ensure that the log files include the time when the issue was reproduced.
    Starting with version 18.05, you can enable logs across servers and server groups. For more information, see Managing the server group logs

Reproduce the issue.

If you do not have specific steps to reproduce the issue, enable the logs, wait for the problem to occur, and then perform these steps.

Provide the following information to BMC Support.

  • Name of the user who performed the search.
  • The search criteria used.
  • Time when the problem occurred.


Analyze Java heap stack if you encounter any of the following problems:

  • Java heap size
  • AR System Server stops responding
  • FTS plug-in server stops responding

Use the Java Virtual Machine (JVM) or other appropriate tools to obtain a heap dump or thread dump as necessary. Collect the dump files when you observe the problem. 
For more information about collecting a heap or thread dump, see the following knowledge articles:


Disable logging


Collect the logs

  • Copy logs to another location where you can view them.
    Ensure that the logs are not overwritten.
  • Review the symptoms and error messages.
    Use the table to troubleshoot the issue.
6Analyze the logsYou can review the logs, identify error messages or behaviors. Use the table to identify possible symptoms and solutions.
7Create a BMC Support case

Collect and send logs and detailed information when creating a case with BMC Support:

  1. Provide the following information as part of your case:

    • Name of the user who performed the search.
    • The search criteria used.
    • Time when the problem occurred.
    • Any error messages received.
    • Include the pluginsvr_config.xml file located in the ..\pluginsvr\fts\secondary directory.
    • If you have more than one indexer, include all.
  2. Perform the following steps:
    1. Run the Log Zipper utility on each affected indexer server and select Zip Logs
    2. If you provide the Log Zipper file from multiple servers, rename the file to include the server name.
  3. Attach the zip file to your case.
    You can attach a zip file upto 2 GB. You can also upload the files on FTP.
    For more information, see How to use BMC's Managed File   Transfer (MFT) to send log files to BMC Support to comply with GDPR policies.

After you determine a specific symptom or error message, use the following table to identify the resolution:

ARERR 8760On Screen
  • Check the Server-Plugin-Alias parameter in the ar.cfg file or in Centralized Configuration.

Slow response

Search results take too long to return

  1. Check the numcorethreads in the plug-in configuration.
  2. Check the API or SQL logs to determine if the FTS portion or the database portion of the search is slow.
  3. Ensure that the search string is not long by verifying the arfts-searcher.log file.
  4. Check the FTS Best Practice knowledge article to successfully set up the AR System Server and the FTS plug-in server.

ARERR 657 or ARNOTE 657

Failed to complete full text operation

The arerror.log file on screen

Check the arftindx.log file for related messages.

ARS:ARF.FTS (8753)
Error while searching

On screen

Check the configuration of the FTS secondary plug-in.

ARWarn 682


Full text search service not available; a database search was performed

The arerror.log file and the arsql.log file on the screen

  • Check if a reindex is being performed. Obtain the arftindx.log file from each indexer.
  • Query the ft_pending table for operationType 5 or 7.
  • Obtain the arerror.log and arsql.log files from the searcher server.
    • If you perform search on an indexer server and failover occurs, the search does not move to the next rank searcher server.
    • If you perform a search on a non-indexer server (searcher server), all the indexer servers are busy.
  • If indexing is progressing, wait for it to complete.
  • If Indexing does not work, contact BMC Support and provide the necessary log files.

Data is missing from resultsBrowser
  • Ensure that the field is indexed in Developer Studio.
  • Check the arftindx.log file to see if any record or any form is indexed or is showing any error.
    • If the arftindx.log file shows an error, the index might be corrupted. You can reindex the form.
    • If it is taking too long to index other data, review the knowledge article Best Practices.
  • Ensure that you are not out of disk space for the Collection directory.
  • Check the arfts-searcher.log file and check if the Phase 2 of FTS searches (applying permissions) eliminated the results because of Row-Level-Security.

Best Practice

To ensure that Full Text Search Threshold is high enough to return adequate results, we recommend that you set it to 2000.

FTS Memory Leak

OS Tools


Addressed in 18.02 hot fix package:

FTS search is not working if field data contains dash or underscore like (- or _).



Addressed in 18.02 hot fix package:

FTS searcher server error OutOfMemoryError in arftsplugin-searcher.logarftsplugin-searcher.log

Increase heap (See knowledge article FTS Best Practices)

Common Error Messages:

  • java.lang.OutOfMemoryError: GC overhead limit exceeded
  • java.lang.OutOfMemoryError: Java heap space
Cannot insert duplicate key row in object 'dbo.ft_pending'API/SQL logsSW00548960

Addressed in 18.02 hot fix package:

ERROR (678): Full text indexing is disabled -- turn on full text indexing and retry your operation;

The arfts-searcher-plugin.log file on screen

Check the FTS tab from Server Information form and confirm FTS searching is not set to disabled.

Fri Nov 30 12:40:13 2018 390602 :r:0 : The specified plug-in does not exist. (ARERR 8755)

The arerror.log file
  • Check the Server-Plugin-Alias parameter in the ar.cfg file to validate Server Name and Port.
  • Check plug-in configuration from the Plug-in Server Configuration.
Was this page helpful? Yes No Submitting... Thank you