Error when running reports from dashboards
Hi on all burndown reports on my dashboards, when i click on the hyper-link which drills down to the report section. Although the report displays I get the following error at the bottom of the burndown report.
Can anyone shed any light on this?
The following items have errors:
ReportDesign (id = 1):
- Unhandled exception when executing script.
Error.UnhandledScriptError ( 1 time(s) )
detail : org.eclipse.birt.report.engine.api.EngineException: Unhandled exception when executing script.
at org.eclipse.birt.report.engine.script.internal.ScriptExecutor.addException(ScriptExecutor.java:199)....
Can anyone shed any light on this?
The following items have errors:
ReportDesign (id = 1):
- Unhandled exception when executing script.
Error.UnhandledScriptError ( 1 time(s) )
detail : org.eclipse.birt.report.engine.api.EngineException: Unhandled exception when executing script.
at org.eclipse.birt.report.engine.script.internal.ScriptExecutor.addException(ScriptExecutor.java:199)....
5 answers
I'm seeing the same problem with the burndown chart.
It's displaying successfully but the error appears at the bottom of the burndown report in the About this report section. See error.
Any ideas what's causing this error?
The following items have errors:
ReportDesign (id = 1):
- Unhandled exception when executing script.
Hi on all burndown reports on my dashboards, when i click on the hyper-link which drills down to the report section. Although the report displays I get the following error at the bottom of the burndown report.
Can anyone shed any light on this?
The following items have errors:
ReportDesign (id = 1):
- Unhandled exception when executing script.
Error.UnhandledScriptError ( 1 time(s) )
detail : org.eclipse.birt.report.engine.api.EngineException: Unhandled exception when executing script.
at org.eclipse.birt.report.engine.script.internal.ScriptExecutor.addException(ScriptExecutor.java:199)....
Hi Steven, Sonya, Greg,
Just to confirm, you are only seeing this issue with the normal-sized version of the Burndown report when shown in the Reports Web UI, correct?
i.e. The exception does not show up within the viewlet content area (only after you click on the viewlet title hyperlink).
I suspect there is a problem with the BIRT report template and can be easily resolved by uploading a newer fixed version to your project areas via the Rich Client.
Some additional questions:
* Are you all running with RTC 2.0.0.2 iFix 6 ?
* Are you seeing the exception regardless of what report parameters you specify or are you seeing the exception only with specific report parameters
* Are you seeing the exception in any other report?
* Can you paste the full exception stack trace?
I will forward this to the Reports team.
We may need to open a work item for this.
Just to confirm, you are only seeing this issue with the normal-sized version of the Burndown report when shown in the Reports Web UI, correct?
i.e. The exception does not show up within the viewlet content area (only after you click on the viewlet title hyperlink).
I suspect there is a problem with the BIRT report template and can be easily resolved by uploading a newer fixed version to your project areas via the Rich Client.
Some additional questions:
* Are you all running with RTC 2.0.0.2 iFix 6 ?
* Are you seeing the exception regardless of what report parameters you specify or are you seeing the exception only with specific report parameters
* Are you seeing the exception in any other report?
* Can you paste the full exception stack trace?
I will forward this to the Reports team.
We may need to open a work item for this.
Hi Steven, Sonya, Greg,
Just to confirm, you are only seeing this issue with the normal-sized version of the Burndown report when shown in the Reports Web UI, correct?
i.e. The exception does not show up within the viewlet content area (only after you click on the viewlet title hyperlink).
I suspect there is a problem with the BIRT report template and can be easily resolved by uploading a newer fixed version to your project areas via the Rich Client.
Some additional questions:
* Are you all running with RTC 2.0.0.2 iFix 6 ?
* Are you seeing the exception regardless of what report parameters you specify or are you seeing the exception only with specific report parameters
* Are you seeing the exception in any other report?
* Can you paste the full exception stack trace?
I will forward this to the Reports team.
We may need to open a work item for this.
Just as a followup to this, click on the red "+" sign in the viewlet to expand the stack trace, then select all of it and copy into here or (preferably) into a work item. The full stack should help us a lot here.
Also answers to Mike's other questions would be helpful.
james
RTC Reports Team Lead
Hi Steven, Sonya, Greg,
Just to confirm, you are only seeing this issue with the normal-sized version of the Burndown report when shown in the Reports Web UI, correct?
i.e. The exception does not show up within the viewlet content area (only after you click on the viewlet title hyperlink).
I suspect there is a problem with the BIRT report template and can be easily resolved by uploading a newer fixed version to your project areas via the Rich Client.
Some additional questions:
* Are you all running with RTC 2.0.0.2 iFix 6 ?
* Are you seeing the exception regardless of what report parameters you specify or are you seeing the exception only with specific report parameters
* Are you seeing the exception in any other report?
* Can you paste the full exception stack trace?
I will forward this to the Reports team.
We may need to open a work item for this.
Just as a followup to this, click on the red "+" sign in the viewlet to expand the stack trace, then select all of it and copy into here or (preferably) into a work item. The full stack should help us a lot here.
Also answers to Mike's other questions would be helpful.
james
RTC Reports Team Lead
This was solved by deploying the most recent report templates.I was using older ones from a previous version.