NAV 2017 CU 2 - NAV Service Instance connection problem even its "Running"

barandeniz

Hello All, i have a customer who uses NAV 2017 CU 2. After the users connect to regarding NAV Instance, after a while some of the users can not connect to instance, and we have to restart the instance to solve the issue. But restarting the instance causes whole users drop hence its not a feasible solution at all. Any of you guys experienced an issue like that? The users who can not connect nav, gets the same error when the instance is stopped. but even some users get that error, some users can connect. The connection problem seems random across the users. Any ideas?

allenyyzhou

Hi

Have you checked the windows event log both in NAV server and Client side? Should have some errors related to NAV.

barandeniz

allenyyzhou wrote: »

Hi

Have you checked the windows event log both in NAV server and Client side? Should have some errors related to NAV.

https://gist.github.com/anonymous/c2607ec173a7cd3930990e702b5e6b31

geronimo

is there anything special happening in codeunit 50000? Like use of external tools to add item tracking or so?
It seems it hangs on the function RedLotKontrol.

Message <ii>(NavNCLDialogException): <ii>3223200004-4 NOLU STOK KARTI İÇİN LOT SEÇİLMEMİŞ
ExceptionStackTrace:
at Microsoft.Dynamics.Nav.Runtime.NavDialog.ALError(Guid automationId, String message)
at Microsoft.Dynamics.Nav.BusinessApplication.Codeunit50000.RedLotKontrol_Scope.OnRun()

allenyyzhou

barandeniz wrote: »

allenyyzhou wrote: »

Hi

Have you checked the windows event log both in NAV server and Client side? Should have some errors related to NAV.

https://gist.github.com/anonymous/c2607ec173a7cd3930990e702b5e6b31

Hi, based on your event log, I can not say what exactly happened, but seems your processed CU50000 in EventSubscription of OnBeforePostSalesDoc. You need to check CU50000.
If you can produce the same error by posting sales order, you are not away from solve it.
Try to let system run all the code in "PerformChecksBeforeSalesPosting" of CU50000, you shall get the same event log error.