Skip to Content

Login Failure: all modules ignored

Hi,

We have recently done system copy of JAVA only instance (EPP). In live environment EPP is frontend for endusers but access all databse i.e. UME and transaction data from PRD (ABAP only system). We have already completed system copy of PRD. Now we were trying to start SAP on SAND-EPP (Copy system) and while doing this getting error - Login Failure: all modules ignored, when logging on with any user including administrator. We are able to logon to configtool only but SDM, Visual admin, portal web page etc. is not getting working. ABAP ystem is running fine separately. When we start VA eror is: java.lang.nullpointerexception.

For Login Failure: all modules ignored; i have followed note 957355. No need to make any change as all the settings as per note were intact. This error is occuring whether userid or password is correct or not. (even for userid: ~!@#$%; Password: ~!@#$%, means no authentication check, error straightaway).

I am able to logon with sap* user and master password in https:// :50001/useradmin/ index.htm after enabling superadmin global setting in ume to true.

Kindly help.

Thanks,

Gaurav

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Feb 23, 2012 at 11:46 AM

    Hi Gurav,

    After perfoming system copy on Java stack , have you executed script for schema name change & user ID changes?

    Check if this note helps:

    Note 1317908 - No login to the J2EE engine possible, user not authorized

    Regards,

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Rupali,

      Thanks. Done.

      Now the story: This note was among my first few checks. Earlier compared both the live and sandbox instance, These settings -

      1. Check the "instance.properties" file located in /usr/sap/<SID>/<instance>/j2ee/cluster - all dispatcher and server nodes must have a Java option "-Djava.security.policy=./java.policy". If it is missing, add it to the corresponding node in the Configtool (instanceXXX -> <node>), save the changes and restart the whole instance. Also, make sure the /dispatcher and /serverX folders contain a file named "java.policy". If this is not true, you must find it (from the JDK vendor) and put it there.

      2. Check the <JDK_HOME>/jre/lib/security folder. It must contain two files named "java.security" and "java.policy" (along with other files). If they are missing you need to reinstall the JDK from scratch.

      were already in both systems. (Verified by using putty). But today I verified again using putty and winscp. In putty it was the same but in winscp there was a mismatch. In both the file icons of "java.security" and "java.policy", there was a red mark on shortcut arrow. these 2 files points to /etc/java14_64/jre/lib/security folder. And most suprizingly there was no directory called "java14_64". Hence existance of "java.security" and "java.policy" files in <JDK_HOME>/jre/lib/security folder was meaningless. Done the needful changes.

      Rgds,

      gaurav

  • Feb 23, 2012 at 09:10 AM

    Hi Gaurav,

    Since you are able to login by SAP* by activating emergency user on Java stack , i would suggest to unlock/reset password all standard users i.e. administrator /J2EE_ADMIN , J2EE_GUEST ,SDM etc.

    Also check data source information of these users , like eariler it was LDAP now changed to UME etc.

    Once you unlock other standard users , disble emergency user and try to access tools from os level Visual admin,JSPM etc and login to portal.

    Let us know if it helps.

    Regards,

    Edited by: Rupali B on Feb 23, 2012 2:41 PM

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Rupali,

      Thanks. I have given this a try but no effect. Infact only guest user was locked, that i unlocked. Observed that SDM is working fine, i am able to logon there.

      I open with all the ideas, suggestions and checks. Please throw.

      Rgds,

      gaurav