How To Fix S1757 - No data 'since startup' for 'all servers', try period = 'today'.

SAP Error Message - Details

• Message type: E = Error

• Message class: S1 - Statistik / SAP-Monitor

• Message number: 757

• Message text: No data 'since startup' for 'all servers', try period = 'today'.

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 S1757 - No data 'since startup' for 'all servers', try period = 'today'. ?

  The SAP error message S1757 "No data 'since startup' for 'all servers', try period = 'today'" typically indicates that the system is unable to retrieve any performance data for the specified time period. This can occur in various contexts, such as when using transaction codes related to performance monitoring or system analysis.
  Causes:
  
  
  No Data Collected: The most common reason for this error is that the system has not collected any performance data since the last startup. This can happen if the monitoring tools or data collection processes are not configured correctly.
  
  
  System Restart: If the SAP system was recently restarted, it may not have accumulated any performance data yet.
  
  
  Data Retention Settings: The data retention settings may be configured in such a way that older data is purged, leaving no data available for the specified time frame.
  
  
  Monitoring Configuration: The monitoring tools (like CCMS or ST03N) may not be properly configured to collect the necessary data.
  
  
  Authorization Issues: There may be authorization issues preventing the retrieval of performance data.
  
  
  Solutions:
  
  
  Check System Status: Verify if the system has been restarted recently. If so, wait for a while to allow the system to collect performance data.
  
  
  Review Monitoring Configuration: Ensure that the monitoring tools are correctly configured to collect and store performance data. Check the settings in transaction codes like RZ20 (CCMS Monitoring) or ST03N (Workload Analysis).
  
  
  Data Collection Settings: Check the data collection settings in the SAP system. Ensure that the necessary data collection jobs are scheduled and running.
  
  
  Increase Data Retention: If data retention settings are too aggressive, consider adjusting them to retain data for a longer period.
  
  
  Check Authorizations: Ensure that the user has the necessary authorizations to access performance data. This may involve checking roles and permissions in the SAP system.
  
  
  Use Alternative Time Periods: If you are looking for data for "today," try expanding the time frame to see if data is available for previous days.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ST03N (Workload Analysis), ST04 (Database Performance Analysis), and RZ20 (CCMS Monitoring).
  SAP Notes: Check SAP Notes for any known issues or patches related to performance monitoring and data collection.
  Documentation: Review SAP documentation on performance monitoring and data collection to ensure best practices are being followed.
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.