SAP Note 12946 - Put still running, logon not possible

Symptom:

When trying to log onto the R/3 System, the following message appears in the message line:
'Put is still running, logon not possible'.
Users DDIC and SAP* however are able to log on.

Cause and prerequisites

There are two possible causes:

1. A PUT is actually running at the moment, that is, a 'tp put' call.

2. A 'tp put' call terminated.

Solution

1. No action can be taken. A logon is prevented during a 'tp put' call for security reasons.

2. If you are quite sure that the 'tp put' call could not run to the end, and that the system should nonetheless be accessible to everyone, you can release this lock with the following command on operating system level. First make sure that the present directory is the 'bin' sub-directory of the transport directory (for the SAP upgrade the PUT directory). Then call tp unlocksys

where

is the name of the system which is locked for the logon. For a 'tp put' call, the system alterability is normally set to 'non-alterable'. You should check this with Transaction STME (as of Release 3.0 the Transaction is SE03) under user DDIC, and reset it to the required value if necessary.

Caution: If the 'tp put' call is still running, or if it terminated in an inconsistent status, and changes are then made to the development environment in the system, the result may be irreparable damage. Exercise caution when using the unlock 'tp' call. Note that there is also the corresponding lock call ('tp locksys ').

Additional key words

TR900, R3SLTRATP, R3SLPUT, locked