Nav 2016 cu7 Debugger and RTC crash

(0) Share

Report

Posted on by Community Member

Hello All,
2 weeks back we applied cu7 on our NAV 2016 cu2 dev environment. From that moment we are facing issues while launching debugger or RUN RTC from "NAV Development Environment". But the issue never pops up if "NAV Development Environment" is launched as "Administrator". Is this is bug or have we gone wrong somewhere?

Expecting your quick feedbacks.

Thanks

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

Suggested answer

Nareshwar Raju Vane... 5,596 on at

Like (0)

Report

Hi Anoop,

Can you attach the Event Viewer log please?

Did you try on any other machines?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Forgot to put the error message recorded on Event Viewer

Faulting application name: Microsoft.Dynamics.Nav.Client.exe, version: 9.0.45834.0, time stamp: 0x5723b44c

Faulting module name: KERNELBASE.dll, version: 6.3.9600.18202, time stamp: 0x569e7eb1

Exception code: 0xe0434352

Fault offset: 0x0000000000008a5c

Faulting process id: 0x3fd4

Faulting application start time: 0x01d1d053f7fbf0f6

Faulting application path: C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 35f2366a-3c47-11e6-8162-000d3a22536f

Faulting package full name:

Faulting package-relative application ID:

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Nareshwar,

Thanks for the response. We are restricted to work on this machine alone for development. I am copying the event viewer message here below

Faulting application name: Microsoft.Dynamics.Nav.Client.exe, version: 9.0.45834.0, time stamp: 0x5723b44c

Faulting module name: KERNELBASE.dll, version: 6.3.9600.18202, time stamp: 0x569e7eb1

Exception code: 0xe0434352

Fault offset: 0x0000000000008a5c

Faulting process id: 0x3fd4

Faulting application start time: 0x01d1d053f7fbf0f6

Faulting application path: C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 35f2366a-3c47-11e6-8162-000d3a22536f

Faulting package full name:

Faulting package-relative application ID:

Was this reply helpful? Yes No
Suggested answer

Nareshwar Raju Vane... 5,596 on at

Like (0)

Report

Hi Anoop,

There must be a version conflict between your Dev environment and Dynamics NAV Windows client.

Follow this link: msdn.microsoft.com/.../dn757163(v=nav.90).aspx

Hope it helps.

Was this reply helpful? Yes No
gert@lynge.org on at

Like (2)

Report

It is a NAV bug introduced in NAV 2016 CU7 and NAV 2015 CU20. Caused by NAV looking for running RTC processes in a new way (because MS eliminated some old COM code from the platform). This "new way" was a little to aggressive and tried to get process info. of processes the current user did'nt have rights to look at (that's why it works as admin.).

It will also give you problems if you try to run the session list from RTC (which is in fact the debugger - I know :-) ) and if you try to do any of it on a terminal server with a user which does not have rights to look at the other users processes.

It is fixed in NAV 2016 CU9 and NAV 2015 CU21 which will be released "real soon now" on The NAV Team Blog https://blogs.msdn.microsoft.com/nav/

I guess it will be available on the blog today or in a couple of days...

I got a preview of the NAV 2016 CU9 running and can confirm 1st hand that it is in fact fixed...

If you are Danish speaking, I've blogged about the bug in Danish here: http://blog.systemconnect.dk/?p=943

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Hi Nareshwar,

I can confirm that there is no version conflict. The versions match in the error reports.

If there were version issues it should have crashed even while running as administrator.

There has to be something else.

Thanks

Anoop

Was this reply helpful? Yes No
Suggested answer

Nareshwar Raju Vane... 5,596 on at

Like (0)

Report

Hi Gert,

Thank you for the insight. Never thought it is a bug in the first place since, in most cases, its just the version conflict.

Thank you again for sharing.

Was this reply helpful? Yes No
Suggested answer

Nareshwar Raju Vane... 5,596 on at

Like (0)

Report

Hi Anoop,

As Gert mentioned it is a bug from Microsoft's end. As he further mentioned, it will be fixed in CU9.

As a workaround, you can set the dev environment to run as admin.

Hope it helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Nareshwar and Gert,

Thanks for the updates, do we have and official confirmation of the same?

Anoop

Was this reply helpful? Yes No
Suggested answer

gert@lynge.org on at

Like (2)

Report

No problem.

I hope CU9 will be the best NAV 2016 so far :-)...

All earlier versions have had bugs which was a hassle for us.

Until CU7 it was really poor report performance when using ClickOnce.

And after that this issue and a strange periodic metadata error on a few pages (mostly G/L Journals when running check and/or post). MS have promised me the metadata errror is also gone with CU9 - and I have not seen it so far :-).

Was this reply helpful? Yes No