Subsystem failing

Hi Folks,

This morning one of our subsystem UBE's "disappeared", i.e. when vieing subsystem processes via WSJ row exit the process was gone.

A re-start of the subsystem put everything back in order. A trawl through the server JDE logs gave me below. So I have two questions re same:

[1] Has anyone else hit similar issues and if so how if at all did you get them resolved?

[2] It looks to me as though some job submitted to the particular subsystem queue caused it to fall over. Can anyone interpret in any detail the contents of the log?

2660/2848 Sat Dec 01 01:07:19 2007 IPCPUB.C3135
process 2660 <jdequeue.exe> registered in entry 39

2660/2848 Sat Dec 01 01:07:23 2007 JDB_CTL.C6179
JDB9900155 - Failed to get non - zero AB Number.

2660/2848 Sat Dec 01 01:07:23 2007 JDB_UTL1.C9926
JDB9900808 - Failed to get Address number for user JDE

2660/2848 Sat Dec 01 01:07:23 2007 JDB_UTL1.C9937
JDB9900810 - Failed to populate address book number and user full name for ser JDE

2660/2848 Tue Dec 04 10:07:37 2007 IPCPUB.C4686
State information for process 2920, User=S_SUBSYST, Group=CNCADMIN , Environment=PD7334, Profile=NONE, Application=R46171, Client Machine=UNKNOWN, Version=OIL0007.

2660/2848 Tue Dec 04 10:07:37 2007 IPCPUB.C4700
Call stack for process 2920:
CWARE.dll/UNKNOWN/F4600ProcessLocationSelection
CWARE.dll/B4600330/F46095SelectPickingLocation

2660/2848 Tue Dec 04 10:07:37 2007 JDEQUEUE.C1041
Job of type UBE failed with rcode = 1


EnterpriseOne 8.0, SP22, W2K SP4, Oracle 9i.
Thanks in Advance!

It would help to know what platform and version you're running. You could put it into your signature to make it easier.

However, you are correct - it looks like R46171 was launched and caused a business function memory violation of some sort - specifically with B4600330.

I would look to see if this business function has been updated recently - maybe an ESU ? I would also look at any D46* data structures that might have been altered as well.

The solution for this might be several things. First of all, I doubt if any data has gone awry - though I really don't know what R46171 does myself (you should check to see what this UBE does). If its just a report - then theres no data harm.

Is the issue repeatable ? If you launch the same UBE with the same data selection - will it crash again ?

Next, it might not be the UBE itself that has the issue - but the custom version "OIL0007". If the issue is repeatable, then try creating a brand new version with the same settings.

Lastly, if you have recently updated this report or any of its business functions with an ESU recently - did you perform a full package build and deployment ? I always recommend a full package if a pretty large ESU has been implemented, rather than an update package.

Those are the first steps I would step through. Hope that helps.

Thanks for the input Jon. BTW, I did put version etc info in original post.