Friday, September 23, 2011

OBIEE 11g Errors- nQSError: 43113, nQSError: 43126, nQSError: 37001


My Environment: Windows 2008 R2, Oracle DB 11gR2, OBIEE 11.1.1.5.0

One fine day no user even administrator was able to log in to OBI. We were receiving the following errors:
Unable to Sign In- An invalid User Name or Password was entered.
When trying to open the repository in online mode, following error messages are received:
nQSError: 43113, nQSError: 43126, nQSError: 37001

We tried everything including redeploying rpd and catalog, refreshing GUIDs, creating new users with Admin privileges, playing around with BI System User, etc. with no success.

NQServer Log:
Error Message For BISystemUser: User not authenticated.
Authentication failed: invalid user/password.

NQ Admin Tool Log:
[nQSError: 43113] Message returned from OBIS.
[nQSError: 43126] Authentication failed: invalid user/password.
[nQSError: 37001] Could not connect to the Oracle BI Server instance.

Presentation Log:
Could not create a system user connection to Oracle BI Server during start-up. Please check the error message and try again.
Authentication Failure.
Odbc driver returned an error (SQLDriverConnectW).
[nQSError: 10018] Access for the requested connection is refused.
[nQSError: 43113] Message returned from OBIS.
[nQSError: 43126] Authentication failed: invalid user/password.

After several hours of debugging we found that our DB schemas/user MDS and BIPLATFORM got locked/ expired. It was a setting in Oracle DB which makes schemas or users lock after a period of time. To check the status of account use:


SELECT USERNAME, ACCOUNT_STATUS FROM DBA_USERS;


You can use the following to unlock accounts:

ALTER USER MDS ACCOUNT UNLOCK;
ALTER USER BIPLATFORM ACCOUNT UNLOCK;

If the password has expired make sure to revert it back to the password you used during installation. Use the following:

ALTER USER MDS IDENTIFIED BY Admin123;
ALTER USER BIPLATFORM IDENTIFIED BY Admin123;

This did the trick and we were able to login to OBI Presentation Services.

Cheers!
Deepak


12 comments:

  1. Deepak,

    Thanx a lot for this blog post.

    I have a question though, is there a way to avoid getting such errors (nQSError: 43126), in short how can we make sure that PWD for MDS as well as BIPLATFORM never expires?

    Regards,
    Jitendra

    ReplyDelete
  2. This was really helpful.. it was exactly my situation!
    Never thought it would be a database issue!
    Excellent hint, Deepak!

    Well, I have another question regarding the user GUIDs that I faced while configuring the security provider.
    I have a migrated 10g environment to 11g just for assessment and checking out the new features.
    I decided to try out the iPhone app. But it doesn't seem to work according to this Doc ID 1349522.1 and it only refers to documentation.

    The thing is, the solution is there, but I couldn't apply it because of my shallow experience with WebLogic.
    Do you have any idea about the proper value to be set in:
    GUID=newvalue

    Appreciating your help!

    ReplyDelete
  3. @Jitendra Bhagwat, HYG

    alter profile default limit password_life_time unlimited;

    copied from:
    http://serverfault.com/questions/37622/how-do-i-turn-off-oracle-password-expiration
    and
    http://blog.darwin-it.nl/2009/04/password-expiry-in-oracle-db-11g.html

    ReplyDelete
    Replies
    1. Hi Martian,

      Sorry for the delayed reply.

      Thanx for the solution.

      Regards,
      Jitendra

      Delete
  4. Thanks for help Deepak, it was exactly my situation too.

    ReplyDelete
  5. Hi Deepak,

    In my case this is not working.. all my databases are in open state they are not locked. but still getting the same error. please help

    Regards,
    Raju

    ReplyDelete
  6. Hi Raju,

    Please double check for MDS and BIPLATFORM schemas.

    Thanks,
    Deepak

    ReplyDelete
  7. Same problem is occurring with me. I have done all the above steps plus both schemas are unlock ,still I am not able to connect to RPD in online mode and login into analytics.
    Please help

    ReplyDelete
    Replies
    1. hi,
      Change the password for the dev_biplatform under deployments->scheduler tab in enterprise manager and click on restart all servers.
      Let me know if still facing the issue.

      Thanks,
      Sandeep

      Delete
    2. Thanks Sandeep a lot! It solved my problem well!!

      Best Regards,
      Gerbera

      Delete
  8. hi Deepa
    we have the same problem as above but not for all users but certain LDAP users, both schema's are unlocked.

    please advise

    ReplyDelete
  9. Hi Elkana,

    Yours looks like a different issue. What error codes are you receiving? Do you have multiple authentication providers? Which users are able to log in?

    Cheers!
    Deepak

    ReplyDelete