Community
Participate
Working Groups
In a recent deployment of an new web application using BIRT as its reporting engine, we faced a problem where our report headers not being shown when get deployed in the server. We have a hard time figuring out the problem as there's no error occur when the report gets generated. At the end, only we found out that the shared library path in the reports is wrong. Having raise an error message like 'invalid shared library path' would have been saved us a lot of time, instead of just quietly generate an invalid report.
The user could find the error in the following places: 1. If the report is running in the designer,the designer should display the error message. 2. If the report is running in the BIRT SDK, the log file should contains the message.
fixed. Model outputs error message in log file.
Verified in daily build 2.6.1.v20100908-0630 that FILE_NOT_FOUND will be output to report engine log.