E9.2 BI Publisher Intermittent Communications Failure

James Monroe

Active Member
Good afternoon. Wanted to see if this rang a bell with anyone. We use the embedded BI Publisher in JDE to print checks. These checks automatically print as defined in the Report Definition delivery options. We are seeing periodically that a check batch will not print. Reviewing the Delivery info from Submitted jobs/View Report Definition, we will see ' Communication Failure' for those that did not print. When there is no Comm Failure, it says Submitted. If we do a Redeliver, it will then print.

We are on E1 9.2, tools One other note, our Enterprise Server is hosted by an offsite third party host service, the print server is on AWS. So it would seem that intermittently when JDE sends check output to the print server it cannot reach the print server and fails. JDE has processed 39 check batches since April 1, 3 have failed with the Comm Failure.

Any thoughts would be appreciated.


VIP Member
In these kinds of intermittent printer comms failure scenarios I recommend a local print queue on the Enterprise Server (where the BIP kernel is running) which in turn points to the remote print queue/printer. You can then put monitoring on the local print queue, detect failures, alert, retry from local queue etc.

I tend to use local print queues on the enterprise server regardless of OS platform for all printers. Maybe it is my old way of thinking of things but I feel like print jobs submitted in good faith from JDE that don't error for other reasons should eventually make their way to the destination and a "system operator" should sort out/handle the intermittent failures from a system console versus demanding that the end-user reprint.

Of course, my approach isn't very good without monitoring/alerting and an active system operations team. The benefit of letting the user know that there has been a print failure is that they can use the JDE UI to reprint output be it standard PDF or BIP output.


Hi James,
We are facing the same issue as you got with BIP and intermittent printer output failure. resubmintting the print works fine. I found into the a debug log a select that didn't retreive the job in F986110 but doing a select of searching with submitted jobs application is able to retreive the record. ORacle support guys isn't able to help us and i don't thing he asked to the developper teams. How did you fix you issue?
Nov 24 10:08:44.126046 dbresrq.c179 - ORACLE DBRsetReq conn=0000000000e652a0 requ=00000000029aa170 NAJDERAC01 (CMSTPD1_SHARED)
Nov 24 10:08:44.126057 dbsql_s.c1983 - SELECT * FROM SVM920.F986110 WHERE ( JCEXEHOST = 'VBQPD ' AND JCJOBNBR = 672195.000000 ) ORDER BY JCEXEHOST ASC,JCJOBNBR ASC
Nov 24 10:08:44.126330 jdb_exef.c2441 - Exiting JDB_SelectKeyed with Success
Nov 24 10:08:44.126335 dbfetch.c107 - ORACLE DBFetch conn=0000000000e652a0 requ=00000000029aa170 maxrows=1
Nov 24 10:08:44.126544 dbfetch.c140 - ORACLE DBFetch conn=0000000000e652a0 requ=00000000029aa170 fetched=0
Nov 24 10:08:44.126545 jdb_exef.c4235 - No More Data found (hRequest 0000000001b26130)
Nov 24 10:08:44.126547 jdekprnt.c4651 - JDB_SelectKeyed failed for F986110 in prtPDF_PrintEx API. Job#: 672195