Adobe Rendering Error
This problem analysis scenario applies, if the connection of your system to the Adobe Document Services (ADS) works correctly.
Problem Description
Rendering errors might occur as follows:
· during the rendering process (e.g. ADS fail to create or print a PDF form)
· after the rendering process (e.g. a form can not be displayed properly, scripting in the form fails).
Rendering errors are indicated by the ADS message …render error…
Decision Roadmap
Prerequisites
You have access to the following systems:
· AS Java that hosts the Java Web Dynpro application (HTTP connection); only for forms created in AS Java.
● AS ABAP that is used for the forms processing (SAP GUI connection); only for forms created in AS ABAP. You need debugging authorization to use this function.
Main Tools
● Internet Browser
● Transaction SFP (only for forms created in SAP Web AS ABAP)
● Adobe Reader; for information on the version, see SAP Note 834573.
Execution
To get all test collateral:
Web Dynpro for Java
Set the Web Dynpro Trace level to ALL to get the PDF with attachments, respectively in case of a rendering error a file ERROR.PDF, which is stored on the ADS server.
For additional information, see
...
● Returned Rendering Result (below)
● Attachments of the Returned PDF (below)
ABAP
Proceed as described in Saving Runtime Information and a Generated PDF Locally
Analysis
Check the Returned PDF
If the trace level is set to a value equal to 4, or if an error occurred during rendering, Adobe document services provides you with a PDF and several files embedded in its attachment. These files contain all input that is needed for rendering of the form. For performance reasons, it is an untagged PDF and therefore not accessible.
The appearance of the returned PDF depends on the setting for the trace level and on the type of error (error or warning). In some cases, the called PDF form is returned. There may also be cases when only a PDF containing error messages is returned. See the following table:
Return Renderin Results
Rendering error |
Trace = 4 |
PDF requested |
Explanation |
Yes |
Not relevant |
Not relevant |
No PDF form is returned. Instead a file ERROR.PDF with attachments is created and displayed. It is stored on the ADS server in <DIR_GLOBAL>\AdobeDocumentServices\renderErrorLog\ErrorFiles, under file name <Date+Time+ApplicationName+Username>.pdf, exactly specified in TRACE.TXT. |
No |
Yes |
Yes |
The PDF form is returned with additional information in its attachments. If warnings exist, they are listed in a file ERROR.PDF, which is also included in the attachments. |
|
|
No |
No PDF form is returned. Instead a file ERROR.PDF with attachments is created and displayed, which may contain warnings or even be empty. |
|
No |
Yes |
The PDF form is returned without any additional information (interactive form or PDF-based form in print preview). |
|
|
No |
No PDF form is returned. PDL may be created for printing. |
Attachments of the Returned PDF
Item |
Description in PDF |
Further description |
Error.pdf |
Render Error report |
Errors and warnings, that occurred during rendering. |
Data.xml |
Document Services Data |
Runtime data |
pdfDocument.xml |
Document Services Control Stream |
Control file for rendering |
<formname>.xdp |
Document Services Template |
Layout of the form, can be displayed in Adobe LiveCycle Designer. Note that it does not contain any separate schema or context information. |
trace.txt |
Document Services Trace |
Trace information provided by Adobe document services. |
xfa.xci |
Document Services Config |
Control file for rendering |
<name1>.xdc |
Document Services XDC |
Control file for printer or Adobe Reader |
<name2>.xdc |
Document Services XDC 2 (if there is a dual render) |
Control file for printer or Adobe Reader |
Analyze the Returned PDF
The returned PDF with Additional Information gives you detailed information on the reason for errors and warnings. If you have further questions to be solved by the support team, create a message under BC-SRV-FP and attach the PDF with Additional Information.
Additional information
Check Storage Size
The default maximum size of the directory that stores all ERROR.PDF files (see the table Returned rendering result above for detailed information on the file names) on the server is 0 MB.
To change the size limit, see Changing the Maximum Size for the Storage of the ERROR.PDF File in the Adobe Document Services Configuration Guide. After it creates the ERROR.PDF file, Adobe document services examines the directory to determine the total size of files in the directory. If the size is more than the maximum allowed, the system begins deleting files (oldest first) until the directory size is below the maximum allowed or until one error file is left in the directory.
Changing the Design of the ERROR.PDF File
This document is in the Adobe Document Services Configuration Guide and gives you information on how you can customize the design of the ERROR.PDF file.