How To Fix RSOS116 - RFC connection to TREX engine is Null; searching or indexing not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: RSOS - Message class for BI Metadata Search with TREX

• Message number: 116

• Message text: RFC connection to TREX engine is Null; searching or indexing not possible

What causes this issue?

RFC connection to TREX engine is Null.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

Search or Indexing is not possible.

How to fix this error?

Procedure for System Administrators

To enter the RFC connection:
Execute transaction <LB>RSODADMIN</>.
In the <LS>Administration of BW Metadata Search</> screen, in <LS>RFC
Destination</>, select the appropriate RFC destination.
Choose <LS>Execute</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSOS116 - RFC connection to TREX engine is Null; searching or indexing not possible ?

  The SAP error message RSOS116 indicates that there is an issue with the RFC (Remote Function Call) connection to the TREX (Text Retrieval and Extraction) engine. This error typically arises when the system is unable to establish a connection to the TREX server, which is essential for searching or indexing operations in SAP systems that utilize TREX for full-text search capabilities.
  Causes:
  
  TREX Server Down: The TREX server may not be running or may have crashed.
  Network Issues: There could be network connectivity problems between the SAP application server and the TREX server.
  Configuration Issues: The RFC destination for the TREX connection may not be configured correctly in the SAP system.
  Authorization Issues: The user or service account used for the RFC connection may not have the necessary permissions to access the TREX engine.
  TREX Instance Not Registered: The TREX instance may not be properly registered in the SAP system.
  
  Solutions:
  
  
  Check TREX Server Status:
  
  Ensure that the TREX server is up and running. You can check the status of the TREX server using the TREX administration tools or logs.
  
  
  
  Verify Network Connectivity:
  
  Test the network connection between the SAP application server and the TREX server. You can use tools like ping or telnet to check connectivity.
  
  
  
  Review RFC Destination Configuration:
  
  Go to transaction SM59 in the SAP GUI and check the RFC destination that is configured for the TREX connection. Ensure that it is correctly set up and points to the correct TREX server.
  
  
  
  Check Authorization:
  
  Verify that the user or service account used for the RFC connection has the necessary authorizations to access the TREX engine. You may need to adjust roles or permissions.
  
  
  
  Check TREX Registration:
  
  Ensure that the TREX instance is properly registered in the SAP system. You can check this in transaction SICF or by using the TREX administration tools.
  
  
  
  Restart Services:
  
  If the TREX server is running but still not connecting, consider restarting the TREX services or the entire TREX server.
  
  
  
  Review Logs:
  
  Check the logs for both the SAP system and the TREX server for any additional error messages or warnings that could provide more context about the issue.
  
  
  
  Related Information:
  
  TREX Documentation: Refer to the official SAP documentation for TREX for detailed information on configuration and troubleshooting.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to TREX and RFC connections.
  SAP Community: Engage with the SAP Community forums for insights and solutions from other users who may have encountered similar issues.
  
  By following these steps, you should be able to diagnose and resolve the RSOS116 error related to the RFC connection to the TREX engine.