If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

DPR-ERR-2014 ... SACamSrvc

Started by Marva55, 28 Apr 2014 01:15:06 AM

Previous topic - Next topic

Marva55

We managed to get rid of this error messages by setting "Enable replication?" to False in Cognos Configuration on all application servers.

DPR-ERR-2014 Unable to load balance the request because no nodes in the cluster are available, or no nodes are configured for the service: SACamSrvc.


Jayson.A

We are experiencing this same error. We're you using SSO with Active Directory? It says the following for the description of this field.

"Defines general properties related to replication of user session data"
"use this group of properties to set the settings for IBM Cognos authentication services to enable user session replication"

I'm concerned turning this off might break SSO but i will test it in DEV.

Marva55

Yes we are using "Active Directory" as the Cognos authentication provider, but we are using the environment variable REMOTE_USER to achieve single signon

If you do not want Kerberos delegation, you can configure the provider to access the environment variable REMOTE_USER to achieve single signon.
You must set the advanced property singleSignOnOption to the value IdentityMapping. You must also specify bind credentials for the Active Directory namespace.

Microsoft IIS sets REMOTE_USER by default when you enable Windows integrated authentication. If Kerberos authentication is bypassed, single signon to Microsoft OLAP (MSAS) data sources will not be possible.

Procedure
In every location where you installed Content Manager, open IBM® Cognos® Configuration.
In the Explorer window, under Security > Authentication, click the Active Directory namespace.
Click in the Value column for Advanced properties and then click the edit button.
In the Value - Advanced properties dialog box, click Add.
In the Name column, type singleSignOnOption
In the Value column, type IdentityMapping.
Click OK.
Click in the Value column for Binding credentials, and then click the edit button.
In the Value - Binding credentials dialog box, specify a user ID and password and then click OK.
Results
The Active Directory provider now uses REMOTE_USER for single signon.

Tip: To switch back to Kerberos delegation, edit Advanced properties and, in the Value column, type KerberosAuthentication.


Source: Enabling Single Signon Between Active Directory Server and IBM Cognos Components using REMOTE_USER

Jayson.A

Thanks for the reply yea that was our issue we use SSO for MSAS/OLAP.

On a good note though IBM emailed me yesterday saying they have a hotfix that is only released upon validation of the issue.