How To Fix REXCES335 - Incorrect RFC connection or Web service is not working

SAP Error Message - Details

• Message type: E = Error

• Message class: REXCES -

• Message number: 335

• Message text: Incorrect RFC connection or Web service is not working

What causes this issue?

You cannot validate the cadastral reference because the external web
service used to check the information is currently down.

System Response

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

How to fix this error?

Try again at a later time. If the problem persists, contact your system
administrator.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message REXCES335 - Incorrect RFC connection or Web service is not working ?

  The SAP error message REXCES335 typically indicates an issue with the Remote Function Call (RFC) connection or a web service that is not functioning correctly. This error can arise in various scenarios, such as when trying to connect to an external system or when invoking a web service from SAP.
  Causes:
  
  
  Incorrect RFC Destination: The RFC destination may not be configured correctly in the SAP system. This could include incorrect connection parameters, such as the hostname, service number, or user credentials.
  
  
  Network Issues: There may be network connectivity issues between the SAP system and the target system. This could be due to firewall settings, network outages, or incorrect routing.
  
  
  Web Service Configuration: If the error is related to a web service, it could be due to incorrect configuration of the web service endpoint, such as the URL being incorrect or the service not being available.
  
  
  Authorization Issues: The user credentials used for the RFC connection may not have the necessary authorizations to access the target system or web service.
  
  
  Service Availability: The target service may be down or not running, leading to connection failures.
  
  
  Solutions:
  
  
  Check RFC Destination:
  
  Go to transaction SM59 in SAP.
  Verify the configuration of the RFC destination. Ensure that the connection parameters (like hostname, service number, and user credentials) are correct.
  Test the connection using the "Connection Test" button.
  
  
  
  Network Troubleshooting:
  
  Check network connectivity between the SAP system and the target system. You can use tools like ping or telnet to verify connectivity.
  Ensure that any firewalls or network security settings allow traffic on the required ports.
  
  
  
  Web Service Configuration:
  
  If using a web service, verify the endpoint URL and ensure that the service is up and running.
  Check the web service configuration in transaction SOAMANAGER to ensure that it is set up correctly.
  
  
  
  Authorization Check:
  
  Ensure that the user credentials used for the RFC connection have the necessary authorizations to access the target system or web service.
  You can check user roles and authorizations in transaction SU01.
  
  
  
  Service Status:
  
  If the target service is down, contact the administrator of the external system to check the service status and resolve any issues.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to REXCES335. You can search for notes in the SAP Support Portal.
  Logs and Traces: Review the application logs (transaction SLG1) and RFC traces (transaction SM21) for more detailed error messages that can provide additional context.
  Documentation: Refer to SAP documentation for more information on configuring RFC connections and web services.
  
  By following these steps, you should be able to diagnose and resolve the REXCES335 error in your SAP environment.