This documentation supports the 19.02 version of Remedy with Smart IT.

To view an earlier version, select the version from the Product version menu.

Troubleshooting Smart Recorder issues

When you use Smart Recorder, you might face issues such as Smart Recorder not retrieving correct templates, knowledge articles, or service requests. Use this information to understand and resolve the problem or to create a BMC Support case.

Symptoms

  • Smart Recorder does not retrieve suggested data.
  • Smart Recorder search retrieves incorrect results.
  • Smart Recorder takes a long time to retrieve search results.
  • Smart Recorder displays error messages when performing a Full Text Search (FTS) or Global search.

Scope

  • One or more users experience these problems.
  • In a server group environment, these problems might impact one or more servers.

Resolution

Perform the following steps to troubleshoot the Smart Recorder issues:

Step

Task

Description

1Try to replicate the issue.

Enter several different terms in Smart Recorder. 

If Smart Recorder does not suggest any templates, ensure that the templateSearchByAuthoringGroup property is set to False. If this property is set to True, template suggestion in Smart Recorder is limited to only those templates that match the support group to which the user belongs.

2

Open Chrome Developer Tools and check the response.

  1. Enter a search string in the Global search field or in Smart Recorder.
  2. Use the F12 key to enable the browsers developer tools.
  3. Check the /ux/rest/globalsearch response.
3Check the search results by running the search directly on the MFS:MultiFormSearch form.

Open the MFS:MultiFormSearch form in Remedy Mid Tier and search for the same keyword used in Global search and check the results.

4Log in to Remedy IT Service Management and check whether you are able to perform Global search.Check if the application retrieves any search results.
5Change the log level of the UX or Smart IT log to DEBUG.

For information on enabling debug log level, see  How to enable the debug log for Smart IT version 18.05 and 18.08

6Check the response from the Global search in the UX or Smart IT log.

Check for the word ERROR in the ux.log or smartit.log and verify the response.

The response must be /smartit/rest/globalsearch/suggest/search.

7Smart Recorder searches take a long time.

If searches in Smart Recorder take a long time to retrieve results, you can improve the search performance by modifying parameters in Server Group Configuration.

  1. Select Remedy Management Console > AR System Server Group Console > Server Group Configuration.

  2. Set the value of the isExclude_TAG_and_CI_ID and useLeadingSearchForAsset parameters as True.

8

Review the Remedy AR System configuration. Determine if the search is performed from indexer server or searcher (user-facing) server.

Verify the FTS configuration. For information on FTS configuration, see Troubleshooting FTS configuration issues . 

  • For searches run from the indexer server, see  Troubleshooting full text search

  • For searches run from the searcher server, see  How do I enable Debug FTS Plugin logs in ARSystem 1805 and above?

9

In the server where the search is being executed, enable API and SQL logging. 

You can enable logs across servers and server groups. For more information, see  Managing the server group logs

10

Reproduce the issue in both Smart IT and Remedy IT Service Management and note search-related information.

Enable logs and reproduce the problem. 
If you are unable to reproduce the problem, wait until the problem occurs on its own.

When you replicate the issue in both Smart IT and Remedy IT Service Management, provide the following information to BMC Support:

  • Name of the user who executed the search

  • The search criteria used
  • Time period that the problem occurred

Important:

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

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

Use a 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 any issue. 

See the following knowledge articles for more information about collecting a heap or thread dump:

  • Collecting a Heap or Thread dump of the AR Server
  • Collecting a Heap or Thread dump of the FTS Plugin Server
11

Disable logging.

Allow three to five minutes for log buffering before running Log Zipper. Use the steps listed in Enabling server-side AR System logs to disable logging.

12

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 information in this table to troubleshoot the issue.

13

Create 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 from the ..\pluginsvr\fts\secondary directory.
    • If there is more than one indexer, include all indexers
  2. Perform the following steps:
    1. Run the Log Zipper utility on each affected indexer server and select Zip Logs.
    2. For more information on how to run the Log Zipper utility using the maintenance tool, see  BMC Remedy AR System Maintenance Tool .
  3. Attach the ZIP file to your case. You can attach zip file up to 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.
14Analyze the logs.

You can review the logs to try to identify error messages or behaviors. Use the information in the following table to help identify possible symptoms and solutions.

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

SymptomLocationActionReference
Service request templates are not displayed properly.Smart Recorder

If you cannot see a service request template for a customer, check the following items:

  • Does the customer's People record include a login ID? 
    The Smart Recorder uses the customer's login ID to show available service request templates for that person. For more information, see  Configuring people information.
  • Is the customer entitled to see the service request template?
    For more information about service request entitlements, see Submitting service requests.
Submitting service requests

People search through Smart Recorder has delayed response.

Smart Recorder

You can configure the allowPersonSearchByNameOnly parameter.

This configuration parameter is used to set the name-based query. You can configure this parameter to true to enable search by firstname%lastname.

Centralized Configuration
Was this page helpful? Yes No Submitting... Thank you

Comments