How To Fix SMMSS_ALERTS035 - &1 non-R/3 connections to the R/3 DB

SAP Error Message - Details

• Message type: E = Error

• Message class: SMMSS_ALERTS - Message class for MSSQL rz20 messages

• Message number: 035

• Message text: &1 non-R/3 connections to the R/3 DB

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 SMMSS_ALERTS035 - &1 non-R/3 connections to the R/3 DB ?

  The SAP error message SMMSS_ALERTS035 indicates that there are non-R/3 connections to the R/3 database. This typically means that there are external applications or systems trying to access the SAP R/3 database directly, which is not recommended and can lead to various issues, including performance degradation and data integrity problems.
  Cause:
  
  Direct Database Access: External applications or tools are connecting directly to the SAP R/3 database (e.g., using SQL queries) instead of going through the SAP application layer.
  Configuration Issues: Misconfiguration in the SAP system or in the network settings that allows unauthorized access to the database.
  Legacy Systems: Older systems or custom applications that were designed to connect directly to the database without using the SAP application layer.
  
  Solution:
  
  Identify Non-R/3 Connections: Use database monitoring tools or logs to identify which applications or users are making direct connections to the R/3 database.
  Restrict Access: Implement network security measures to restrict direct access to the database. This can include firewall rules, database user permissions, and network segmentation.
  Use SAP Interfaces: Encourage the use of SAP-provided interfaces (like BAPIs, RFCs, or IDocs) for any external applications that need to interact with the SAP system. This ensures that all interactions go through the application layer, maintaining data integrity and performance.
  Review Configuration: Check the SAP system configuration and database settings to ensure that they are set up correctly to prevent unauthorized access.
  Educate Users: Inform users and developers about the risks associated with direct database access and promote best practices for interacting with the SAP system.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or updates related to this error message.
  Documentation: Review SAP documentation regarding database access and security best practices.
  Monitoring Tools: Utilize SAP Solution Manager or other monitoring tools to keep track of system performance and access patterns.
  
  By addressing the root cause of the error and implementing the recommended solutions, you can mitigate the risks associated with non-R/3 connections to the R/3 database.