How To Fix /FTI/EXT_SRV_MAINT028 - No Hits Found

SAP Error Message - Details

• Message type: E = Error

• Message class: /FTI/EXT_SRV_MAINT -

• Message number: 028

• Message text: No Hits Found

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /FTI/EXT_SRV_MAINT028 - No Hits Found ?

  The SAP error message /FTI/EXT_SRV_MAINT028 No Hits Found typically occurs in the context of SAP's Full Text Indexing (FTI) functionality. This error indicates that a search query did not return any results, meaning that the system could not find any entries that match the search criteria specified.
  Causes:
  
  No Data Indexed: The most common cause is that there are no documents or entries indexed in the system that match the search criteria.
  Incorrect Search Criteria: The search parameters or keywords used may not match any indexed data.
  Indexing Issues: There may be issues with the indexing process itself, such as incomplete indexing or errors during the indexing job.
  Data Deletion: The data that was previously indexed may have been deleted or is no longer available.
  Authorization Issues: The user may not have the necessary authorizations to view the indexed data.
  
  Solutions:
  
  Check Indexed Data: Verify that there is data available in the system that should be indexed. You can do this by checking the relevant tables or documents.
  Review Search Criteria: Ensure that the search criteria you are using are correct and relevant. Try using broader or different keywords to see if any results are returned.
  Reindexing: If you suspect that the indexing process has issues, you may need to reindex the data. This can usually be done through the SAP transaction codes related to FTI, such as /FTI/INDEX or similar.
  Check Indexing Jobs: Look into the background jobs related to indexing to see if there were any errors or if the jobs have completed successfully.
  Authorization Check: Ensure that the user has the necessary permissions to access the indexed data. You may need to consult with your SAP security team to verify this.
  Consult Documentation: Refer to SAP documentation or support notes related to Full Text Indexing for any specific troubleshooting steps or known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /FTI/EXT_SRV_MAINT for maintaining external services and /FTI/INDEX for managing indexing.
  SAP Notes: Check SAP Notes for any updates or patches that may address known issues with Full Text Indexing.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.