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

PROBLEM: No authority could be contacted for authentication

Started by josepherwin, 03 Dec 2009 04:54:42 PM

Previous topic - Next topic

josepherwin

Hi All,

Our company is located in 2 different state, for this example, lets call them Site A and Site B (distance between the 2 is about 3000Km)

All of our Cognos App Servers, web server, and Content Manager server is located in Site A.

The only thing that is established in Site B is Site B Active Directory.

The problem here is that sometime, our end-users in site B experience intermittent connection.

During the issue happening, the following scenario take place:
1. When user is already in Cognos and click on any of the link in the portal, they will immediately throw out the error "No authority could be contacted for authentication". Once they close their session and try to open up Cognos from scratch, issue #2 occurs
2. When user does not have any cognos session opened, they try to access the environment, and they will get HTTP 5000 error.

However, 7 - 15 minutes later, the problem resolved itself.
During this downtime, user is Site A does not get affected and still able to perform their task in Cognos as per normal.

No error recorded anywhere in the Cognos log and the technical/networking team from both Sites have looked into their components and was unable to see anything wrong.

Anyone able to shed some lights in regards to this matter?

Allen Krause

hi there,

somewhere in your connection to 'Site B' where your LDAP  (Active Directory) (im assuming your using Active Directory for your user source) is there is a connectivity drop (firewall maybe?).  Have you asked your network team to enable packet sniffers or monitor data collisions?  At the moments of downtown are they spuratic or at a continuous time, if its continues hopefully it can be narrowed.

If this causes to much hassle is it possible to migrate the DC that has AD on it to 'Site A', this way only users from Site B need to autheticate through the network.

A side note, Cognos is an application that hates network hiccups.

cognosjon

Have a look at the asynch time out requests, it may be around this area.