How To Fix /CFG/FTI_BUSN_ERROR036 - The system is currently activating. Try again later

SAP Error Message - Details

• Message type: E = Error

• Message class: /CFG/FTI_BUSN_ERROR -

• Message number: 036

• Message text: The system is currently activating. Try again later

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 /CFG/FTI_BUSN_ERROR036 - The system is currently activating. Try again later ?

  The SAP error message /CFG/FTI_BUSN_ERROR036 indicates that the system is currently in the process of activating a configuration or a business function, and therefore, the requested action cannot be completed at that moment. This is a common scenario in SAP systems when changes are being made, and the system is not yet ready to accept new requests.
  Cause:
  
  Ongoing Activation Process: The most common cause is that a previous activation process is still running. This could be due to a configuration change, a business function activation, or a transport request that is being processed.
  System Lock: The system may be locked for maintenance or updates, preventing any new changes or requests from being processed.
  Long-running Processes: Sometimes, the activation process can take longer than expected due to system performance issues or complexity of the changes being made.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for a few minutes and then try the action again. The activation process may complete shortly.
  Check Activation Status: You can check the status of the activation process in transaction SM37 (Job Monitoring) to see if there are any long-running jobs related to the activation.
  System Logs: Review the system logs (transaction SM21) for any errors or warnings that might indicate why the activation is taking longer than expected.
  Transaction SM12: Check for any locks in the system using transaction SM12. If there are locks that are preventing the activation from completing, you may need to resolve those.
  Contact Basis Team: If the issue persists and you cannot identify the cause, it may be necessary to contact your SAP Basis team for assistance. They can provide insights into system performance and any ongoing processes that might be affecting the activation.
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Job Monitoring
  SM21: System Log
  SM12: Lock Entries
  
  
  SAP Notes: Check for any relevant SAP Notes that might address known issues related to activation processes.
  System Performance: If activation processes are frequently taking too long, it may be worth investigating the overall performance of the SAP system, including database performance and system resources.
  
  By following these steps, you should be able to resolve the error or at least understand the underlying issue causing the activation delay.