My Oracle Support Banner

E1: GEN: Troubleshooting Guide for Errors During the Generation Process (Doc ID 1346836.1)

Last updated on AUGUST 25, 2021

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.


This document is a collection of "currently known" generation issues that can occur when generating objects to the F989998 and F989999 tables.

If an issue occurs during generation always try and collect corresponding generation logs from the generation workstation, and if running on demand generation get the corresponding kernel logs form the Enterprise Server.

Examples of errors can be:

  • Could Not Load Form: P0XXX Fetch Serialized Object Failed
  • [WEBJITI_ERROR] Demand generation failed for REPORT
  • Unable to Generate due to Errors: JavaGenException, JDESpecException
  • An Invalid Cell Record was Found
  • No Suitable Driver Error

Logging related to web client errors:



Refer to the following documents on collecting logs for GSC, and Support Development:

Critical files for problem determination.  When collecting information to troubleshoot an error on an HTML/Web client please include the following files:

Refer also to <Document 1352463.1> for Generation Process Setup, Best Practices and Known Issues when Starting Generation.




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
 Operating System & Workstation Issues
 Scenario 1: Windows 7 - Generator Gets Errors Running on Windows 7
 Scenario 2: UNIX/LINUX Issue
 Scenario 3: AS400 Issue
 Scenario 4: WEBDEV Client Tools Release 8.9x and above
 Scenario 5: SQL2005 Database Issue Causes a Generation Error
 Security Workbench
 Scenario 1: Generation and P00950
 On-Demand Generation
 Scenario 1: On Demand Generation Causes [WEBJITI_ERROR]
 Scenario 3: On Demand Generation for Reports Fails with Error: No Data Selection Information Found
 Scenario 4: On Demand Generation Fails With Error: CLI0102E Invalid Conversion (AIX Server Speific)
 Scenario 5: One or more forms fails during on demand generation SPEC_DATA_CREATE_FAILURE
 Scenario 6: [WEBJITI_ERROR] Demand generation failed for APPINFO-: null
 Batch & INI Files
 Scenario 1: GEN.BAT Configuration Causes Generation Error: The syntax of the command is incorrect
 Scenario 2: GEN.BAT Configuration Causes Generation Error: NoClassDefFoundError
 Scenario 3: Incorrect JDBJ.INI Settings Prevent Login to Generator
 RDA, FDA and DD Items
 Scenario 1: Generation Error Caused by Data Dictionary Item
 Scenario 2: Generation Error for UBES R34A400 and R34A410
 Scenario 3: Generation Error Caused by XML Document for UBE R04572JP BEING MALFORMED
 Generation Log Errors
 Scenario 1: Generation Errors in JDE.LOG: An Invalid Cell Record was Found
 Scenario 2: Generation Errors in Command Prompt Window: Cannot initialize Grid for Form. No Grid Columns present
 Scenario 3: Generation Errors in Command Prompt Window: Reload time in properties file is not found
 Scenario 4: Generation Errors in the JAS Logs: BSFNUBEDSTR-D9800150
 BSSV Data Structure
 Scenario 1: Full JAS Generation Skips BSSV Data Structure Objects
 Scenario 1: Generation Fails when Large Applications are Generated

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