Unable to Print the PDF file.

I get the following error message in my jde.log

Unable to Print the PDF file.

When attempting to run various reports in the PY7333 Environment. The job shows as error in the Submitted Jobs screen.

We are running on a HP9000, with a Oracle 8.1.6. Database over OneWorld Xe Update 2.

On the UNIX box the job lp seems to loop and take upto 50% of the processing power.

You are not getting any data or you are getting errors with the report. Run it in advanced mode and check out the logs.

hi

Errors with the report, and it shows the following the jde.log

973 Mon Feb 18 14:27:55 2002 runbatch.c382
INITIALIZING RUNBATCH job: 37654

973 Mon Feb 18 14:27:55 2002 ipcpub.c2901
process 973 <runbatch> registered in entry 58

973 Mon Feb 18 14:27:55 2002 runbatch.c631
Startup for User=SHARDMAN, Env=PY7333, Job#=37654

973 Mon Feb 18 14:27:58 2002 runbatch.c1101
RUNBATCH: Remote CP=1252, Remote OS=5, Local CP=1252, ConvertToASCII=0

973 Mon Feb 18 14:28:08 2002 jdekprnt.c4581
KNT0000165 - Loading of filter DLL failed

973 Mon Feb 18 14:28:08 2002 runbatch.c1233
Unable to Print the PDF file.

973 Mon Feb 18 14:28:08 2002 ipcpub.c3214
API ipcSawUnregisterProcV1 : process 973 unregistered in entry 58

973 Mon Feb 18 14:28:08 2002 runbatch.c1372
Job of type UBE failed with rcode = 1

973 Mon Feb 18 14:28:08 2002 jdb_ctl.c4474
JDB4200003 - OPEN TABLE NOT CLOSED = F986110

Before you submit your report, select advanced and then select override location, start logging and start tracing, then select okay.
Then submit your report and select local.
This will submit your report locally and create a log in your print queue directory on your hard drive.
This log should give you some insights.
You can also change your JDE.INI file to print out your jdedebug file.

Look at menu GH9013, printer setup for your printer. Click once in the "Custom" box and make sure your conversion filter strings are correct. You get this error when the strings are wrong or missing.
Note that the PostScript and PCL radio buttons use one of these conversion strings "under the covers".

The printer Definition Language was set up as *FORMS on the Dev Box, but when I compared this against the prod box it was diffrent as the Prod box was set up as *FORM. *FORM existed on the Dev box but it did not have the command string -s POSTSCIPT_PRINTER -l sender -f sendptf in the F986164 (in SYS7333). I added the string using the Oracle Table Data Editor then amended the Printer Defintion Language from *FORMS to *FORM for all the Forsmcape development printers.

Yep, that would do it... the -s parameter tells the UNIX box
which shell script to use to send the job to the printer,
the -l tells it which shared library, and the -f tells it
which function in the aforementioned shared library contains
the conversion filter.

Glad it helped!