COGNOiSe.com - The IBM Cognos Community

IBM Cognos Analytics Platform => Cognos Analytics => Administration and Security => Topic started by: zakatak on 01 Jun 2017 01:31:09 PM

Title: Cannot Get to Administration Console
Post by: zakatak on 01 Jun 2017 01:31:09 PM
This is in my development environment, an 11.0.5 installation making use of IIS for SSO. I go to my server http://server/ibmcognos/bi/ and I'm automatically logged in. I run reports, review schedules, all the normal stuff. I then choose Manage > Administration console and a new window opens up (just like in production) with the url http://server/ibmcognos/bi/v1/disp?b_action=cogadmin but the page never actually loads. After about 4 minutes it just seems to give up...

I don't remember the exact date this last worked, but it was within the last month. Being a non-production environment it's easy to reboot the machine, or restart Cognos. I've done both, but neither seems to work. I've tried remotely with IE, Firefox, and Chrome. I've tried locally with IE.

Any thoughts on what to try or where to look for errors?

edit: removed code tags
Title: Re: Cannot Get to Administration Console
Post by: zakatak on 02 Jun 2017 09:19:56 AM
So I'm still trying to fix this... I have attempted to bypass my IIS gateway by going directly to http://server:9300/bi/ but I never proceed past the login page. Any ideas on where I could look to figure out why? I'm not getting any onscreen messages, just that endless gif of the parallel lines expanding, contracting, and changing colors.

When I look in the web console I see GET and POST messages to http://server:9300/bi/v1/login resulting in a 441 status code... probably relevant, but I'm not really sure what I can do with this knowledge.
Title: Re: Cannot Get to Administration Console
Post by: zakatak on 06 Jun 2017 08:01:56 AM
I found a solution; I ran the NC_DROP & dbClean scripts. I might have been okay with just the NC_DROP script actually. Anyhow after doing so I could get to the administration console again, but I also wiped my content store.

I am not so smart.

Luckily it was development so I was able to restore from Production... If you are reading this because you have the same issue, take a backup before you "fix" the issue...