COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Report Studio => Topic started by: Cognos8 on 22 Jul 2011 04:47:48 AM

Title: " AAA-AUT-0011 - Invalid namespace was selected "
Post by: Cognos8 on 22 Jul 2011 04:47:48 AM


I have installed cognos 10.1 fp2 .while launching web uri or dispatch url (http://fbpcrm4:9400/p2pd/servlet/dispatch) it thorws the below error.
sometimes ,  after submitting OK , environment launches properly. Due to this issue, i am not able to save the life cycle manager configuration. Please help if anyone have solution for this.

" AAA-AUT-0011 -  Invalid namespace was selected "
Title: Re: " AAA-AUT-0011 - Invalid namespace was selected "
Post by: cadams on 14 Mar 2012 08:21:01 PM
I seem to be having a similar issue,

I have 10.1.1 on Windows 2008, users can logout and login with no issues SSO is implemented.

As soon as users enter into Query Studio, and from within there choose logoff and try and login again they get :-

"AAA-AUT-0011 Invalid namespace was selected"

Does Anyone have any thoughts on this ?
Title: Re: " AAA-AUT-0011 - Invalid namespace was selected "
Post by: HalfBloodPrince on 14 Mar 2012 11:39:06 PM
This Links may help

http://www-01.ibm.com/support/docview.wss?uid=swg21508564
Title: Re: " AAA-AUT-0011 - Invalid namespace was selected "
Post by: bpothier on 16 May 2012 01:53:18 PM
We had this same issue and it turned out to be the port number we were susing with our single source signon. Once we changed the port from 636 back to 389 everythign worked fine
Title: Re: " AAA-AUT-0011 - Invalid namespace was selected "
Post by: kawabunga on 22 Mar 2013 10:58:40 AM
Quote from: cadams on 14 Mar 2012 08:21:01 PM
I seem to be having a similar issue,

I have 10.1.1 on Windows 2008, users can logout and login with no issues SSO is implemented.

As soon as users enter into Query Studio, and from within there choose logoff and try and login again they get :-

"AAA-AUT-0011 Invalid namespace was selected"

Does Anyone have any thoughts on this ?

Hi cadams, you just described the exact scenario we're experiencing today after we activated SSO yesterday. Did you ever resolve this?