How To Fix /STMC/CR_MSG118 - Error while recording statistics; subcomponent &1 not started

SAP Error Message - Details

• Message type: E = Error

• Message class: /STMC/CR_MSG -

• Message number: 118

• Message text: Error while recording statistics; subcomponent &1 not started

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 /STMC/CR_MSG118 - Error while recording statistics; subcomponent &1 not started ?

  The SAP error message /STMC/CR_MSG118 indicates that there was an issue while trying to record statistics for a specific subcomponent, which has not been started. This error typically arises in the context of SAP's statistical data collection and monitoring functionalities.
  Cause:
  The error can occur due to several reasons:
  
  Subcomponent Not Initialized: The specific subcomponent that the system is trying to record statistics for has not been initialized or started properly.
  Configuration Issues: There may be configuration issues in the system that prevent the subcomponent from starting.
  Authorization Issues: The user may not have the necessary authorizations to start the subcomponent or to record statistics.
  System Errors: There could be underlying system errors or inconsistencies that are preventing the subcomponent from functioning correctly.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Subcomponent Status:
  
  Verify if the subcomponent in question is running. You can do this by checking the relevant transaction codes or monitoring tools in SAP.
  If it is not running, try to start it manually.
  
  
  
  Review Configuration:
  
  Check the configuration settings for the subcomponent. Ensure that all necessary parameters are set correctly.
  If there are any recent changes to the configuration, consider reverting them to see if that resolves the issue.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to start the subcomponent and to record statistics.
  You may need to consult with your SAP security team to verify and adjust user roles and permissions.
  
  
  
  System Logs:
  
  Review system logs (transaction SM21) for any related error messages or warnings that could provide more context about the issue.
  Check for any dumps in transaction ST22 that might indicate underlying problems.
  
  
  
  Restart the System:
  
  If the issue persists, consider restarting the relevant application server or the entire SAP system, as this can sometimes resolve transient issues.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Contact SAP Support:
  
  If none of the above steps resolve the issue, consider reaching out to SAP Support for further assistance. Provide them with detailed information about the error, including any logs or screenshots.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM21 (System Log), ST22 (Dump Analysis), and ST03N (Workload Analysis) for monitoring and troubleshooting.
  Documentation: Review SAP documentation related to the specific subcomponent and its statistical recording functionalities.
  Community Forums: Check SAP Community forums for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.