How To Fix SRT_WS_IDP035 - Check from client &1 is not allowed for client &2

SAP Error Message - Details

• Message type: E = Error

• Message class: SRT_WS_IDP - Message Class for Idempotent WS

• Message number: 035

• Message text: Check from client &1 is not allowed for client &2

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_WS_IDP035 - Check from client &1 is not allowed for client &2 ?

  The SAP error message SRT_WS_IDP035 indicates that there is a client inconsistency when trying to access a web service. Specifically, the error message states that a check from one client (client &1) is not allowed for another client (client &2). This typically occurs in scenarios involving cross-client communication or when a web service is being called from a different client than the one it is configured for.
  Cause:
  
  Cross-Client Access: The web service is being accessed from a client that is not authorized to do so. In SAP, each client is a separate environment, and certain configurations or data may not be shared across clients.
  Configuration Issues: The web service might be configured to only allow access from specific clients, and the client making the request does not match those configurations.
  Authorization Issues: The user or service account making the request may not have the necessary authorizations to access the web service from the specified client.
  
  Solution:
  
  Check Client Configuration: Verify the configuration of the web service in transaction SOAMANAGER. Ensure that the service is correctly set up to allow access from the intended client.
  Adjust Client Settings: If the web service is intended to be accessed from multiple clients, you may need to adjust the settings to allow cross-client access. This may involve modifying the service definition or the client-specific settings.
  User Authorizations: Ensure that the user or service account making the request has the necessary authorizations in both clients. You can check this in transaction SU01 for user roles and authorizations.
  Testing in Correct Client: If the web service is only meant to be accessed from a specific client, ensure that you are testing or calling the service from that client.
  Consult Documentation: Review SAP documentation or notes related to the specific web service you are using, as there may be additional configuration steps or considerations.
  
  Related Information:
  
  Transaction Codes: 
  
  SOAMANAGER: For managing web service configurations.
  SU01: For user management and authorization checks.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Logs and Traces: Review the application logs (transaction SLG1) and traces to gather more information about the error context and any additional details that may help in troubleshooting.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis or technical team for further assistance, as they may have more insights into the specific configurations and settings in your SAP environment.