Debugger broken in NAV2016 CU23?

EvR

Hi all,

We're having some major debugger issues since we've upgraded to 2016 CU23.

- Debuggers are freezing when hitting a breakpoint. The client process just carries on as if nothing happened and no break was hit.
- Debuggers are crashing with 'fatal debugger error'.
- Breakpoints aren't hit at all.

I've just tried installing a fresh new Windows 10 VM and we're having exactly the same issues there.
Has anyone else experienced this?

Greetings, Erik

allenyyzhou

Hi Erik

What version do you upgrade from? Is it possible that upgrading is not going so well? Like some objects are not upgraded? I assume 2016 CU23 demo DB won't have same issue.

EvR

The fresh install was a clean windows installation with an (obviously ) clean NAV install (demo DB).
2016 CU23 (NL local).

EvR

Faulting application name: Microsoft.Dynamics.Nav.Client.exe, version: 9.0.49146.0, time stamp: 0x599ecf6c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x08d48b81
Faulting process id: 0xc0c
Faulting application start time: 0x01d33370e5f08d3b
Faulting application path: C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe
Faulting module path: unknown
Report Id: 700a37e5-9f64-11e7-8134-00155d00b619
Faulting package full name:
Faulting package-relative application ID:

========

Type: System.InvalidOperationException
Message: Not an application method.
StackTrace:
bij Microsoft.Dynamics.Nav.Client.WinClient.ExceptionHandler.<>c__DisplayClass6.<DoRethrowWithCatchException>b__4()
bij Microsoft.Dynamics.Nav.Client.WinClient.NavClientErrorHandler.ExecuteAndCatchExceptions(Func`1 execute)
bij Microsoft.Dynamics.Nav.Client.WinClient.ExceptionHandler.DoExecute(Func`1 execute)
bij Microsoft.Dynamics.Nav.Client.WinClient.ExceptionHandler.DoRethrowWithCatchException(Exception exception, Boolean designMode)
Source: Microsoft.Dynamics.Nav.Client.WinClient
HResult: -2146233079

---

Type: System.InvalidOperationException
Message: Not an application method.
StackTrace:
at Microsoft.Dynamics.Nav.Runtime.MethodSourceInfo.GetSourceSpanAttribute(Type navMethodScopeType)
at Microsoft.Dynamics.Nav.Runtime.MethodSourceInfo.GetCurrentStatementSourceSpan(NavMethodScope scope)
at Microsoft.Dynamics.Nav.Runtime.Debugger.DebugEnvironment.<BuildStackTrace>b__1e(NavMethodScope scope)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
at Microsoft.Dynamics.Nav.Runtime.Debugger.DebugEnvironment.PerformBreakCallback(NavMethodScope methodScope, Exception exception)
Source: Microsoft.Dynamics.Nav.Ncl
HResult: -2146233079

EvR

Update:
It seems to happen after trying to debug any event subscriber.

NavNab

Hello @EvR

Maybe it is just a standard bug like the one in NAV 2017 CU6. Microsoft corrected this bug in NAV 2017 CU7.

EvR

I'd create a support ticket at Microsoft. But their retarded outdated system charges ISV's €360.00 to report bugs in their software... Microsoft and its worthless idiotic big company tendencies....