OBIEE 11g Login Fails With 'Unable to Sign In ..' In The UI And " [nQSError: 46164] HTTP Server returned 404 (Not Found) for URL" In The nqsserver.log (Doc ID 1629981.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.7.1 and later
Business Intelligence Suite Enterprise Edition - Version 11.1.1.7.1 and later
Information in this document applies to any platform.

Symptoms

You have installed OBIEE 11g,
When you log in, you get the error:

Unable to Sign In. An invalid User Name or Password was entered.

When you look in nqsserver.log, you see the following error:

[2014-xx-xxT15:43:37.000-08:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: 1] An error message was received from the BI Security Service: [nQSError: 46164] HTTP Server returned 404 (Not Found) for URL .
[2014-xx-xxT15:43:37.000-08:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: 1]  [13026] Error in getting roles from BI Security Service:  'An error message was received from the BI Security Service: [nQSError: 46164] HTTP Server returned 404 (Not Found) for URL .'
[2014-xx-xxT15:43:48.000-08:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 0000KHfRLZR7u1^Y1T6EVV1J3Huq00000w,0:5:1:6] [tid: 454a]  [nQSError: 46164] HTTP Server returned 404 (Not Found) for URL .
[2014-xx-xxT15:44:48.000-08:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 0000KHfRLZR7u1^Y1T6EVV1J3Huq00000w,0:5:1:6] [tid: 454a]  [53003] LDAP bind failure: Timed out.
[2014-xx-xxT15:44:48.000-08:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 0000KHfRLZR7u1^Y1T6EVV1J3Huq00000w,0:5:1:6] [tid: 454a]  [53003] LDAP bind failure: Timed out.
[2014-xx-xxT15:45:24.000-08:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 000002iaTlx7u1^Y1T6EVV00GW2C000026,0] [tid: 727e]  [43069] The configuration on Cluster Controller host01.domain:9706 specifies a different Secondary Cluster Controller or  [[
client controller port than this Oracle BI Server's cluster configuration.
]]

 

The bimiddleware application (deployment) is up and running. 
The endpoint test URLs work correctly in Enterprise Manager Fusion Middleware Control.

Changes

This issue could manifest itself in several ways.  A couple of known changes that may introduce this issue are.

  1. Horizontally scaling out a node (node 1 works, node2,3,n does not work). Specifically, when a node is scaled out after the initial node 1 has been patched with a patchset.
  2. Cloning an environment from source to target via the Test to Production (T2P) process documented in the Fusion Middleware Administration Guide

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms