SMLT ( language is locked: you cannot perform this action)

[Former Member]

Hi Experts,

I want to restart the my failed langauge import. But it gives me the above error.

How do I restart my import?

Regards

Prashant

[muzavor · Accepted solution]

Hi Everyone,

I know this an old post but is referenced by many to view the solution.

I came across this solution in one of the forums related to SAP and it helped me out when I encountered the issue of "Language locked".

The solution was provided by Huub Hellings

Solution:

Run SMLT

Enter "abortimp" in the command field and press the ENTER button.

Once the above steps are performed one can scheduled a new task. We cannot use the import task with "X"

Hope the above helps all those who encounter this issue.

Regards

Arshad

[Former Member · Accepted solution]

I ran that command and that sole my problem.

Enter "abortimp" in the command field and press the ENTER button.

Thanks,

José

[Former Member · Accepted solution]

Yes, it works for ecc6+ehp7 install

[bobbidonna_boyd]

FYI.

There is another way to delete the lock flag.

Go to STMS_IMPORT

Click on the Import Monitor

Find the job that is executing. Delete the job.

Go back to SMLT.

Reload the package and start the import again.

[wen_vincent]

It work !

[Former Member]

Hi,

Here are a few tips.

1) Make absolutely sure that no language transports are recorded in TPSTAT. I know you looked at TPSTAT earlier, but just double-check for any entries with COMMAND = 'IMPORT' and TRKORR like 'SAPKL%'. If such entries exist, delete them.

2) If your Basis 7.00 Support Package is < 13, then consider note 1064502

3) You can also reset the lock as follows: call STMS and in the command window (the top left field where you type transaction codes), enter ABORTIMP

Let me know how this goes.

Rgds,

Mark

[Former Member]

Dear Experts,

Any suggestions?

Regards

[Former Member]

Experts,

Any suggestions??

Regards

[shlomi_ambar]

Hi

Use transaction SM50 to terminate the background processes of the language transport.

Reset the lock indicator in transaction SMLT (alternatively: transaction SM12)

Good luck

Shlomi

[Former Member]

Hi,

I donot see any indicator( Reset the lock indicator in transaction SMLT ) as mentioned by you.

Also could not find anything in sm12 nor sm50, because I had schedule this a month back, which was failed due to some oracle error.

Now I want to reschedule it again, but again getting same error.

I have see TPSTAT table, but could not see any language related thing.

Any suggestion?

[Former Member]

Please read the note [1064502|https://service.sap.com/sap/support/notes/1064502] and see if it is relevant for you.

It is about a program error (reads TPSTAT in the wrong way).

[Former Member]

Hi Tomas,

Thanks for your reply.

I have checked TPSTAT but could not find any of the SAPK* requests nor any blank timestamp as per the note mentioned.

I got another thing , table PAT03, which has that request SAPK* ( the import request), and need to delete it. But it does not give option to delete. se11, se16 and sm30 does not give any option for deleting the rows from PAT03.

Does deleting the row from PAT03 will work? But how to delete the rows from PAT03. I have registered the object and got the key, but no delete option.

Any suggestion?

Regards

[antonio_voce]

ummary

Symptom

Language import locked

Additional key words

Language import, Upgrade

Cause and prerequisites

Scheduling of a language import is terminated with the error message

1. "No action is currently possible, as a previous action is still running" (start via SMLT)

2. "Import refused; there are jobs that are not yet processed" (start via SMLT)

3. "Language Transport Utility locked. Administrator is active" (start via SMLT)

4. "IMPORT_LOCK: language import is locked" (when called from R3up).

The following causes exist:

1. A previous language import terminated. In this case, the lock flag could not be reset.

2. The scheduling module found active or released language import jobs. Before any further scheduling can take place, you must check whether it is necessary to cancel the available jobs.

3. The transaction found that another user is scheduling a language import at the same time. It is not possible to schedule two language import jobs at the same time.

4. The scheduling module was started from R3up and recognized one of the two situations described under 1. or 2.

Solution

1. Manually reset the lock flag.

Start transaction SMLT and select

-> Utilities -> Reset lock flag

2. Use transaction SM37 to check whether language import jobs are released or active.

On the selection screen of SM37, select

Job name = SAP-LANGUAGE-IMPORT*

User = *

Start after event = *

Jobs without start date = X

Jobs with previous job = X

For active jobs, check whether the status is correct.

If the released / active jobs are no longer running, delete the jobs or set the jobs to cancelled.

3. No further action is necessary.

4. Proceed as described under 1. and 2.

[Former Member]

Hi Antonio,

The procedure you mentioned does work.

1. Manually reset the lock flag.

Start transaction SMLT and select

-> Utilities -> Reset lock flag

_ There is nothing in the Utilities tab. I am working on ECC6_

2. Use transaction SM37 to check whether language import jobs are released or active.

On the selection screen of SM37, select

Job name = SAP-LANGUAGE-IMPORT*

User = *

Start after event = *

Jobs without start date = X

Jobs with previous job = X

For active jobs, check whether the status is correct.

If the released / active jobs are no longer running, delete the jobs or set the jobs to cancelled.

_ There is not such job present. The import failed almost a week back and was restarted many times. So no such job would exist_

3. No further action is necessary.

_ What action is required?_

4. Proceed as described under 1. and 2.

_ Step1 and 2 does not work_

Any suggestion.

Regards

Prashant

[antonio_voce]

Hi ,

give us more detailed info about the error ( more log ).

This error is too much generic.

[Former Member]

Hi Antonio,

There is no specific log with the error. When double clicked on the error, it says something abt inconsistency of TPSTAT. But I found nothing in that......no entries on SAPK*(language installation).

Whatever you mentioned, was as per the note, but I think with ECC6 it differs.

Regards