Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: CMS - KPro: Content Management Service
Message number: 173
Message text: RFC destination &1 is using gateway (&2 / &3)
The RFC destination &V1& does not have the standard values. The RFC
destination &V1& is using a gateway (&V2& / &V3&).
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Delete RFC destination &V1& (<DS:TRAN.SM59>Defining RFC destinations
</>). If necessary, the system automatically re-creates the destination
with the standard values.
Error message extract from SAP system. Copyright SAP SE.
CMS173
- RFC destination &1 is using gateway (&2 / &3) ?The SAP error message CMS173 indicates an issue with the RFC (Remote Function Call) destination configuration in your SAP system. Specifically, it suggests that the RFC destination is using a gateway that is not properly configured or is experiencing issues.
Cause:
- Gateway Configuration Issues: The specified gateway might not be correctly set up or might be down.
- Network Issues: There could be network connectivity problems between the SAP systems.
- Incorrect RFC Destination Settings: The RFC destination might have incorrect parameters, such as the wrong gateway host or service.
- Multiple Instances: If multiple instances of the SAP system are running, there might be conflicts in the gateway settings.
Solution:
Check Gateway Configuration:
- Use transaction code
SMGW
to check the status of the gateway. Ensure that the gateway is running and properly configured.- Verify the gateway host and service settings in the RFC destination.
Verify RFC Destination:
- Go to transaction code
SM59
to check the configuration of the RFC destination.- Ensure that the target system's connection parameters (like the gateway host and service) are correct.
Network Connectivity:
- Test the network connection between the systems. You can use tools like
ping
ortelnet
to check connectivity to the gateway host and port.- Ensure that firewalls or network policies are not blocking the connection.
Check for Multiple Instances:
- If you have multiple SAP instances, ensure that they are not conflicting with each other regarding the gateway settings.
Restart Gateway:
- If the gateway is down or unresponsive, consider restarting it. This can sometimes resolve transient issues.
Review Logs:
- Check the system logs (transaction
SM21
) for any related error messages that might provide more context on the issue.Related Information:
SMGW
: Gateway MonitorSM59
: RFC DestinationsSM21
: System LogIf the problem persists after following these steps, consider reaching out to your SAP Basis team or SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
CMS172
RFC Destination &1 OK and Accessible
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CMS171
RFC Destination &1 Inaccessible: &2&3&4
What causes this issue? The RFC destination &v1& is not accessible: &V2&&V3&&V4&System Response The system issues an...
CMS174
Trace for RFC request to &1, command &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CMS175
Trace for RFC request to command &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.