Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

external debugging: user is locked

Former Member
0 Likes
2,094

Hi All,

I am trying to enable external debugging for my username. It is giving the message 'User is locked'. I can enable external debugging with other usernames.

Please advise.

Regards,

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,556

Hi there,

Basically you will need to manualy set the value USR02-UFLAG to 0 for your user that does not work. I think the problem is fundimentally with SAP's function module 'SUSR_CHECK_DEBUG_ABILITY' which assumes if there is any value in the UFLAG field the user is locked. This is incorrect as i believe 3 is a valid number or it used to be, representing the number of times locked or somthing like that. In anycase setting the value to 0 or deleting and re-creating the user should solve your problem.

Regards

Martin

<a href="http://www.sapdev.co.uk">SAP Development using ABAP, ABAP OO, BSP, Web dynpro…</a>

9 REPLIES 9
Read only

former_member189059
Active Contributor
0 Likes
1,556

A user gets locked after too many failed login attempts

ensure that your username and password are correct first

then unlock the user from transaction SU01

Read only

Former Member
0 Likes
1,556

Hi there,

The user is not locked as I am logged in with the user name. In SU01 the user is not locked also. Only for externel debugging it is displaying 'User is locked'.

Please advise.

Regards,

FS

Read only

Former Member
0 Likes
1,556

hi

good

ya you can enalble that,or you can delete that user name who has locked that by the basis help,than you can use it using your username.

thanks

mrutyun^

Read only

Former Member
0 Likes
1,556

Hi mrutyum,

Can you please explain the steps that should be followed. I have checked from the basis team and they are suggesting that user is not locked and they unlocked it in solution manager just in case to verify. Only for external debugging, it is displaying user as locked.

Please advise.

Regards,

fs

Read only

0 Likes
1,556

My colleague is getting this same problem,

He can log into the SAP system as normal but when he tries to create an external break-point within a program, it is created greyed out and says the user is locked. But if i log in with my user name and create and external break-point it works fine. Any help in this matter would be greatly appreciated!

Regards

Mart

Read only

0 Likes
1,556

I have found the source of the problem, when trying to active an external break-point for the specified user it runs function module 'SUSR_CHECK_DEBUG_ABILITY' which returns exception 3 'user locked, due to an entry within table usr02. The problem entry in my case is field UFLAG which for the the user that works is '0' and the user that does not work is '3'. If you set this value to 0 im guessing it will work but could do with finding out what lock status 3 means and unlocking it properly! i will keep looking!

Regards

Mart

Read only

0 Likes
1,556

HI ,

I had the same problem. I deleted the user id from the system and created it again. then I was able to create the external breakpoint. Need to find the root cause of the problem.

With Regards,

Ranganathan.

Read only

Former Member
0 Likes
1,557

Hi there,

Basically you will need to manualy set the value USR02-UFLAG to 0 for your user that does not work. I think the problem is fundimentally with SAP's function module 'SUSR_CHECK_DEBUG_ABILITY' which assumes if there is any value in the UFLAG field the user is locked. This is incorrect as i believe 3 is a valid number or it used to be, representing the number of times locked or somthing like that. In anycase setting the value to 0 or deleting and re-creating the user should solve your problem.

Regards

Martin

<a href="http://www.sapdev.co.uk">SAP Development using ABAP, ABAP OO, BSP, Web dynpro…</a>

Read only

Former Member
0 Likes
1,556

I deleted and created the user again and that solved the problem.