Hi.
We have a production server, where we host all our customers.
It works as a terminal server.
The server has NAV2013R2, 2015, 2016 and 2017 installed on it.
Recently, we started experiencing a problem with starting NAV clients (RTC).
It happens only when a developer or consultant open up Navision client on this server.
This doesn't have an effect on terminal sessions for our customers.
From the error message it says (sorry, the server is set to Danish language):
===========
Problemsignatur:
Navn på problemhændelse: APPCRASH
Programnavn: Microsoft.Dynamics.Nav.Client.exe
Programversion: 10.0.13682.0
Tidsstempel for program: 580f9fe5
Fejlmodulnavn: ntdll.dll
Fejlmodulversion: 6.2.9200.21971
Tidsstempel for fejlmodul: 57c044e5
Undtagelseskode: c0000005
Undtagelsesforskydning: 0000000000005715
OS-version: 6.2.9200.2.0.0.16.7
Landestandard-id: 1030
Flere oplysninger 1: 9aeb
Flere oplysninger 2: 9aeb5fe5bbde14dc92a6f81c02c7ea13
Flere oplysninger 3: 2a72
Flere oplysninger 4: 2a720775d67a69fdcef66b2f296d2ede
===========
From where I can understand that something bad happened to ntdll.dll file. But the variety of problem that this one brings is huge.
So, I didn't find an answer for this specific case as of yet.
Sometimes APPCRASH issue doesn't bother us, but then it reappears again.
I spotted interesting thing in the event log, as the error description points to the printer (I marked it bold in the text below)
Here is what I've found in the Event Logs:
==========
Navn på program med fejl: Microsoft.Dynamics.Nav.Client.exe, version: 10.0.13682.0, tidsstempel: 0x580f9fe5
Navn på modul med fejl: ntdll.dll, version: 6.2.9200.21971, tidsstempel: 0x57c044e5
Undtagelseskode: 0xc0000005
Forskydning med fejl 0x0000000000005715
Proces-id 0x38e8
Programmets starttidspunkt 0x01d2a3c97ecabb78
Programsti: C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe
Modulsti: C:\Windows\SYSTEM32\ntdll.dll
Rapport-id: be3b8c3c-0fbc-11e7-9450-0050569d1d38
Fuldt navn på program med fejl:
Relativt program-id for program med fejl:
==========
Program: Microsoft.Dynamics.Nav.Client.exe
Framework-version: v4.0.30319
Beskrivelse: Denne proces blev afsluttet pga. en ubehandlet undtagelse.
Undtagelsesoplysninger: System.AccessViolationException
ved System.Drawing.SafeNativeMethods.DeviceCapabilities(System.String, System.String, Int16, IntPtr, IntPtr)
ved System.Drawing.Printing.PrinterSettings.FastDeviceCapabilities(Int16, IntPtr, Int32, System.String)
ved System.Drawing.Printing.PrinterSettings.Get_PaperSizes()
ved Microsoft.Dynamics.Nav.Common.Printing.NavPrinterSettings..ctor(System.String)
ved Microsoft.Dynamics.Nav.Common.Printing.NavPrinterSettingsCache+<>c__DisplayClass1_0.<TryGetValue>b__0()
ved System.Lazy`1System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089.CreateValue()
ved System.Lazy`1System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089.LazyInitValue()
ved Microsoft.Dynamics.Nav.Common.Printing.NavPrinterSettingsCache.TryGetValue(System.String, Microsoft.Dynamics.Nav.Common.Printing.NavPrinterSettings ByRef)
ved Microsoft.Dynamics.Nav.Client.ServiceConnection+<>c.<AsyncWarmupPrinters>b__134_0()
ved System.Threading.Tasks.Task.Execute()
ved System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
ved System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
ved System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
ved System.Threading.Tasks.Task.ExecuteEntry(Boolean)
ved System.Threading.ThreadPoolWorkQueue.Dispatch()
==========
Did somebody experience that before?
We have a production server, where we host all our customers.
It works as a terminal server.
The server has NAV2013R2, 2015, 2016 and 2017 installed on it.
Recently, we started experiencing a problem with starting NAV clients (RTC).
It happens only when a developer or consultant open up Navision client on this server.
This doesn't have an effect on terminal sessions for our customers.
From the error message it says (sorry, the server is set to Danish language):
===========
Problemsignatur:
Navn på problemhændelse: APPCRASH
Programnavn: Microsoft.Dynamics.Nav.Client.exe
Programversion: 10.0.13682.0
Tidsstempel for program: 580f9fe5
Fejlmodulnavn: ntdll.dll
Fejlmodulversion: 6.2.9200.21971
Tidsstempel for fejlmodul: 57c044e5
Undtagelseskode: c0000005
Undtagelsesforskydning: 0000000000005715
OS-version: 6.2.9200.2.0.0.16.7
Landestandard-id: 1030
Flere oplysninger 1: 9aeb
Flere oplysninger 2: 9aeb5fe5bbde14dc92a6f81c02c7ea13
Flere oplysninger 3: 2a72
Flere oplysninger 4: 2a720775d67a69fdcef66b2f296d2ede
===========
From where I can understand that something bad happened to ntdll.dll file. But the variety of problem that this one brings is huge.
So, I didn't find an answer for this specific case as of yet.
Sometimes APPCRASH issue doesn't bother us, but then it reappears again.
I spotted interesting thing in the event log, as the error description points to the printer (I marked it bold in the text below)
Here is what I've found in the Event Logs:
==========
Navn på program med fejl: Microsoft.Dynamics.Nav.Client.exe, version: 10.0.13682.0, tidsstempel: 0x580f9fe5
Navn på modul med fejl: ntdll.dll, version: 6.2.9200.21971, tidsstempel: 0x57c044e5
Undtagelseskode: 0xc0000005
Forskydning med fejl 0x0000000000005715
Proces-id 0x38e8
Programmets starttidspunkt 0x01d2a3c97ecabb78
Programsti: C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe
Modulsti: C:\Windows\SYSTEM32\ntdll.dll
Rapport-id: be3b8c3c-0fbc-11e7-9450-0050569d1d38
Fuldt navn på program med fejl:
Relativt program-id for program med fejl:
==========
Program: Microsoft.Dynamics.Nav.Client.exe
Framework-version: v4.0.30319
Beskrivelse: Denne proces blev afsluttet pga. en ubehandlet undtagelse.
Undtagelsesoplysninger: System.AccessViolationException
ved System.Drawing.SafeNativeMethods.DeviceCapabilities(System.String, System.String, Int16, IntPtr, IntPtr)
ved System.Drawing.Printing.PrinterSettings.FastDeviceCapabilities(Int16, IntPtr, Int32, System.String)
ved System.Drawing.Printing.PrinterSettings.Get_PaperSizes()
ved Microsoft.Dynamics.Nav.Common.Printing.NavPrinterSettings..ctor(System.String)
ved Microsoft.Dynamics.Nav.Common.Printing.NavPrinterSettingsCache+<>c__DisplayClass1_0.<TryGetValue>b__0()
ved System.Lazy`1System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089.CreateValue()
ved System.Lazy`1System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089.LazyInitValue()
ved Microsoft.Dynamics.Nav.Common.Printing.NavPrinterSettingsCache.TryGetValue(System.String, Microsoft.Dynamics.Nav.Common.Printing.NavPrinterSettings ByRef)
ved Microsoft.Dynamics.Nav.Client.ServiceConnection+<>c.<AsyncWarmupPrinters>b__134_0()
ved System.Threading.Tasks.Task.Execute()
ved System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
ved System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
ved System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
ved System.Threading.Tasks.Task.ExecuteEntry(Boolean)
ved System.Threading.ThreadPoolWorkQueue.Dispatch()
==========
Did somebody experience that before?