How To Fix SRT_WSP3035 - Domain system '&1' does not support communication type RFC

SRT_WSP3035 - Overview

• Message type: E = Error

• Message class: SRT_WSP3 - SRT: Web Service Configuration Messages 3

• Message number: 035

• Message text: Domain system '&1' does not support communication type RFC

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SRT_WSP3035 - Domain system '&1' does not support communication type RFC ?

  The SAP error message SRT_WSP3035 indicates that the domain system specified (represented by &1) does not support the communication type RFC (Remote Function Call). This error typically arises in the context of SAP Process Integration (PI) or SAP Process Orchestration (PO) when trying to establish communication between systems.
  
  Cause:
  
  
  Configuration Issues: The target system may not be configured to accept RFC calls. This could be due to incorrect settings in the SAP Gateway or the RFC destination.
  Communication Type Mismatch: The communication type specified in the configuration does not match the capabilities of the target system. For example, if the target system is set up for HTTP communication but the source system is trying to use RFC.
  Network Issues: There may be network connectivity issues preventing the systems from communicating properly.
  Authorization Issues: The user credentials used for the RFC connection may not have the necessary authorizations to perform the requested operation.
  
  
  Solution:
  
  
  Check Configuration:
  
  Verify the configuration