My Oracle Support Banner

"Ora-20001: The Printing Engine Could not be Reached" Exporting APEX Report (Doc ID 846587.1)

Last updated on AUGUST 11, 2019

Applies to:

Oracle Application Express (APEX) - Version 3.0.1 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.


When running APEX using the Apache FOP, attempting to export an APEX report to PDF (either interactive report or a standard report), the following error occurs:

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

Testing the print server with the static HTML file provided in <Note.748179.1> Troubleshooting Apex PDF Printing, the following error can be seen:

<HTML><HEAD><TITLE>500 Internal Server Error</TITLE></HEAD><BODY><H1>500
Internal Server Error</H1>OracleJSP: oracle.jsp.provider.JspCompileException: <H3>Errori di
deployments\fop\fop\persistence\_pages\\</H3><pre>Could not
create the Java virtual machine.
Error occurred during initialization of VM
Could not reserve enough space for object heap


No recent changes were recently done to the environment.


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.