COGNOiSe.com - The IBM Cognos Community

Legacy Business Intelligence => COGNOS ReportNet => Topic started by: pw on 09 Sep 2005 04:53:24 AM

Title: ReportNet Viewer - Filter
Post by: pw on 09 Sep 2005 04:53:24 AM
Hi Folks,

i have created a small testreport (my first steps...) which shows me some information from 2 tables, each table in a small list.
Both tables have a "Year" column.
What i did was to add a dropdownlist with a query of all years.
I also added a button "Proceed" to filter the report.
The filter is optional. When i now execute the report, the first view shows me all data of all years- quite fine (i didn't enter a filter yet).
When i now select year 2004 (or another) from the dropdown list and press proceed, i always get the following error:

CCLUnknownError:0:Fatal:

Zurückverfolgen:

WPBIBusMethod.cpp(194): CCLUnknownError: CCL_CAUGHT: WPBIBusMethod::run

WPReportExecutionMethod.cpp(184): CCLUnknownError: CCL_RETHROW: WPReportExecutionMethod::checkRequestForExceptions

WPExecuteRequestThread.cpp(169): CCLUnknownError: WPExecuteRequestThread::checkException



Can anybody help??

Thanks in advance!
Title: Re: ReportNet Viewer - Filter
Post by: cognosfreelancer on 09 Sep 2005 07:42:51 AM
Hello pw

Someone might actually remember what the cryptic message mean but you and we may have a better idea about what caused it by looking at the crnserver.log file.

Often I have noticed the log file capturing more information that is displayed in the portal.

NKT
Title: Re: ReportNet Viewer - Filter
Post by: sunil911 on 09 Sep 2005 12:08:21 PM
Unfortunately, the error message isn't too intuitive.  Can you use the Go Sales model to dummy up the report and attach a XML file of the version so that we can troubleshoot it ? Thanks.
Title: Re: ReportNet Viewer - Filter
Post by: pw on 12 Sep 2005 03:06:00 AM
Well, i found out what this message means ;)

i just made the error myself (as most times)

infact, i put the wrong "execute" button into my form.
instead of implementing a "submit" button i used the "next" button......

that is what the error caused :-(