clm - error about timesheet reports on v4.0.5
hi,
we are receiving following error message on timesheet reports.In detail we use tomcat as app.server, SQL server as databases, version CLM 4.0.5 . One of that reports works successfully that is "workitem Timesheet Summary". Other of them(personal timesheet, personal timesheet by project area, personal timesheet by workitem) result with the error:
Table (id = 1367):
+ An exception occurred during processing. Please see the following message for details:
Failed to prepare the query execution for the data set: Work Items
Failed to prepare the following query for the data set type (com.ibm.team.reports.generic.advancedDataSet).
[PROJECT_AREA_NAME = ProjectArea AND CATEGORY_ITEMID IN Category AND DEV_LINE_NAME IN Timeline AND ITERATION_NAME IN Iteration]
org.eclipse.datatools.connectivity.oda.OdaException: Parse error near: PROJECT_AREA_NAME = ProjectArea AND CATEGORY_ITEMID IN
+ An exception occurred during processing. Please see the following message for details:
Failed to prepare the query execution for the data set: Work Items
Failed to prepare the following query for the data set type (com.ibm.team.reports.generic.advancedDataSet).
[PROJECT_AREA_NAME = ProjectArea AND CATEGORY_ITEMID IN Category AND DEV_LINE_NAME IN Timeline AND ITERATION_NAME IN Iteration]
org.eclipse.datatools.connectivity.oda.OdaException: Parse error near: PROJECT_AREA_NAME = ProjectArea AND CATEGORY_ITEMID IN
Thanks
One answer
Hi Eray,
I would not expect any error in jts.log. I think it is not related. We had couple of issues with Java version embedded in WAS which caused error when reports running. It is described on http://www-01.ibm.com/support/docview.wss?uid=swg21616615.
This might be affecting you as well.
If it does not help, then please open new PMR.
I would not expect any error in jts.log. I think it is not related. We had couple of issues with Java version embedded in WAS which caused error when reports running. It is described on http://www-01.ibm.com/support/docview.wss?uid=swg21616615.
This might be affecting you as well.
If it does not help, then please open new PMR.
Comments
Krzysztof Kaźmierczyk
Feb 24 '14, 8:54 a.m.Hi Eray,
What is full stack trace of the issue? You will find it in ccm.log file on your server.
Eray İzgin
Feb 24 '14, 9:10 a.m.Hi Kaźmierczyk,