EBS R12 Login Page Is Not Coming Up – java.lang.RuntimeException: Guest user/pwd does not exist or match: GUEST/ORACLE


Acual Behavior
E-Business Suite (EBS) Production Instance Login page is not coming up, Instead a blank page is being displayed.

The issue can be reproduced at will with the following steps:
1. Type the EBS URL on browser.
2. It redirects to EBS login page.
3. But a blank page is displayed.

CHANGES

CAUSE
The root cause of the issue is with GUEST User and Password not in sync.

Running the below query, confirmed that GUEST user and password was not in sync

select fnd_web_sec.validate_login(‘GUEST’,’ORACLE’) from dual;

FND_WEB_SEC.VALIDATE_LOGIN(‘GUEST’,’ORACLE’)
——————————————————————————–
N

Run following SQL to see more details on why above SQL reported No

select fnd_message.get from dual;
Also, confirmed with the below error on the oacore log

javax.servlet.ServletException: java.lang.RuntimeException: Guest user/pwd does not exist or match: GUEST/ORACLE

SOLUTION
Please perform the below steps

1. Shutdown the EBS services.

2. The only supported way to change the Guest user password is to update the context variable s_guest_pass and run AutoConfig, which runs the AdminAppServer utility internally.

Note : Restriction on the GUEST User Password : The GUEST User password cannot include the special character “#”.

 3. Run Autoconfig on DB Node and then application node.

4. Execute the below sql again:

select fnd_web_sec.validate_login(‘GUEST’,’ORACLE’) from dual;

Check whether query output is showing Y.

If no,  Please check whether the below error is seen on autoconfig log:

Unable to update GUEST_USER_PWD in database to GUEST/ORACLE – Password was not changed, this point to the DB parameter JAVA_JIT_ENABLED which is set as TRUE.

5. On 11g DB you need to have the below settings for EBS specifically, run the below sql

alter system set JAVA_JIT_ENABLED= FALSE scope = both;
6. Follow the steps 2 and 3 again.

7. Run the below command:

perl $FND_TOP/patch/115/bin/ojspCompile.pl –compile –flush -p 2

7. Check whether the compile completed successfully.

8. Restart the application services.

9. Retest the issue.

10. Migrate the solution to appropriate environments.

Reference :(Doc ID 1673030.1)

  • January 25, 2019 | 22 views
  • Comments