Sunday 21 July 2013

OBIEE11G : "Unable to Sign in. An error occured during Authentication" Error When A User Logs In OBIEE

The purpose of this Post is to provide steps to troubleshoot "Unable to Sign in. An error occurred during Authentication. Try again later or contact your system administrator" errors when a user logs in to Oracle Business Intelligence Enterprise Edition (OBIEE)11g. 
NOTE: You may not need to complete all steps (i.e. Step A, Step B, C.).  After completing all sub-tasks in each stepped section, please retest login and if the login still fails, then proceed to the next step.

 I found a simple way to fix this issue by following the below steps.

 1) Open the RPD in the Offline mode
2) Manage --> Identity--> Check for the user name with what user your trying to login into presentation services (Analytics), For example if you are using weblogic user to login to Analytics then search for weblogic user in rpd opened in offline mode. 
3) Delete the user (in our example weblogic) from the offline RPD and save the RPD.
4) Deploy this rpd in to BI Server and restart the services. 

 Note : Restarting of all the services is recommended.
5) Now try to login with the weblogic user , now you can see the user is able to successfully login.

The issue is with the GUID. It is always recommended to check the user references in the offline rpd before deploying it. If you find any of the users in offline mode,delete them and save the RPD then deploy it.

Step A: Refreshing GUIDs (or Regenerating User GUIDs)


  1. Check to see if any error messages regarding GUID mismatch is seen in the sawlog located in \OBI11g\instances\instance3\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1 folder/directory.
  2. If yes, follow steps to refresh GUID as documented in Section 3.2.7 "Regenerating User GUIDs" of the Oracle Fusion Middleware Administrator's Guide.
  3. After completing step 2, login to OBIEE as the problematic user to verify if you still encounter any login errors.

Step B: Delete user from Repository (RPD) file,  if present


  1. Launch admin tool and open RPD in OFFLINE Mode.
  2. Click Manage -> Identity -> Users tab to verify if you see this user present
    Note : Normally you will only see list of users when you open RPD in ONLINE mode. Unless the users were created manually in RPD, no users should be visible in OFFLINE mode.
  3. If the user is present, delete this user entry from RPD.
  4. Save RPD and deploy this changed RPD using EM.
  5. Restart OBI Server component.
  6. Re-login as the problematic user to see if you still encounter log in error.

Step C: Delete the cacheduserinfo files from webcatalog

If login errors persist after completing Step A and Step B above, then complete the following.



Note : In the illustration example below, the catalog name is "SampleApp" and the user who gets "Iœnvalid Login" error is the "Administrator" user.



  1. Take a backup of your webcatalog.
  2. Navigate to \OBIEE11G\instances\instance2\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog\SampleApp\root\users\Administrator\_prefs
  3. Delete the files named "cacheduserinfo" and "cacheduserinfo.atr."
  4. Open web browser and retest OBIEE 11g login for that user.


Note :

1. The cacheduserinfo and cacheduserinfo.atr files get automatically recreated when the user logs in next time
Posted by at

11 comments:

  1. Kanthi2 October 2013 at 21:32

    Did you figure out what the root cause was? I could not observe a pattern with our end users who had this issue?

    ReplyDelete
  2. Venkata Nagarjuna2 October 2013 at 23:57

    Hi Kanthi,

    Can you elaborate on the issue?

    Thanks,
    Nagarjuna

    ReplyDelete
  3. Kanthi3 October 2013 at 16:41

    Issue is that our end users sometimes face the same error. We resolve these issues however. My intention is to find the root cause of this problem. We generally ask a standard set of questions to our users such as - if there were any system updates which ran on their computers, if they were issuing the correct password, version of the browser, etc.
    As I see the responses, I did not find any common pattern among all these instances.

    I am more curious about the reason why user folders/files are corrupted on the web catalog. My intention is to prevent these issues if possible, than spending time to resolve.

    Hope this is clear.

    Thanks.

    ReplyDelete
  4. Venkata Nagarjuna3 October 2013 at 20:35

    Hi Kanthi,

    We will run in to these kind of issues in following scenarios...

    1) User entered wrong password for more than 5 times

    2) When we deploy a new RPD where the GUID is not updated

    3) When an existing user reference is present in the Offline RPD

    4) When ever the security files got screwed up (Identity store and credential store)

    5) After applying a patch to upgrade the version but the security jar file is unable to communicate to admin server

    Thanks,
    Nagarjuna

    ReplyDelete
  5. Kanthi4 October 2013 at 05:30

    Thanks a lot. I believe above reasons may also some other inconsistencies such as user unable to view all the tabs that he/she should have access to.
    We are currently struggling to resolve this issue. This may trigger a whole new thread, but if you can help...that will be awesome.

    ReplyDelete
  6. Santhosh5 February 2016 at 12:07

    worked for me when I deleted cacheduserinfo and cacheduserinfo.atr files from weblogic.

    Thanks

    ReplyDelete
  7. Venkata Nagarjuna5 February 2016 at 21:14

    Hi Santhosh,

    Thanks for sharing your feedback.

    Thanks,
    Nagarjuna

    ReplyDelete
  8. STAR2811 February 2016 at 21:19

    Hi Venkata

    I tried step A, for some reason, my system is not writing the logs, so am not getting the errror messages.
    Step B, I could not find the weblogic user, at all from the RPD.
    Step C, the files have been deleted.

    I am still unable to login to analytics.

    However,I looked at your list of scenarios, and I believe the cause of my issue is from security files being screwed up(Identity store and credential store)
    because this issue started after I was enabling the SSL that did not go well.....

    How do I fix these files, please help.

    ReplyDelete
  9. Unknown17 February 2017 at 14:07

    Worked for me when i deleted weblogic user in administration tool. Thank you!

    ReplyDelete
  10. Unknown8 August 2017 at 14:34

    Step 1 did work in my case, but with different user defined locally.

    ReplyDelete
    Replies
    1. Venkata Nagarjuna9 August 2017 at 19:15

      Hi Ali,

      Thanks for your feedback.

      Thanks,
      Nagarjuna

      Delete

Subscribe to: Post Comments (Atom)