How To Fix RSM1079 - InfoPackage & currently running; no further scheduling possible

RSM1079 - Overview

• Message type: E = Error

• Message class: RSM1 - Messages for AWB, Scheduler and Monitor (new)

• Message number: 079

• Message text: InfoPackage & currently running; no further scheduling possible

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 RSM1079 - InfoPackage & currently running; no further scheduling possible ?

  The SAP error message RSM1079 indicates that an InfoPackage is currently running, and as a result, no further scheduling of that InfoPackage is possible until the current execution is completed. This is a common issue in SAP BW (Business Warehouse) when multiple processes are trying to access the same InfoPackage simultaneously.
  
  Cause:
  
  Concurrent Execution: The InfoPackage is already being executed, either manually or through a scheduled job.
  Long Running Process: The current execution of the InfoPackage is taking longer than expected, which can happen due to large data volumes or performance issues.
  Locking Mechanism: SAP uses a locking mechanism to prevent multiple instances of the same InfoPackage from running at the same time to ensure data integrity.
  
  
  Solution:
  
  
  Check Running Processes:
  
  Go to transaction code SM37 to check the status of the job. Look for the InfoPackage job that is currently running.
  If the job is stuck or taking too long, you may need to analyze the logs