SAP Messages

SAP message number 006 within class STRALAN_MSAG - Could not lock language (ENQUEUE)








Messsage Text for 006(STRALAN_MSAG)

Could not lock language (ENQUEUE)


What causes this issue?
Before a new action is executed, an attempt is made to set an ENQUEUE lock on the language. This is meant to prevent multiple actions from editing the same language at the same time.
For example, problems can arise if a language is being supplemented and a language package is being imported at the same time.

System Response
The system stops the action from being executed.

How to fix the issue?
Check all actions that are running. You can start a new action for a language only when all currently running actions have been completed. You can access all running jobs easily from Transaction SMLT.
You can also use Transaction SM37 to administrate all language transport jobs. All jobs start with the prefix SAP-LANGUAGE.
In rare cases, an unexpected event may keep a lock, even though the corresponding process is no longer active. If this is the case, use Transaction SM12 (for table T002C) to delete the lock manually.






ABAP Code to add mesage to own reports


MESSAGE W006(STRALAN_MSAG). "warning message
MESSAGE E006(STRALAN_MSAG). "Error message
--> See here for more options


Contribute (Add Comments)

Use the comments section below to add any links, information or screen shots that you feel are relevant to this message. This could include issues you have found that cause the messages to appear incorrectly as well as any fixes you have found or relevant SAP OSS notes. You will then be able to find this information quickly, simply by searching on the message class STRALAN_MSAG and number 006



Return to Message Class STRALAN_MSAG