cancel
Showing results for 
Search instead for 
Did you mean: 

SAP logon Failed

Former Member
0 Kudos

Hello Sir

I am using SAP ECC 6.0 ides in my laptop, when i go to logon i typed wrong password and did it again and again, by this my SAP logon failed and shown a message" not able to logon- too many wrong password attempted". Now i have right password with me,but that message shown again and again. Can anyone know how to solve this problem? please help.

B.R

Nishant Kaushik

Accepted Solutions (0)

Answers (1)

Answers (1)

sivakumar_kilari3
Active Contributor
0 Kudos

Login with Following login details

user id : idadmin

password : ides

Thanks

Siva

former_member182034
Active Contributor
0 Kudos
Login with Following login details

user id : idadmin
password : ides

how do you know about this password because it is not standard password.

if sap* locked then execute following commands

SQL> delete sapsr3.USR02 where bname='SAP*' and mandt='client_number';

SQL> COMMIT;

Regards,

Former Member
0 Kudos

Please don't make me confuse frnds, tell me the right path to do. I don't want to make more trouble in it, And don't want to install it again because it take too much time to install it. Please tell me if you know the right commands.

former_member182034
Active Contributor
0 Kudos

niskau,

please follow below procedure.

login with SIDadm
Start -- Run -- sqlplus "/as sysdba"
and execute below command
SQL> delete sapsr3.USR02 where bname='SAP*' and mandt='client_number'; 
sql> commit;

now you can login with SAP*/password

if your query resolve then select Solved Problem and if you still get error then let me know.

Regards,

Former Member
0 Kudos

If you have the right password now, unlock sap* on database level. For Oracle, you do it like this:

sqlplus / as sysdba

select bname,mandt,uflag from sapsr3.usr02 where bname='SAP*';

--> should show a value of 128 for uflag in a row

update sapsr3.usr02 set uflag=0 where mandt='the desired client' and bname='SAP*';

commit;

select bname,mandt,uflag from sapsr3.usr02 where bname='SAP*';

--> should show a value of 0 for uflag now

SAPSR3 is the database scheme, it can be different, you might want to check this in case of problems

If you already have deleted SAP* on database level and still cannot logon do the following:

- in DEFAULT.PFL set

login/no_automatic_user_sapstar = 0 // (if not already set to this)

- Restart the instance so the parameter is active

- logon with SAP* and password PASS

- create SAP* in su01 with profiles sap_all and sap_new

If you do not create the user, anyone will be able to logon in the client for which the user record was deleted with the everywhere-known password PASS with sap_all authorizations if you do not set the parameter above to 1 and restart again.

Edited by: Ulf Brinkmeier on May 20, 2011 10:17 AM

Former Member
0 Kudos

Are you sure that this will work because i don't want to do R&D on it. Because to install it i take someone help and don't want to disturb him anymore. So please confirm me if you are 100% sure. And can you please can you explain it with step by step.

Thanks for your prompt reply.

B.R.

Nishant Kaushik

volker_borowski2
Active Contributor
0 Kudos

Login with Following login details
> 
> user id : idadmin
> password : ides

> how do you know about this password because it is not standard password.

>

Hi,

idadmin/ides is standard for IDES systems.

So if someone else did install the system for you, you can try to login as

SAP* or DDIC with the same password you use for sidadm

(supposing they all did get the installation master password).

With DDIC or SAP* you should be able to unlock IDADMIN.

If nothing else helps, the procedure described above to access the

system with the hard-coded "SAP*" is correct.

Volker

Former Member
0 Kudos

Thnks frnds for your cooperation, but i solved it by using SAP* password after it i put SU01 T code and unlock login. Now i am able to logon in SAP. Thanks again. I hope i will get same kind of response in future if i get problem in SAP.