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

 

Data Source Error: QE-DEF-0312 An error occurred while calling the content store

Started by lazrobot, 13 Mar 2015 10:29:02 AM

Previous topic - Next topic

lazrobot

We have a distributed environment with 4 dispatchers. 

On 3 of 4 dispatchers, we have no issues.  On the 4th, data sources test fine via JDBC, but Compatible connections' test fails (for any data source) and gives the following error:

QE-DEF-0312 An error occurred while calling the content store for identity information

Context:
- This dispatcher is not one of the Content Managers
- Did not see any error messages the last time I restarted Cognos services
- Running 10.2.1 FP5 across the whole environment

I am sure this is a installation/configuration issue on my end, but I can't figure out what it is.  Any idea what am I doing wrong?

MFGF

Quote from: lazrobot on 13 Mar 2015 10:29:02 AM
We have a distributed environment with 4 dispatchers. 

On 3 of 4 dispatchers, we have no issues.  On the 4th, data sources test fine via JDBC, but Compatible connections' test fails (for any data source) and gives the following error:

QE-DEF-0312 An error occurred while calling the content store for identity information

Context:
- This dispatcher is not one of the Content Managers
- Did not see any error messages the last time I restarted Cognos services
- Running 10.2.1 FP5 across the whole environment

I am sure this is a installation/configuration issue on my end, but I can't figure out what it is.  Any idea what am I doing wrong?

Hi,

Sounds like it might be this?

http://www-01.ibm.com/support/docview.wss?uid=swg21393889

MF.
Meep!

lazrobot

Yeah - I saw this but the dispatcher setting are correct.  I may just restart over the weekend to see if that clears everything up.  Thanks for the reply!

kommireddy

Noticed same in our environment, and it turns out dispatcher process actually crashed due to CPU spike, dump files noticed in bin64 directory. After restarting service, datasource test succeeded.

Dhruv

These might be because of query service thread.
Try to disable it from Cognos configuration and monitor the changes.