NAV2016 Build 43897/44365: Recursion error when reversing a large Gen. Journal

(0) Share

Report

Posted on by Community Member

Hello,

has anyone a proven solution for the following recursion error:

Our client wants to reverse the journal of a close income statement, that has been posted with dimensions and additional reporting currency. They get the error, that NAV is running out of memory because of to many recursive function calls.

In the debuggers call stack you can see that the not subscribed event trigger OnAfterInsertGlobalGLEntry() of codeunit 12 has been fired from within function FinishPosting more then 4900 times.

Our temporary solution was commenting out the OnAfterInsertGlobalGLEntry() event trigger call in codeunit12.FinishPosting(). After that it works as it should.

IMO it seems to be not a very stable solution how events are implementetd then. It can't be the solution that the size of general journals to reverse depends on the NAV servers memory?!

Best regards,

Marco

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

keoma 32,729 on at

Like (0)

Report

if it is not customized, please open a ticket at microsoft support.

please write a feedback, if they provide a solution.

if it is a known bug, it will be solved with an upcoming hotfix or CU.

Was this reply helpful? Yes No
Sergisoft 20 on at

Like (0)

Report

Hi Marco,

I had the same issue at posting a big journal and I get it temporary sorted doing the same change you did.

Hopefully MS will get it sorted on next CU.

Thanks,

Sergi.

Was this reply helpful? Yes No
Abz@Tecman 10 on at

Like (0)

Report

Hello

I've got the same scenario where a user is posting a single cash receipt journal line that is applied against 1200+ customer ledger entries.... previous postings have gone through fine.

Did anyone get a permenant long term resolution for this?

Was this reply helpful? Yes No
Suggested answer

Amol Salvi 18,698 on at

Like (0)

Report

Hi,

If you are still facing this issue then open incident to MS so they can provide the solution

Was this reply helpful? Yes No