TREX RFC Setup Test Failed 

Problem Description

The TREX RFC setup test failed in transactions SM59 and SRMO.

Scenario Type:	Error analysis
NetWeaver Component:	TREX
Validity:	TREX 6.1 SAP Web AS 6.20 and 6.40

Decision Roadmap

Prerequisites

Main Tools

Transactions

●     SM59

●     SRMO

Analysis

The following section describes typical problems that can occur after the installation of TREX in non-portal scenarios, as well as what to do about these problems.

Checking communication between the SAP system and TREX in transaction SM59 for RFC Destination imsdefault_reg

The error message may be:

●     partner not reached (Web AS 6.20) or

or

●     ThGetT1002 (Msg -10 not found) (Web AS 6.40)

Check if the gateway service configured in the RFC destination is started.

...

       1.      On Windows, you should see gwrd.exe in your task manager processes.

                            a.      If you do not see process gwrd.exe start the tool Services by choosing Start  ® Settings  ®  Control Panel  ® Administrative tools and check if the service SAPGWS_<InstanceNumber> is started.

■      If the service is missing here, check if the gateway was installed on the server.

■      If the service is displayed but cannot be started, contact SAP and provide the complete information about the error message.

                            b.      If you can see the gwrd.exe process, check whether the instance number of the gateway service in TREXRfcServer.ini and in transaction SM59 is the same as in the name of the gateway service displayed in the tool Services. Change this if necessary in the TREXRfcServer.ini and the RFC destination.

       2.      On UNIX, start the command ps –fe | grep gwrd .

You should see process gwrd as displayed on the following screenshot:

                            a.      If you do not see process gwrd, check if the gateway is installed on the server.

■      If the gateway has been installed, start it as gwsadm user with the following command:
/<…>/gwrd –force pf=/<…>/GWS_G<InstanceNumber>_<HostId>

For example:
/usr/sap/GWS/SYS/exe/run/gwrd -force pf=/usr/sap/GWS/SYS/profile/GWS_G47_Host1

■      If the process cannot be started, contact SAP.

                            b.      If you can see the gwrd process, you have to check whether the instance number of the gateway service in TREXRfcServer.ini and in transaction SM59 is the same as in the name of the gateway service. You can find this as part of the name of profile file GWS_G<InstanceNumber>_<HostId>.

 

The error message is program <HostID>.TREXRfcServer_<InstanceNumber> not registered.

       1.      This problem can occur if the TREX services were started before the gateway.

Restart the TREX services.

       2.      Check if the TREXRrcServer is running. The service is probably missing in file TREXDaemon.ini.

       3.      Check if the TREX instance is started.

       4.      The host ID in the TREXRfcServer.ini is not correct (the value should use the same lower/uppercase convention as used in transaction SM59).

Here is an example of such a mistake:

Part of the TREXRfcServer.ini:

[CONNECTION]

HOST=p102415

INSTANCE=sapgw47

SERVICE=P102415.TREXRfcServer_02

Configuration in Web AS: P102415.TREXRfcServer_02

The host ID in the RFC destination should be changed to p102415.

Alternatively, change the host ID in file TREXRfcServer.ini and restart the TREX services.

Checking the Search Server Relation in Transaction SRMO

The error message An RFC communication error occurred! No connection! is displayed when the communication between Web AS and TREX is tested on the RFC Destinations tab.

 

       1.      Check if the TREX services are running. Check the communication in transaction SM59 (see above).

       2.      Check if the search server relation in transaction SRMO points to the correct RFC destination.

 

No data path is visible when trying to display this using Display data path on the RFC Destinations tab in transaction SRMO:

 

Check if the TREX index server is running.

       1.      On Windows, you should see process TREXIndexserver.exe.

 

○     If you do not see TREXIndexServer.exe, you have to check whether the TREX instance service is started and start it if necessary:

○     If the service cannot be started or some of the TREX services are not running, you have to contact SAP.

       2.      On Unix you should see process TREXIndexServer.x.

○     If you do not see TREXIndexServer.x you have to check if some of TREX services were started. You can see these with command

ps –fe | grep TREX

Try to start these with command TREX start

○     If the service cannot be started or some of the TREX services are not running, you have to contact SAP.

Additional Information

Search and Classification (TREX)

Technical Operation of Search and Classification (TREX)

Search and Classification (TREX) Security Guide: Minimal Installation