How To Fix SRT_WSP2346 - IBC Reference with receiver type '&1',name '&2' and system '&3' not found

SAP Error Message - Details

• Message type: E = Error

• Message class: SRT_WSP2 - Messages for SRT WSP

• Message number: 346

• Message text: IBC Reference with receiver type '&1',name '&2' and system '&3' not found

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_WSP2346 - IBC Reference with receiver type '&1',name '&2' and system '&3' not found ?

  The SAP error message SRT_WSP2346 indicates that there is an issue with the configuration of a web service in the SAP system. Specifically, it means that the system is unable to find a specific IBC (Integration Broker Component) reference for a given receiver type, name, and system. This typically occurs in scenarios involving SAP Process Integration (PI) or SAP Process Orchestration (PO) when trying to call a web service.
  Cause:
  
  Missing Configuration: The specified receiver (service) is not configured correctly in the SAP system. This could be due to missing entries in the Service Registry or incorrect settings in the Integration Directory.
  Incorrect Receiver Type: The receiver type specified in the error message may not match any existing configuration.
  System Not Registered: The system specified in the error message may not be registered in the SAP landscape or may not be accessible.
  Transport Issues: If the configuration was recently transported from another system, it may not have been transported correctly or completely.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the Integration Directory and verify that the receiver service is correctly configured.
  Ensure that the receiver type, name, and system match the values specified in the error message.
  
  
  
  Service Registry:
  
  Check the Service Registry to ensure that the service is registered and available.
  If the service is missing, you may need to register it again.
  
  
  
  System Connectivity:
  
  Verify that the system specified in the error message is up and running and that there are no connectivity issues.
  Check the RFC connections to ensure they are correctly configured and operational.
  
  
  
  Review Transport Requests:
  
  If the configuration was recently transported, review the transport requests to ensure that all necessary objects were included and successfully imported.
  
  
  
  Logs and Traces:
  
  Check the logs and traces in the SAP system for more detailed error messages that may provide additional context for the issue.
  
  
  
  Testing:
  
  After making the necessary changes, test the web service call again to ensure that the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like SOAMANAGER for web service configuration and SXMB_MONI for monitoring messages in PI/PO.
  Documentation: Refer to SAP Help documentation for detailed guidance on configuring web services and troubleshooting common issues.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance.