R09801 won't run on server

R09801 won\'t run on server

This problem is in my SQL test environment. It runs fine locally. The error message on the pdf is "Business Function EditForPosting at line 308 for Event 13 in Section Detail Section - F0011 has caused a memory violation. Also below is an except from the log file.

4008/4152 Fri Mar 17 10:06:26 2006 RUNBATCH.C384
INITIALIZING RUNBATCH job: 316

4008/4152 Fri Mar 17 10:06:26 2006 IPCPUB.C3135
process 4008 <runbatch.exe> registered in entry 14

4008/4152 Fri Mar 17 10:06:26 2006 RUNBATCH.C680
Startup for User=PSULLIV, Env=PY7333, Job#=316

4008/4152 Fri Mar 17 10:06:26 2006 RUNBATCH.C697
bAPListening=0

4008/4152 Fri Mar 17 10:06:28 2006 IPCPUB.C4686
State information for process 4008, User=PSULLIV, Group=CNCADMIN , Environment=PY7333, Profile=NONE, Application=R09801, Client Machine=UNKNOWN, Version=PAT.

4008/4152 Fri Mar 17 10:06:28 2006 IPCPUB.C4700
Call stack for process 4008:
CFIN.dll/UNKNOWN/EditForPosting
CALLBSFN.dll/BLM0001/SetError_Batch


Has anyone seen this error before? Thanks in advance for your help.

Patty

Re: R09801 won\'t run on server

Patty,

Have you seen this on the KG

Summary: Xe and ERP 8.0 Post Program (R09801) Ends in Error on SP19 or later
Details: Title: Xe and ERP 8.0 Post Program (R09801) Ends in Error on SP19 or later

Abstract: Documents an error occurring when the post program is submitted to the enterprise server after installing SP19 or later service packs in Xe or ERP 8.0.

Issue

Two issues exist with the post program after installing Service Pack 19 or a later service pack release:

1) Batches submitted to post on the enterprise server will end in error. The batch status remains "In Use."
The problem has been identified on NT servers but may not be limited to one server. The General Ledger
Post Report (R09801) generated by the post program displays one of the following errors:

Event Rule: EditForPosting at line 297 for Event 13 in Section Detail Section - F0011 has caused a memory violation

Event Rule: EditForPosting at line 308 for Event 13 in Section Detail Section - F0011 has caused a memory violation.

The post program does complete successfully if submitted locally. The post program completes successfully on the server if logging is active.

2) Other memory leaks and errors can occur.

Resolution

To resolve these issues, install the ESUs for the following SARs. Not all SARs are contained in the same ESU.

Xe ERP 8.0
5986243 6012571
5864254 included in base release
5819162 included in base release
6028186 6112290
6086271 6099291
6119088 6125681
6095696 6125331

Re: R09801 won\'t run on server

Cleo

Yes I did. I had a call open with Oracle and they sent me the exact same thing.

I want to share with you what I found with this problem. I built a full client and server JD7333 package for testing of the ESUs they suggested I apply to solve the memory error. I had applied the Baseline JD18810 ESU a couple of years back. I ran a test BEFORE applying any of the aforementioned ESU and posting ran on the server! I also tested it with our data and it also worked. This posed a dilemma.

As I always suspected B0900055 is the offending business function. After applying SP23_L1 to our current Oracle/Unix database in December, journal posting on the server was giving us a bogus sub ledger type error. I pulled B0900055 from ESU JD23931 to fix the problem. This ESU has been superseded by JD24118. In the list of SARs and associated ESU's they gave me only JD24118 has B0900055 in it. B0900055 is the same in JD24118 as the one I pulled for JD23931.

To resolve both issues (memory error on SQL server and bogus sub ledger type error), I did an advance get of the JD18810 version of B0900055 and then compared the C++ code that validated sub ledger type against the UDC tables from the JD24118 ESU and hand entered the change. It solved both problems. I know this is a cowboy approach, but they left me no other choice. I don't believe applying the list of ESU they sent me would have fixed the problem and we have a fair amount of customization. There were too many objects affected by these ESUs. It seems whenever I install something new, something else breaks, SP23_L1 is one example.

Our go live date for the SQL migration is the first week of June and posting on the server is a dropped dead issue.

Thanks for responding.

Patty

Re: R09801 won\'t run on server

Good job Patty!

It sux to have to take 4000 objects from ESUs to fix 1 bug.
But sometimes you have to be the "cowgirl".

Best Regards,