How To Fix XMS_ADM361 - Repeat terminated copy job first

XMS_ADM361 - Overview

• Message type: E = Error

• Message class: XMS_ADM - XMS - Administration

• Message number: 361

• Message text: Repeat terminated copy job first

What causes this issue?

A conflict situation arose during an attempt to start a background job
that processes the tables of the persistence layer.

System Response

The last copy job was not completed successfully. The copy job will be
executed once the switch procedure for deleting the processed XML
messages is implemented and the tables have been reorganized (see also
<DS:TX.SXMB_CONF_SWITCH>Switch Procedure</>).
Until the problem is resolved, no background jobs for the persistence
layer can be started.

How to fix this error?

Call transaction SXMB_MONI and choose <ZK>Job Overview</>. Repeat the
incomplete job. If the job cannot be completed due to database errors,
first correct the database errors, and then repeat the job again.

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 XMS_ADM361 - Repeat terminated copy job first ?

  The SAP error message XMS_ADM361 ("Repeat terminated copy job first") typically occurs in the context of the SAP Landscape Management (LaMa) or during the execution of a copy job in the SAP system. This error indicates that a previous copy job was terminated and needs to be addressed before you can initiate a new copy job.
  
  Cause:
  
  Job Termination: The most common cause of this error is that a previous copy job was terminated unexpectedly, either due to a system error, resource issues, or manual intervention.
  Incomplete Job State: The system may still be in a state where it recognizes the previous job as incomplete, preventing new jobs from being initiated.
  Locking Issues: There may be locks in the system that are preventing the new job from starting.
  
  
  Solution:
  
  Check Job Status: Go to the job monitoring transaction (e.g., SM37) to check the status of the terminated copy job. Look for any logs or messages that