Using RTF Report Layout with ORDS Creates Unreadable PDF and Print URL Errors (Doc ID 1903644.1)

Last updated on SEPTEMBER 20, 2016

Applies to:

Oracle REST Data Services - Version 2.0 and later
Oracle Application Express (formerly HTML DB) - Version 3.2.0 and later
Information in this document applies to any platform.

Symptoms

After defining an RTF Report Layout for an APEX report, the report cannot be rendered as a PDF.  The Inline display or Download of the printed report cannot be viewed in Adobe.  An error is raised.

"Adobe Reader could not open <filename>.pdf because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded)."

  

Also, if the Print URL (Report "Print Attributes") is used to create print link in a page or button, an error is raised when clicking on the link or button.

ORA-20001: The printing engine could not be reached because either the URL specified is incorrect or a proxy URL needs to be specified.

  

The same errors are not produced when XSL-FO is used as the basis for the Report Layout.

Changes

 Oracle REST Data Services (ORDS) was selected as the PDF printing solution.

Instance Administration -> Instance Settings -> Report Printing -> Print Server = "Oracle APEX Listener" (now called Oracle REST Data Services / ORDS).

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms