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

Error while upgrading to Cognos 11

Started by fakxy, 10 Aug 2020 09:07:08 AM

Previous topic - Next topic

fakxy

Hello Folks,

I have recently upgraded from Cognos 10.2 to Cognos Analytics.
There is an error that I am getting.Can someone help me with this:

XQE-GEN-0005 Found an internal error: java.lang.IllegalMonitorStateException

What does this error could mean

Regards!

MFGF

Quote from: fakxy on 10 Aug 2020 09:07:08 AM
Hello Folks,

I have recently upgraded from Cognos 10.2 to Cognos Analytics.
There is an error that I am getting.Can someone help me with this:

XQE-GEN-0005 Found an internal error: java.lang.IllegalMonitorStateException

What does this error could mean

Regards!

Hi,

XQE errors are coming from the Dynamic Query Mode engine. Were you using DQM in Cognos 10.2, or is this a result of trying to migrate from Compatible Query to Dynamic Query?

XQE-GEN-0005 is a very generic error from DQM - on its own it doesn't really tell us anything other than there was an issue in generating a query. Have you looked in the XQE logs to see if there are more details logged on this?

Cheers!

MF.
Meep!

fakxy

Hi MF,

This error is coming after moving from CQE to DQM.I shall review the logs mentioned by you, get some more information on the error and get back

Thanks so much for your response

MFGF

Quote from: fakxy on 12 Aug 2020 06:46:48 AM
Hi MF,

This error is coming after moving from CQE to DQM.I shall review the logs mentioned by you, get some more information on the error and get back

Thanks so much for your response

CQE to DQM migrations can be frustrating - especially if the modeler has done weird things in FM. Compatible Query has looser syntax checking than Dynamic Query, and sometimes people do things in CQE that work but should never really have worked. Once you try to move it to DQM you bump up against these issues.

Are you seeing this error when upgrading a model in FM, or is it when running a report?

MF.
Meep!