E1: XMLP: UBE Ends in Error on Server when Attached to a Report Definition (Doc ID 867182.1)

Last updated on MAY 30, 2017

Applies to:

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

Symptoms

Information Center: BI Publisher in the JD Edwards EnterpriseOne Tools and Technology ProductInformation Center: Troubleshooting BI Publisher in the JD Edwards EnterpriseOne Tools and Technology Product > Note 1460780.2

UBEs (usually custom) ends in error on server when attached to a BI Publisher Report Definition. There are no issues running the UBE on LOCAL, or running it without the Report Definition.

The respective UBE log shows that the RUNBATCH process crashed. Sometimes the log will contain memory violation errors pointing to specific business functions. For example:

Exception Code: C0000005   ACCESS_VIOLATION

or

Jul 14 13:36:16.706457 - 5228/5336 WRK:Starting jdeCallObject Exception code: C0000005 ACCESS_VIOLATION
Jul 14 13:36:16.987000 - 5228/5336 WRK:Starting jdeCallObject ====> Exception occurred with call stack:
ExpInterlockedPopEntrySListFault+0 C:\WINDOWS\system32\ntdll.dll
0000:00000000
Jul 14 13:36:16.987002 - 5228/5336 WRK:Starting jdeCallObject ====> Exception occurred with call stack:
ExpInterlockedPopEntrySListFault+0 C:\WINDOWS\system32\ntdll.dll
0000:00000000

This issue was originally reported on 8.12 with 8.98.1.1 but it is likely to occur in different tools and application releases.

On another report, the RUNBATCH processes crash when the UBE version is connected to BI Publisher Report Definition and the following message appears in the RUNBATCH log file:

KNT0000XXX - JDENET_ReceiveMsg failed. Error = 11

The issue is intermittent and appears to occur more frequently during high loads on the server. Issue is limited to Windows servers. Problem has been documented and addressed in <bug 11781336>, first included in tools release update 8.98.4.3.

A third variation of this problem was reported for tools release 8.98.4.4. and it is documented in <bug 13006639> included in 8.98.4.6.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms