/CFG/ACTIVATION035 - Activation History Timestamps not written

SAP Error Message - Details

• Message type: E = Error

• Message class: /CFG/ACTIVATION -

• Message number: 035

• Message text: Activation History Timestamps not written

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 /CFG/ACTIVATION035 - Activation History Timestamps not written ?

  The SAP error message /CFG/ACTIVATION035 indicates that the activation history timestamps were not written during the activation of a configuration object. This can occur in various scenarios, particularly when dealing with configuration changes in the SAP system.
  Cause:
  
  Authorization Issues: The user executing the activation may not have the necessary authorizations to write to the activation history.
  System Errors: There may be underlying system issues, such as database connectivity problems or inconsistencies in the configuration data.
  Configuration Errors: The configuration object being activated may have errors or inconsistencies that prevent the activation process from completing successfully.
  Transport Issues: If the configuration was transported from another system, there may be issues with the transport itself that prevent the activation history from being recorded.
  
  Solution:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the activation and write to the activation history. This may involve checking roles and permissions in the SAP system.
  Review System Logs: Check the system logs (transaction SLG1) for any related error messages or warnings that could provide more context about the failure.
  Re-activate the Object: Try to re-activate the configuration object. Sometimes, simply re-attempting the activation can resolve transient issues.
  Check Configuration Consistency: Validate the configuration object for any inconsistencies or errors. Use transaction codes like SPRO to access the configuration settings and ensure everything is set up correctly.
  Database Consistency Check: If there are indications of database issues, consider running database consistency checks or consulting with your database administrator.
  Transport Management: If the issue is related to a transport, check the transport logs and ensure that all necessary objects were included and correctly imported.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for relevant notes in the SAP Support Portal.
  Documentation: Review the SAP documentation for the specific configuration area you are working with to ensure that all prerequisites and steps are followed correctly.
  Community Forums: Consider searching or posting in SAP community forums or discussion groups for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.