1. Flex report element only displays column headers

Problem:
Create and generate a report with one flex and one html report element in a Built-In template layout that divides the page in half (top and bottom). Make sure there is enough data in both report elements, that individually they can fill more than a page. Place the flex at the top of the layout and the html report element at the bottom. When you generate it, the flex only displays the column headers.

Solution:
The only solution is to set the height of the cell containing the flex to a specific size and not use the percentage value, which is default.

2. Report not saving to HTML

Problem:
If images in the generated report in the OPUS web page are not displayed the report will not save to HTML.

Solution:
Ensure that all report images are in the images folder and displaying correctly when the report is generated in the OPUS web page.

3. Single page report saves as two pages in PDF

Problem:
A single page report saves as 2 pages with the PDF save.

Solution:
Resize any report elements that are the full page size of the layout page to 85% by clicking the Resize toolbar button in the layout configuration of the report.

4. Report elements show up blank when generated

Problem:
The bar graph, line graph and pie chart report elements show up blank (display no data) when generated in the OPUS web client if the Windows Regional Settings set to Polish.

Solution:
If the regional settings of the OPUS Server machine and OPUS web client machine don't have the same decimal point and thousand separator then the bar graph, line graph and pie chart report elements won't display it data on the OPUS web client machine.

5. Error in HTML: 2-Overflow

Problem:
If this error, Error in HTML:2-Overflow, is displayed in the OPUS web page when generating a Data Grouping report, then the Regional Settings of the client machine is incompatible for the decimal point and thousand separator with the data used in the Data Grouping report.

Solution:
This problem was found on a Danish operating system where the decimal point and thousand separator are switched around to the English operating system; the decimal point and thousand separator were set to the English operating systems settings and solved the problem.

6. Data Grouping reports not supported on SQL 7

Problem and solution:
The error, Bulkload will only work with SQL Server 2000 or later, is displayed in the OPUS web page when generating a Data Grouping when the SQL Server where the OPUS database is installed on, is a SQL version prior to SQL 2000. A grouping report will not generate from SQL 7 because Bulk Loading is only supported from SQL 2000 and later versions. The Bulk Loading functionality is needed to process the Data Grouping report data.

7. Excessive report generation time

Problem:
When you do report development and configuration on one PC, let’s say at your office premises, then Export the OPUS database to Import it on site, you have to edit the datasource connections. The paths to the datasources, e.g. the path to an Access database or the name of a SQL Server might be different on site than at the office. But when the SQL Server name is edited for a SQL datasource is seems that the report generation is very slow in the OPUS web page, where the original configuration at the office was fast.

Solution:
Every datasource in OPUS has an authentication linked to it and in the case of a SQL datasource the authentication specifies the computer name where the SQL Server sides. This authentication is done from PC to PC through the operating system. When the SQL Server name is edited for a datasource, you must also edit the authentication of the SQL datasource connection by clicking the Advanced button in the edit dialog of the datasource and editing the Path, which in the case of a SQL datasource would be the computer name. If this is not done, when the report attempts to retrieve the data from the datasource it tries to connect to a machine that is not on the network. The reason why the report still works with a wrong authentication is because the SQL Server name is normally the same name as the computer

8. Data Grouping Header/Footer is blank

Problem:
The value of a group header or footer blank.

Solution:
This means that the value for that header/footer is Null and therefore can’t be related to data under it because the Shaping procedure of the data done in SQL can’t relate Null to valid data values.

9. Custom layout page not displaying report elements

Problem and Solution:
When using a custom HTML page as a layout page for a report, you must either specify a height for the table where in you wish to drag your report element or the report elements height must be an actual value and not a percentage. If this is not done then the report element image is not displayed in the custom layout page because the default height of a report element image is 90%. And if the table containing the report element image doesn't have a height specified then 90% of nothing is still nothing and therefore you won’t see the report element in the layout.

10. Blank report elements in report

Problem:
The value of a group header or footer blank.

Solution:
This means that the value for that header/footer is Null and therefore can’t be related to data under it because the Shaping procedure of the data done in SQL can’t relate Null to valid data values.

11. Custom layout page not displaying report elements

Problem and Solution:
When using a custom HTML page as a layout page for a report, you must either specify a height for the table where in you wish to drag your report element or the report elements height must be an actual value and not a percentage. If this is not done then the report element image is not displayed in the custom layout page because the default height of a report element image is 90%. And if the table containing the report element image doesn't have a height specified then 90% of nothing is still nothing and therefore you won’t see the report element in the layout.

12. Blank report elements in report

Problem and Solution:
If a generated schedule being viewed displays blank pages where report elements should be then the Network Access User specified in OPUS Setup doesn't have enough access rights to create the report elements when the Schedule is generated. Select at least a Power User for the OPUS Network Access user.

13. Report Elements not printing

Problem and Solution:
If you have a report layout with four cells containing report elements in all the cells, then change the size of the bottom two report elements to 100%, when you print this report you will notice that the bottom two report elements did not print. To solve this, change the size of the bottom two report elements to 98%

14. Blank report when saving to PDF

Problem and Solution:
If the report that has been saved to PDF is blank from an OPUS web page client or a scheduled task, change the OPUS Postscript Printer paper size to A4. This can be done via the Printers and Faxes menu item in the Windows Start menu. Right click on the OPUS Postscript Printer and select Properties. Then select Device Settings and change the Form to Tray assignment to A4.

15. Single quotes in the Excel report elements

If a datasource or parameter text value displayed on an Excel report element should contain a single quote but doesn’t, it is because it’s been removed from the text value otherwise the cell doesn’t display the text after and including the single quote.

16. Office 2007 and Office Web Components

If Office 2007 is installed on the OPUS Server PC then any clients connecting to that OPUS Server to view reports containing an Excel report element must have the Office 2003 Web Components installed to display the reports correctly.

17. Pages rotated when saving to PDF

Problem:
When saving a generated report to PDF, some of the pages are rotated in the PDF document. In other words, saving a report as landscape results in some of the pages rotated to portrait.

Solution:
Change the Category Axis Titles text direction to 45 degrees in the Line Graph or Bar Graph report elements used for saving to PDF.

Cause:
When setting the Category Axis Titles text direction to 90 or 270 degrees in a Line Graph or Bar Graph report element the PDF Distiller automatically rotates pages based on majority text direction.

18. An error occurred with Add-on in Internet Explorer

Problem:
While generating a report in the OPUS Web Client in Internet Explorer, an error is displayed referencing a problem with an Add-on and thereafter the browser window automatically shuts down and therefore the selected report is not generated as expected. This problem only seems to occur with IE 7.

Solution:
1. At the bottom of the screen in the SETTINGS section, select the DISABLE option and click OK to finish.
2. Reboot your computer for the change to take effect.
2. Go to MANAGE ADD-ONS in the drop-down menu.
3. Select the ENABLE OR DISABLE ADD-ONS option in the sub-menu.
4. Select ADD-ONS THAT HAVE BEEN USED BY INTERNET EXPLORER from the SHOW drop-down menu. This will display a list of add-ons that are not visible when you first open the utility.
5. Highlight the add-on that is causing the problem.