How To Fix GW668 - R/2 was restarted; log on again

SAP Error Message - Details

• Message type: E = Error

• Message class: GW - Message Texts for Gateway

• Message number: 668

• Message text: R/2 was restarted; log on again

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 GW668 - R/2 was restarted; log on again ?

  The SAP error message GW668 indicates that the R/2 system has been restarted, and the user needs to log on again. This message typically occurs in environments where SAP R/2 is integrated with other systems or when there are issues with the connection to the R/2 system.
  Causes:
  
  System Restart: The R/2 system may have been restarted for maintenance, updates, or due to a crash.
  Network Issues: Temporary network disruptions can cause the connection to the R/2 system to drop, leading to this error.
  Session Timeout: If the user session has been inactive for a certain period, it may time out, prompting the need to log in again.
  Configuration Changes: Changes in system configuration or updates may require users to re-establish their sessions.
  Resource Limitations: If the server is under heavy load or has resource limitations, it may restart unexpectedly.
  
  Solutions:
  
  Log On Again: The immediate solution is to log on to the R/2 system again. This is often the simplest and quickest fix.
  Check System Status: Verify if the R/2 system is up and running. You may need to contact your system administrator to check the status of the server.
  Network Connectivity: Ensure that there are no network issues affecting connectivity to the R/2 system. Check your network connection and try again.
  Session Management: If session timeouts are frequent, consider discussing with your system administrator about adjusting session timeout settings.
  Monitor System Performance: If the issue persists, monitor the system for performance issues or resource limitations that may be causing restarts.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  System Logs: Review system logs for any errors or warnings that occurred around the time of the restart to identify potential causes.
  User Training: Ensure that users are trained on how to handle session timeouts and what to do in case of unexpected logouts.
  
  If the problem continues after trying the above solutions, it may be necessary to escalate the issue to your IT support team or SAP support for further investigation.