Diagnosis
This message can occur when there are competing write accesses to statustables. For status changes, the system locks entries in the statustables exclusively for a short timeframe, so that multiple users cannotsimultaneously change the task status.

Procedure
This case should not occur, or only very rarely occur, in liveoperations. In particular, this can only occur when many userssimultaneously access the status tables (for example, during datacollection).
If in doubt, repeat the task execution or the save operation.
If an exclusive write lock persists more than a few minutes and thismessage reappears or appears constantly, then most likely astatus-writing process has been terminated (due to external factors)while this process was exclusively locking the status table.
In this case, delete the lock entry manually using transaction SM12. Tofind the lock entry, search for table name "RSTAB" using lock argument"MON" and leave the user name field blank.