Locking of user ids

[Former Member]

Hi, I am facing the situation in AS abap system, one of dialog work processes is in status of running state(it is not changing to wait state), in MMC it is showing a name of SAP program. All the users are getting locked except one user. What could be possible reason, is it can be a program which can cause one of the dialog work process to be in run state?

[Former Member · Accepted solution]

Hi,

A WP could be in status "running" for a long time, it depends on what this WP is executing. This is not a problem itself. What's the name of the SAP program you are talking about? is a job running in SM37?? you can also check in SM50 ->process->details for more information about the SQL sentence executing if this is the case.

You wrote: "All the users are getting locked except one user." do you mean that you lock all users or the users just get locked without reason? Just to give you an example.. if the license is expired, you can log on to system only with user SAP*

Cheers,

Diego.

[Former Member]

Hi all,

Finally the issue has been solved. Logoff bomb was created a developer by changing a SAP program.

We figured it out and commented the logoff lines.

Thanks & Regards,

Abhishek Kalra

[former_member204080]

Hi,

The Wp will be in running state if any Background job is running because some internally uses Dialog Wp.So kindly go through the active jobs and Cancel that .

May be the user id with which the job is scheduled is the user which is not locked right if not pls mention the id which is not locked

[former_member188883]

Hi Abhi,

Can you kill this process using SM50. Process->Cancel without core.

It seems that process is hanged.

Regards,

Deepak Kori

[Former Member]

Hello Abhi,

It could be a hung user session. Usually if runtime of dialog process is beyond the value of rdisp/max_wprun_time, that work process should be released and status should be Waiting.

If you want to determine hung dialog session, please do the steps as follows.

1. Go to SM04 on particular app server

2. Select the entire row of that particular user session.

3. User --> Technical Information.

If you see STATE as DISCONNECTED, then it's hung process and you can safely terminate the session from SM50.

Note: Please check before it's there any corresponding background job running in the system. Check SM12 as well.

Hope it helps.

Thanks,

Siva Kumar