How To Fix MSG_CL_ER070 - Services Registry connections with Proxy Class '&1' or '&2' allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: MSG_CL_ER - Message Class for Enterprise Registry

• Message number: 070

• Message text: Services Registry connections with Proxy Class '&1' or '&2' allowed

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 MSG_CL_ER070 - Services Registry connections with Proxy Class '&1' or '&2' allowed ?

  The SAP error message MSG_CL_ER070 indicates that there is an issue with the configuration of the Services Registry connections, specifically related to the use of proxy classes. This error typically arises when the system is trying to establish a connection to a service registry but encounters restrictions based on the proxy class settings.
  Cause:
  The error message suggests that the connection to the Services Registry is being attempted using a proxy class that is not allowed. This can happen due to several reasons:
  
  Incorrect Proxy Class Configuration: The proxy class being used may not be configured correctly in the SAP system.
  Authorization Issues: The user or service account attempting to make the connection may not have the necessary authorizations to use the specified proxy class.
  System Settings: The system may have restrictions on which proxy classes are permitted for use in service registry connections.
  
  Solution:
  To resolve the MSG_CL_ER070 error, you can follow these steps:
  
  
  Check Proxy Class Configuration:
  
  Go to the transaction code SOAMANAGER in your SAP system.
  Navigate to the "Service Registry" settings and verify the proxy class configuration.
  Ensure that the proxy class you are trying to use is correctly defined and active.
  
  
  
  Review Authorization:
  
  Ensure that the user or service account has the necessary authorizations to access the proxy class.
  Check the roles and authorizations assigned to the user and make adjustments as necessary.
  
  
  
  Modify System Settings:
  
  If there are restrictions on the proxy classes that can be used, you may need to modify these settings.
  Consult with your SAP Basis team or system administrator to review the system configuration and make any necessary changes.
  
  
  
  Check for Updates:
  
  Ensure that your SAP system is up to date with the latest patches and updates, as this can sometimes resolve underlying issues.
  
  
  
  Consult Documentation:
  
  Refer to the official SAP documentation or support notes related to the Services Registry and proxy classes for additional guidance.
  
  
  
  Related Information:
  
  Transaction Codes: SOAMANAGER (Service Orientation Architecture Manager), SE80 (Object Navigator), and SU01 (User Maintenance) may be useful for troubleshooting.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Community Forums: Consider checking SAP Community forums or other online resources where similar issues may have been discussed.
  
  If the issue persists after following these steps, it may be beneficial to engage SAP support for further assistance.