00668 - R/2 was restarted (log on again)

SAP Error Message - Details

• Message type: E = Error

• Message class: 00 -

• 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.

AnswerBot

• What is the cause and solution for SAP error message 00668 - R/2 was restarted (log on again) ?

  The SAP error message "00668 R/2 was restarted (log on again)" typically indicates that the SAP system has been restarted or that the session has been terminated unexpectedly. This can happen for various reasons, including system maintenance, server issues, or network problems.
  Causes:
  
  System Restart: The SAP application server may have been restarted for maintenance or due to a crash.
  Network Issues: Temporary network disruptions can cause the connection to the SAP server to drop.
  Timeouts: If a session is idle for too long, it may time out and require a new login.
  Resource Limitations: Insufficient resources (like memory or CPU) on the server can lead to unexpected restarts.
  Configuration Changes: Changes in system configuration or updates can lead to a restart.
  
  Solutions:
  
  Log In Again: The immediate solution is to log in again to the SAP system. This is often the simplest and quickest way to resolve the issue.
  Check System Status: If you have access, check the status of the SAP system to see if it is up and running. You can do this through the SAP Management Console or by contacting your system administrator.
  Network Check: Ensure that your network connection is stable. If you are on a VPN, check the connection and try reconnecting.
  Contact Support: If the issue persists, contact your SAP Basis team or system administrator to investigate the cause of the restart. They can check logs for any errors or issues that may have led to the restart.
  Review System Logs: If you have access, review the system logs (transaction SM21) for any errors or warnings that occurred around the time of the restart.
  Monitor Resource Usage: If resource limitations are suspected, monitor the server's performance metrics to identify any bottlenecks.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like SM21 (System Log), SM37 (Job Monitoring), and ST22 (Dump Analysis) to gather more information about the system's status and any errors that may have occurred.
  SAP Notes: Check SAP Notes for any known issues related to your version of SAP that might explain the behavior.
  User Sessions: If multiple users are experiencing the same issue, it may indicate a broader system problem rather than an individual session issue.
  
  If the problem continues to occur frequently, it may require a deeper investigation into the system's configuration and performance.