How To Fix MDMXFW071 - Job &1 with ID number &2 is still running

SAP Error Message - Details

• Message type: E = Error

• Message class: MDMXFW - MDC Extraction Framework

• Message number: 071

• Message text: Job &1 with ID number &2 is still running

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 MDMXFW071 - Job &1 with ID number &2 is still running ?

  The SAP error message MDMXFW071 indicates that a job (specifically, a background job) with a certain ID number is still running. This message typically arises in the context of SAP Master Data Management (MDM) or other related processes where jobs are scheduled to run in the background.
  Cause:
  
  Long-Running Job: The job may be taking longer than expected due to a large volume of data being processed or inefficient processing logic.
  Job Stuck: The job may be stuck due to resource contention, deadlocks, or other issues in the system.
  Job Scheduling Conflicts: There may be conflicts with other jobs that are scheduled to run at the same time, causing delays.
  System Performance Issues: General performance issues in the SAP system can lead to jobs taking longer to complete.
  
  Solution:
  
  Monitor Job Status: Use transaction code SM37 to monitor the status of the job. Check if it is still running, and if so, how long it has been running.
  Analyze Job Logs: Review the job logs for any errors or warnings that might indicate why the job is taking longer than expected.
  Check System Resources: Ensure that the system has adequate resources (CPU, memory, etc.) available. You can use transaction codes like ST02 (buffer management) and ST04 (database performance) to analyze system performance.
  Terminate Job: If the job is stuck and not progressing, you may need to terminate it. This can be done from the job monitoring screen (SM37) by selecting the job and choosing the option to cancel it.
  Re-schedule Job: After terminating, you may want to re-schedule the job during off-peak hours or after optimizing the job parameters.
  Optimize Job Logic: If the job consistently takes too long, consider reviewing and optimizing the underlying logic or data being processed.
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Job Monitoring
  SM21: System Log
  ST22: Dump Analysis
  ST04: Database Performance
  ST02: Buffer Management
  
  
  SAP Notes: Check SAP Notes for any known issues related to the specific job or process you are running. You can search for relevant notes in the SAP Support Portal.
  Performance Tuning: Consider engaging with your SAP Basis team for performance tuning if jobs frequently run longer than expected.
  
  If the issue persists after following these steps, it may be beneficial to consult with SAP support or your internal SAP team for further investigation.