web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / Preview Posting in Pay...
Microsoft Dynamics NAV (Archived)

Preview Posting in Payment Journal crashes RTC (NAV 2017)

(1) ShareShare
ReportReport
Posted on by Chris Greenwood 66

Hi,

Yesterday a customer found that clicking Preview Posting in the Payment Journal caused the RTC to crash. They have been using NAV2017 for several months and this was the first time they have seen this error. The error affected more than one user. After restarting the NAV service, they were able to use Preview Posting again. We cannot reproduce the error on a replica system, hence are unable to test any potential fixes.

Details

  • NAV version : 10.0.16996.0 (CU7)
  • Page: Payment Journal
  • Action: Preview Posting
  • RTC error message : The server "INSTANCENAME" was unable to process the request. The application will close.
  • Eventlog error message: <ii>(InvalidOperationException): <ii>An internal error has occurred. Cannot assign a scope id. The maximum number of methods for 5 231 has been exceeded.

From my understanding of this error, it occurs when setting up an event subscriber in codeunit 231 for the event OnRunPreview() in codeunit 19.

Has anyone seen this error?

NAV 2017 CU15 has a fix (ID 254648) for a similar error, but the object ID mentioned is different (8, not 5 231). Does anyone know whether this would also fix our customer's problem?

Thanks & regards,

Chris

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    azelaya59 Profile Picture
    azelaya59 2,807 on at

    Chris

    I have not experienced this behavior, but the event log message: <ii>(InvalidOperationException): <ii>An internal error has occurred. Cannot assign a scope id. The maximum number of methods for 5 231 has been exceeded and the fact you had to restart the NAV instance leads me to believe you have a "cache" situation. I would suggest taking a look at the open sessions and "killing" those which have opened for many days. They may be "orphaned". Look at this blog from Olof Simren on creating a "Kill Session" on the page 9506 (Sessions) www.olofsimren.com/kill-sessions-in-dynamics-nav

    Good Luck!

  • Chris Greenwood Profile Picture
    Chris Greenwood 66 on at

    Hi Alfredo,

    Many thanks for your reply - what you are saying makes sense to me and if/when it happens again, we will definitely scrutinize the sessions before going for the restart. If it's possible to isolate the issue to a few long-running sessions, maybe it would be possible to implement job queue process to kill long-running sessions automatically. But obviously this would only worth doing if the issue happens often and in the absence of a permanent solution !

    Chris

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans