How To Fix TG795 - *** RDDAPPSE: Check connected application servers

SAP Error Message - Details

• Message type: E = Error

• Message class: TG - Messages for Upgrade Repository Switch

• Message number: 795

• Message text: *** RDDAPPSE: Check connected application servers

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 TG795 - *** RDDAPPSE: Check connected application servers ?

  The SAP error message TG795, specifically "RDDAPPSE: Check connected application servers," typically indicates an issue with the connection between the SAP application server and the database or other application servers. This error can arise due to various reasons, including network issues, configuration problems, or server downtime.
  Causes:
  
  Network Issues: There may be network connectivity problems between the application server and the database or other application servers.
  Server Downtime: One or more application servers may be down or not responding.
  Configuration Errors: Incorrect configuration settings in the SAP system, such as incorrect instance profiles or parameters.
  Resource Limitations: The application server may be overloaded or running out of resources (CPU, memory).
  Database Issues: Problems with the database itself, such as being down or unreachable.
  
  Solutions:
  
  Check Server Status: Verify that all application servers are up and running. You can do this using transaction codes like SM51 to check the status of application servers.
  Network Connectivity: Ensure that there are no network issues. You can use tools like ping or traceroute to check connectivity between servers.
  Review Configuration: Check the configuration settings in the instance profiles and ensure that they are correctly set up. Look for any discrepancies in the instance profile or SAP router settings.
  Monitor Resources: Use transaction SM04 or ST06 to monitor resource usage on the application servers. If the server is overloaded, consider optimizing performance or scaling resources.
  Database Check: Ensure that the database is running and accessible. You can check the database logs for any errors or issues.
  Restart Services: If necessary, restart the affected application servers or services to resolve temporary issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM51 (to check application servers), SM04 (to monitor user sessions), ST22 (to check dumps), and SM21 (to view system logs).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Logs: Review the system logs (SM21) and developer traces (ST11) for any additional error messages or warnings that could provide more context about the issue.
  
  If the problem persists after following these steps, it may be necessary to engage SAP support for further assistance.