Output generation issues

When the output of your template does not display as you expected, review these issues and troubleshooting suggestions.

Generating large document-style reports
Document-style reports are considered large for IBM Engineering Lifecycle Optimization - Publishing when they consist of a thousand or more pages. To decrease the time that it takes Engineering Publishing to generate large document-style reports, consider using the multipart property in your document specification or changing the contents of your template.
Fixing document-style report generation error in Publishing Document Builder due to large output document size
When Publishing Document Builder generates output of large sizes, document-style report generation fails. It happens because the default column size in databases is too small to store the large output document-style reports. This issue is observed in Db2® or Derby database.
Job cancellations
If you cancel a local document-style report generation, the cancellation might not be acknowledged by IBM Engineering Lifecycle Optimization - Publishing immediately.
Choosing an output format
Each output might generate differently, depending on the elements and formatting in the template.
Improving document-style report generation performance
You might shorten the time IBM Engineering Lifecycle Optimization - Publishing takes to generate an output document-style report by trying these steps.
Fixing document-style report generation completion issues
When the output document-style report cannot be generated, try these troubleshooting tips.
Fixing invalid data errors
When the output document-style report cannot be generated, try these troubleshooting tips.
Fixing out of memory errors
If the Document Studio or the Launcher applications time out with an out-of-memory error, you can adjust the Java™ heap parameters in the product configuration files to improve performance.
Fixing data attribute not found errors
If you generate your output and the data attribute displays as <data attribute not found>, it means that the attribute used in the template is not found in the data. When that happens, the most common reason is using a schema on a different data source than the one for which the report was designed.
Fixing table display issues
If tables are not displaying correctly in your output, consider adjusting the table properties.
Fixing Object Linking and Embedding (OLE) issues in output
This topic explains how to troubleshoot Object Linking and Embedding (OLE) generation where OLEs are not visible in the Microsoft Word document.
Preventing broken links in Microsoft Word documents
If your Microsoft Word document contains links to other files, moving it to a different computer invalidates the linked information. To make the document-style report self-contained, remove the links from the document-style report.
Fixing macros that are not running
If you run a macro and receive errors, verify that necessary folders are created and that you have the correct permissions to them.
Cleaning your work area
Periodically, clean your work area to delete the content of the temporary files and output files that are generated by IBM Engineering Lifecycle Optimization - Publishing.

Parent topic: Troubleshooting and support for Engineering Publishing