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

How Should I resolve this error

Started by rr.bi1212, 18 Jul 2016 12:02:58 PM

Previous topic - Next topic

rr.bi1212

When I am using a particular prompt I am getting the below mentioned error message. Please let me know how to resolve it.


Query Service internal error has occurred, please see the log for details.

bdbits

There is nothing here to go on ... what is the data source? What is your "particular prompt"? Was there an error number associated with the message? Did you get details from the server log as suggested?

rr.bi1212

[Column name] = ?p_MeetingName? this is the prompt. This is an Optional prompt.

When I put this filter as Before Aggregation I get the below mentioned error:

SQL cannot be generated, because the filter condition [Column Name] = ?p_MeetingName? could not be applied to the following fact stream which does not contain a fact projection: (Table name).

When I Put this filter as After Aggregation I get this error:

Query Service internal error has occurred, please see the log for details.

I did not check the logs as of now.

bdbits

Is [Column name] in your result set (on the report and/or in the query)?
Another possibility might be incorrect cardinality between tables defined in FM.

Copy and paste the generated SQL in Report Studio (Tools > Show Generated SQL/MDX).

MFGF

Quote from: rr.bi1212 on 18 Jul 2016 12:24:09 PM
[Column name] = ?p_MeetingName? this is the prompt. This is an Optional prompt.

When I put this filter as Before Aggregation I get the below mentioned error:

SQL cannot be generated, because the filter condition [Column Name] = ?p_MeetingName? could not be applied to the following fact stream which does not contain a fact projection: (Table name).

When I Put this filter as After Aggregation I get this error:

Query Service internal error has occurred, please see the log for details.

I did not check the logs as of now.

Hi,

We still have very little to go on here. Looking at the error you posted (in particular the part about there being no fact projection), my first guess would be that your report is using manually-coded SQL? Is this the case?

MF.
Meep!