E1: UBE: Common UBE Submission Issues
(Doc ID 1502927.1)
Last updated on JUNE 05, 2024
Applies to:
JD Edwards EnterpriseOne Tools - Version SP24 and laterInformation in this document applies to any platform.
Purpose
This document provides troubleshooting information and solutions to common issues that occur when submitting UBEs. UBE submission issues are any issues that prevent a batch record to be added to the Job Table F986110. If a job record is added to this table and it can be seen from Work with Submitted Jobs (WSJ) application, then the submission is considered to be successful. Any problem that happens after the record is added is considered a UBE processing or runtime issue.
For more information on the UBE Submission process refer to Doc ID 1498831.1
For information and issues that happen while processing the UBE refer to Doc ID 1502974.1 and Doc ID 1502985.1
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| Common Issues When Submitting UBEs |
| All Server Platforms |
| Issue 1: Invalid Job Queue |
| Issue 2: Invalid Enterprise Server name in F986130 |
| Issue 3: Unable to Insert Job Record in F989110 Because of Duplicate Job Number |
| Issue 4: Unable to Save Temporary Files on the Enterprise Server |
| Issue 5: Security Server is Disabled in Local JDE.INI |
| Issue 6: Spec Errors When Submitting from EnterpriseOne Web Client |
| Issue 7: Not Enough Disk Space on Web Server |
| Issue 8: "Not Authorized to Run Report" Errors in Server Process Log |
| Issue 9: Error "There was a problem with the server while running the business function IsXMLP2SPPresent" |
| Issue 10: Error "There was a problem with the server while running the business function IsPrinterMappingPresent" |
| Issue 11: Error "Security token not valid" when Submitting UBEs from a Windows/Fat Client |
| Issue 12: All UBEs fail with error, *ERRROR* LaunchUBE: LaunchUBE failed- JDEKDCL.h/UBEERRORCODE error 22 user |
| Unix and Linux Server Platforms |
| Issue 1: Server Name Mismatch in F986130 |
| Issue 2: All UBEs fail with error, *ERRROR* LaunchUBE: LaunchUBE failed[4] - Invalid Queuename - not defined for server |
| AS/400 Server Platform |
| Issue 1: UBEs fail to Submit when SQL Server Mode is Enabled |
| Issue 2: AS/400 User Permissions Issues |
| Issue 3: Custom Job Queue outside System Library on AS400 |
| Issue 4: Other AS/400 Issues |
| Other Less Common Issues |
| References |