Skip to Content
avatar image
Former Member

j2ee_adm_sid lock freqrently in ECC while login in EP Portal

Hi

We are using EP 7.0 and ECC 6.0

j2ee_aadm_sid is frequently lock in ECC side while login to EP portal,

i tried all the steps to unlock and reset the password of id but not working.

also i checked the user id in idenetity management in portal but no issue found.

all the helps in SDN i tried but no luck.

also i create id and assign all the roles and group as in j2ee_adm_sid and apply setting in configtool and VA.

but still facing the same issue.

also i activite the trace of RFC but no issue traced and in sm20 sapjsf login fail with message Logon Failed (Reason = 53, Type = U)

as sapjsf is assign in identidy management as communication id in r/3 end also i try to reset the password of sapjsf and give new password still same error.

please help for this issue as the EP is not working from last 4 days and i am trying to resolve.

Thanks

Naveen

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 20, 2015 at 11:09 AM

    Dear All,

    Thanks for the valuable support and suggestion after long time to spend we find there is a user id maintained in

    JCO RFC METADATA

    in modeldata SSO was mentioned and in Metadata USER PASSWORD was missing

    we give the correct password and EP is working without locking the id.

    Thanks and Regards

    Naveen

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Hemanth Kumar

      Hi Hemanth,

      There was an old configuration. yes we use different user id for best practice and also noted down.

      Thanks to all for suggestion.

      Regards

      Naveen

  • Oct 19, 2015 at 01:19 PM

    Hi Naveen,


    Hope you are doing good.

    Such locking issues are usually very complicated cause the J2EE server may interact with many external/ABAP server etc(using JCo destinations, JCo RFC destinations, system connection, /nSM59 connections), and if the password is set wrongly in one place and calls are made, then after a particular number of tries, the user will get locked.

    Please go through SAP Note 1493272 throughly and the attachment

    LocationGuide.zip that contains the "How to create a new trace location

    in NW 7.10 and above.doc" document which shows how you NEED to create

    the "com.sap.security.userlocking". This won't be existing on your

    system; you need to create it.

    After this check all the possibilities mentioned in the note.

    Knd regards,
    Hemanth
    SAP AGS

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 17, 2015 at 01:21 PM

    Hi Naveen

    Could you refer the SAP KBA with Case 9

    2113395 - Supportdesk Tool RED signal checking trouble shooting guide

    BR

    SS

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 19, 2015 at 07:43 AM

    Hello Naveen,

    Please check the below link and see if the solution provided by Sebastian Merlo works for you

    https://scn.sap.com/thread/175751

    Thanks.

    Best Regards,

    Anita

    Add comment
    10|10000 characters needed characters exceeded