Adobe Rendering Error
This problem analysis scenario applies only, if the connection of your system to the Adobe document services (ADS) works correctly. For problems concerning the connection, see the following PAS:
● Adobe Connection Error - ABAP
● Adobe Connection Error - Java
Problem Description
When Adobe document services render a form, there may be problems with the rendering or there may be problems using the form after rendering. Rendering problems, for example, include failure to create a PDF or failure to print a PDF-based form. Rendering errors are indicated by one following ADS message.
…render error…
Problems using the form include problems with execution on the client or with the rendering results, even if the form was rendered successfully. For example, the form may not display properly or scripting in the form may fail.
In these cases the user or form developer can generate a PDF that contains enough test collateral for the support team to analyze the problem.
|
Scenario Type: |
Error analysis |
|
NetWeaver Component: |
SAP Web AS, Adobe document services |
|
Validity: |
SAP NetWeaver 7.0 >= SP Stack 06 |
Decision Roadmap
Prerequisites
You need to have access to the following systems:
● Web AS Java that hosts the Java Web Dynpro application (HTTP connection); only for forms created in SAP Web AS Java.
● Web AS ABAP that is used for the forms processing (SAP GUI connection); only for forms created in SAP Web 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
See the following table.
Required Actions
SAP NetWeaver release |
What must you do? |
You get .. |
For additional information, see |
NW’04 < SPS18 |
Set the Web Dynpro Trace level to ALL. |
the trace information of the Adobe document services, which is stored in the log file. |
|
NW’04 >= SPS18 |
Set the Web Dynpro Trace level to ALL. |
the trace information of the Adobe document services, which is stored in the log file. In case of a rendering error, a file ERROR.PDF, which is stored on the ADS server. |
● the table Returned Rendering Result in the section below. This informs you about the location of the ERROR.PDF in the file system. |
NW7.0 SPS6/SPS7/SPS8 |
Append sap-wd-adsTrace=4 to the URL of your Web Dynpro application. |
the PDF with attachments.
You only get this information, when the form is rendered successfully. If a render error occurs, no PDF is returned. |
● SAP Note 742674, informs you on how to get the entire Web Dynpro trace. ● SAP Note 846610, informs you on how to get the ADS trace |
NW7.0 >= SPS9 |
Set the Web Dynpro Trace level to ALL. |
the PDF with attachments, respectively in case of a rendering error a file ERROR.PDF, which is stored on the ADS server. |
● Returned Rendering Result (below) ● Attachments of the Returned PDF (below) |
ABAP
SAP NetWeaver 7.0 releases as of SPS06
Proceed as follows:
1. In transaction SFP, chooseUtilities ® Settings.
2. Under Runtime Information, set the Trace Level to Very Detailed Trace, which corresponds to a trace level of 4.
It is not necessary to specify a file name for the trace, because the trace file is part of the PDF with Additional Information.
3. Choose Save PDF with Additional Information
4. Enter a file name for saving the PDF with Additional Information on your front end.
Once a setting is chosen, the system saves the runtime information for all forms that are generated while you are logged on. When testing or processing different forms you must change the specified file names to ensure that the saved information is not overwritten.
5. Test or call the PDF-based form in your application program.
6. The system stores all information as you specified. When you choose Print Preview, the system also displays the PDF with Additional Information in Adobe Reader.
SAP NetWeaver ‘04 releases as of SPS18
In case of a rendering error, the file ERROR.PDF is stored on the ADS server. For more information on the location, see the table Returned Rendering Result below.
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:
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 100 MB. 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. 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.
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.