JDE UBE failed (status E): how to read jde.log and jdedebug.log

Locate and read the failure

1. 1In Work With Submitted Jobs, note the job number (e.g. 123456) and the server it ran on.
2. 2On that enterprise server, go to the PrintQueue directory (typically B9\PrintQueue or the path set in jde.ini under [NETWORK QUEUE SETTINGS]).
3. 3Find the subfolder for the job number, containing the .PDF, .CSV if generated, and log files.
4. 4Open jde.log (or jde_<PID>.log on newer releases) in that folder or in the server's System\Bin32 or logs directory, most recent entries at the bottom.
5. 5Search jde.log for the job number and for 'Error' or 'Fatal' near the timestamp the job started.
6. 6If jde.log alone does not show root cause, enable jdedebug.log by setting Debug=1 and [DEBUG] output file in jde.ini, then resubmit.
7. 7Common causes at this point: missing processing option template, data selection referencing a deleted UDC, an RDA/BSFN that threw an exception, or a security setting blocking table access.
8. 8Cross-check the job's specific PDF - a blank or partial PDF plus an E status usually means the report aborted mid-section, which jdedebug.log will show as the last event ID processed.
9. 9If the job never produced a subdirectory at all, the problem is upstream: the job never left the enterprise server queue - check jde.ini [JDENET] settings and that the kernel processes (jdenet_k) are running.

jde.log vs jdedebug.log

; jde.ini [DEBUG] section example
Debug=1
JobFile=jde_%job%.log
JobFileMax=1
SectionDebug=1
TAMDebug=1

Server-specific log locations

Common pitfalls

• !Reading jde.log on the wrong server - a UBE can be routed to any enterprise or batch server in the server group, so check which one the job actually ran on before searching logs.
• !Forgetting to turn Debug back off after troubleshooting - jdedebug.log grows fast and will fill disk on a busy batch server.
• !Assuming the PDF being blank means no output logic ran, when it often means a section-level error stopped generation partway through.
• !Searching jde.log by time only, not job number - concurrent jobs interleave their log lines, so filter by the job's PID or job number token.
• !Not checking F986110/F986114 job control tables via SQL when the log files themselves were purged by a log-rotation policy.