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

CAM-AAA-0135 -The user is already authenticated in all available namespaces.

Started by Dargie, 29 Feb 2012 02:51:01 AM

Previous topic - Next topic

Dargie

CAM-AAA-0135 -The user is already authenticated in all available namespaces.

Hi, I was wondering if anyone has had this issue before.
Last night we had installed a SQL client 64bit Application onto the server when it rebooted the Gateway to Active Directory is no longer working.

We are currently moving away from Access Manager but this gateway still works.

We are on Cognos 8.4.1 with two gateway (AM and AD)

Thanks
Dargie

Grim

"Honorary Master of IBM Links"- MFGF
Certified IBM C8 & C10 Admin, Gamer, Geek and all around nice guy.
<-Applaud if my rant helped! 8)

rih9000

I'm getting the same error message.

I was working this morning fine, all of a sudden, when I tried to logon, I got this message:
"Error during login [java.net.ConnectException: Connection refused: connect]"

I rebooted the server. Now when I try to logon, I get this message:
"AAA-AUT-0013 The user is already authenticated in all available namespaces".
I can't logon to Cognos Connection or anything.

I Googled some articles on this error message, but none of them apply to my situation.
I am the only one using Cognos here and I haven't changed any settings,
except that in one package I changed the Query Processing option from "Database Only" to "Limited Local". However now Cognos won't let me into that package or any package, so I think that this is not the cause.
:( thanks for any help

MFGF

Hi,

I have seen this error a number of times when my services don't start in the order I expect them to. If my Cognos 10 service starts before my LDAP service, I see this issue. The fix (for me) is to ensure that my LDAP server is started, then to start (or restart) the Cognos 10 service.

Possibly a red herring, but worth checking out :)

MF.
Meep!


rih9000

I've discovered that my problem with this error message is caused by a custom login java script that somebody here inserted into the logon process ... thanks, all  :P