Symptom
In the Landscape RFC window, the configuration status is yellow or red.
Meaning
The RFC configuration is inconsistent. There are inconsistencies either in the TREX system or between the TREX system and the SAP system.
Activities
This function corrects all configuration errors for which automatic correction is possible. This can take several minutes. During this time, the configuration status remains yellow or red.
Do not choose Repair All several times in quick succession. This would trigger reconfiguration more than once and delay the correction of errors.
We recommend always choosing Repair All first and only correcting configuration errors individually that require manual intervention.
It does not make sense to correct only selected configuration errors. However, the TREX admin tool provides this option, if you require it in special circumstances.
In the following section, you can find information about all configuration errors that can occur.
Local Gateway: Application Server Cannot Reach the TREX System
Symptom
An RFC connection has the status red. When you select the RFC connection, the lower half of the window displays the following:
Meaning
The application servers are running and using their local SAP gateways for the RFC connection. The application servers are specified in the TREX configuration. However, at least one application server cannot reach the TREX system. Possible causes are:
Activities
This action does not solve the cause of the error. However, you can avoid unnecessary TREX trace files.
Once the cause of the error is solved (for example, the Gateway is available again), this is reported to the TREX system. The Landscape RFC window then provides the option of adding the application server to the TREX configuration again.
Local Gateway: Application Server Is not Registered in the TREX Configuration
Symptom
An RFC connection has the status yellow or red. When you select the RFC connection, the lower half of the window displays the following:
Meaning
There are application servers in the SAP system that are not registered in the TREX configuration. Possible causes are:
Activities
Central Gateway Is not Available, But Is Registered in the TREX Configuration
Symptom
An RFC connection has the status red. When you select the RFC connection, the lower half of the window displays the following:
Meaning
The SAP system and the TREX system communicate through a central Gateway. The Gateway is registered in the TREX configuration, but is not available. Therefore, the application servers cannot reach the TREX system.
Possible cause: The gateway information in the RFC destination contains typing errors.
Activities
This action does not solve the cause of the error. However, it helps to avoid unnecessary TREX trace files.
When you refresh the display, the following message appears:
GW is nonexistent, inactive or inaccessible - manual repair required
Once the cause of the error is solved (for example, the Gateway is available again), this is reported to the TREX system. The Landscape RFC window then provides the option of adding the Gateway to the TREX configuration again.
For more information about the procedure, see Changing the Central Gateway.
Central Gateway: If there are network problems
Symptom
An RFC connection has the status yellow or red. When you select the RFC connection, the lower half of the window displays the following:
GW set in TREX, GW available. Network problems?
Meaning
The SAP system and the TREX system communicate through a central Gateway. The RFC configuration is correct in both systems and the Gateway is available. Nevertheless, the application servers cannot reach the TREX system.
Possible cause: There are network problems.
Activities
Attempt to correct the network problems. Configuration changes are not necessary.
Central Gateway Is not Registered in the TREX Configuration
Symptom
An RFC connection has the status yellow or red. When you select the RFC connection, the lower half of the window displays the following:
Meaning
An Gateway that is not registered in the TREX configuration is entered in the RFC destination.
Possible cause: The TREX system has not been configured after installation.
Activities
Central Gateway Is Not Available
Symptom
An RFC connection has the status yellow or red. The following message appears:
GW is nonexistent, inactive or inaccessible - manual repair required
When you select the RFC connection, the lower half of the window displays the following:
Meaning
An Gateway that is not available is entered in the RFC destination. The TREX system and the SAP system cannot communicate through this Gateway.
Possible causes are:
Activities
To do this, use transaction SM59 in the SAP system.
For more information about the procedure, see Changing the Central Gateway.
RFC Destination not Available in the SAP System
Symptom
The Landscape RFC window displays the following message:
No TREX relevant RFC Destination in SAP System
Meaning
The TREX admin tool can connect to the SAP system. RFC destinations are registered in the TREX configuration. However, there are no RFC destinations of the same name in the SAP system.
With regard to RFC destinations, you must ensure the following:
Activities
To do this, use transaction SM59 in the SAP system.
To do this, use the TREX admin tool (stand-alone), Landscape RFC window, RFC Destinations function.
More Than one External Application Uses the Same RFC Destination
Symptom
An RFC connection has the status red. The following message appears:
Another application is also using this RFC destination - manual repair required
When you select the RFC connection, the lower half of the window displays the following:
Meaning
In the SAP system, there is an RFC destination that is used by more than one external application. The reason is probably that there is more than one TREX system that is connected to the same SAP system and uses the same RFC destination.
With this configuration, the SAP system cannot distinguish which external application it sends the requests to. It is possible that the wrong external application receives the requests.
Activities
If the external applications in question are only TREX systems, proceed as follows:
If the external applications in question are not only TREX systems, proceed as follows:
For a TREX system, use the RFC Destinations function in the Landscape RFC window to do this.
For other external applications, you can find the procedure in the documentation of the application in question.
Unnecessary Application Servers in the TREX Configuration
Symptom
The Landscape RFC window displays the following message:
App Servers in TREX that belong to none of the connected SAP Systems
Meaning
There are application servers specified in the TREX configuration that do not belong to the SAP system. Possible causes are:
Activities
The lower half of the window displays the superfluous entries.
Faulty Gateway Instance or Program ID in the TREX Configuration
Symptom
The Landscape RFC window displays the following message:
App Servers/GW hosts in TREX with wrong instance or service
Meaning
The configuration of one or more TREX RFC servers is incorrect. Either the gateway instance is incorrect or the program ID that these TREX RFC servers use to register with the Gateway. Due to the incorrect configuration, these TREX RFC servers cannot receive requests from the SAP system.
Activities
The lower half of the window displays the incorrect entries.
Unnecessary RFC Destinations in the TREX Configuration
Symptom
The Landscape RFC window displays the following message:
RFC Destinations in TREX that belong to none of the connected SAP Systems
Meaning
There are RFC destinations specified in the TREX configuration that do not exist in any of the connected SAP systems.
Possible cause: An administrator has deleted the RFC destination in the SAP system.
Activities
The lower half of the window displays the superfluous entries.
Number of RFC Server Instances Is Inconsistent
Symptom
The Landscape RFC window displays the following message:
Configured Number of RFC Servers differs from default value
Meaning
The number of started RFC server instances is different to the number defined as the default value.
Activities
The lower half of the window displays the connections for which there are inconsistencies.
Program ID Is Possibly not Unique
Symptom
The Landscape RFC window displays the following message:
Potentially non unique Program IDs detected
Meaning
This message occurs if you have created RFC destinations directly in the SAP system and not using the TREX admin tool (stand-alone).
One or more RFC destination contain program IDs that do not conform to the naming convention defined by TREX. The program IDs may not be unique. This can cause problems if more than one TREX system communicates with SAP applications using the same SAP gateways. The requests from the SAP applications could be forwarded to the wrong TREX system.
Activities
The lower half of the window displays the connections that are affected by this problem.
The change is made in the TREX configuration and in the RFC destination in the SAP system.