Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix TN153 - Caution: Upgrade or Prepare is still running; import not allowed


SAP Error Message - Details

  • Message type: E = Error

  • Message class: TN - Support Package Manager (SPAM) Messages

  • Message number: 153

  • Message text: Caution: Upgrade or Prepare is still running; import not allowed

  • Show details Hide details
  • What causes this issue?

    You are upgrading your system. The upgrade is currently in the PREPARE
    phase. You are not allowed to import OCS Packages (add-on
    installations/upgrade, Support Packages) in this phase since this
    changes the system state on which the current upgrade is based.

    System Response

    The import of the OCS queue terminates.

    How to fix this error?

    If the upgrade is in the PREPARE phase, and you have to import the OCS
    queue, proceed as follows:
    Delete the queue by using one of the following:
    Support Package Manager: Choose <ZK>Display/ Define -> Delete Queue</>.
    Add-On Installation Tool: Choose <ZK>Back</>.
    Completely reset PREPARE as described in the upgrade guide.
    Redefine the queue and import it.

    Procedure for System Administrators

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message TN153 - Caution: Upgrade or Prepare is still running; import not allowed ?

    The SAP error message TN153, which states "Caution: Upgrade or Prepare is still running; import not allowed," typically occurs during system upgrades or when performing certain maintenance tasks in the SAP environment. This message indicates that a previous upgrade or preparation process is still in progress, and as a result, no further imports or changes can be made until that process is completed.

    Cause:

    1. Ongoing Upgrade/Preparation: The most common cause is that an upgrade or preparation process is still running in the background. This could be due to a long-running upgrade or a process that has not been completed successfully.
    2. Locking Mechanism: SAP uses a locking mechanism to prevent changes while critical processes are running. If the system detects that an upgrade or preparation is still active, it will block any import attempts.
    3. System Errors: Sometimes, if an upgrade process fails or hangs, it may not release the lock properly, leading to this error.

    Solution:

    1. Check Upgrade Status: Use transaction code SPAM or SAINT to check the status of the upgrade or preparation process. If it is still running, you will need to wait for it to complete.
    2. Monitor Background Jobs: Go to transaction SM37 to check for any background jobs related to the upgrade or preparation. If you find any jobs that are stuck or have failed, you may need to analyze the logs and take appropriate action.
    3. Review Logs: Check the upgrade logs (found in the directory where the upgrade was executed) for any errors or warnings that might indicate why the process is still running or has failed.
    4. Terminate Stuck Processes: If you determine that the upgrade process is stuck and not progressing, you may need to terminate the process. This should be done with caution and typically requires administrative privileges. Use transaction SM50 to find and terminate the process.
    5. Restart the Upgrade: If the upgrade process was terminated, you may need to restart it from the beginning, ensuring that all prerequisites are met and that the system is in a stable state.
    6. Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.

    Related Information:

    • SAP Notes: Always check for relevant SAP Notes that may provide specific guidance or patches related to the error.
    • System Logs: Review system logs (transaction SM21) for any additional errors or warnings that may provide context for the issue.
    • Documentation: Refer to the official SAP upgrade documentation for best practices and troubleshooting steps related to upgrades and system maintenance.

    Important Considerations:

    • Always ensure you have a backup of your system before making any changes or terminating processes.
    • If you are unsure about any steps, consider consulting with your SAP Basis team or SAP support for assistance.
    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:
  • TN152 Queue is inconsistent
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • TN151 Program tp did not execute successfully
    Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...

  • TN154 Error during RFC call
    What causes this issue? An error occurred when executing an RFC module. Return code .....: &V1& Destination .....: &V2& Module .........

  • TN155 File & does not exist
    What causes this issue? The file that you wanted to copy could not be opened. The file probably does not exist. File ........: &V1& Director...

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant