Alpha India Group

Alpha India Group => TC - Support => AIG Traffic Controller => AIG Software => TC Solved Issues => Topic started by: max1806 on August 23, 2020, 10:02:53 AM

Title: [SOLVED] .NET-related CTD
Post by: max1806 on August 23, 2020, 10:02:53 AM
Hi,

first of all I would like to thank everybody involved at AIG for their amazing work and populating our sims with such accurate and diverse AI flights!

I have been using TC for a a while now and have noticed several CTDs which seem to be related to .NET. Sometimes TC crashes after a few minutes after start, sometimes it runs for more than an hour.

Here are the three logs from Windows event viewer, I hope you can still work with them despite being in German. If you need any other information, I'll be glad to provide it.

----------------------------------------------------

Anwendung: AIGTech - Traffic Controller.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund eines internen Fehlers in der .NET-Laufzeit beendet. bei IP 00007FFBB296F227 (00007FFBB2870000) mit Exitcode 80131506.

----------------------------------------------------

Name der fehlerhaften Anwendung: AIGTech - Traffic Controller.exe, Version: 0.3.2.0, Zeitstempel: 0xc6e565ac
Name des fehlerhaften Moduls: clr.dll, Version: 4.8.4200.0, Zeitstempel: 0x5ee03503
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000ff227
ID des fehlerhaften Prozesses: 0x2040
Startzeit der fehlerhaften Anwendung: 0x01d6792908b7f278
Pfad der fehlerhaften Anwendung: C:\Users\Max\Downloads\AIG_TrafficController_0.3.1.2\AIGTech - Traffic Controller.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Berichtskennung: 43e75f96-df08-4925-8f42-bf397a7400ee
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

-------------------------------------------------------------

Fehlerbucket 1573642781736624269, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: AIGTech - Traffic Controller.exe
P2: 0.3.2.0
P3: c6e565ac
P4: clr.dll
P5: 4.8.4200.0
P6: 5ee03503
P7: c0000005
P8: 00000000000ff227
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94BA.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95C4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95D5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95D3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95E4.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AIGTech - Traffi_3af794862d875e123a15d8822eafbccfe2bedef_78534f04_0f6dced0-7987-4c36-be22-8a1adb6f2a9b

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 43e75f96-df08-4925-8f42-bf397a7400ee
Berichtstatus: 268435456
Bucket mit Hash: f4a8f89d415f257825d6b3c5c0c4e08d
CAB-Datei-Guid: 0
Title: Re: .NET-related CTD
Post by: davidsuter on September 26, 2020, 11:52:16 PM
Same issue that I'm having.
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on September 27, 2020, 05:37:27 AM
I am still running tests to find the cause for it.. So far our own Crash Handler is unbale to identify the cause :-\ ???
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on October 25, 2020, 11:46:21 AM
good news: I think I have found the cause - at least no crashes so far on my 3 long term runnings.
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on October 25, 2020, 04:44:46 PM
Sounds great! I'll be happy to provide updates as soon as a new version is available.
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on October 26, 2020, 04:26:22 PM
thanks, new Version will still take some time. I am currently reqorking the internal sector system for a better performance :stirpot:
Title: Re: [OPEN] .NET-related CTD
Post by: bopalka on October 27, 2020, 07:34:00 PM
Ah, was wondering why some of my traffic was not showing at my arrival airport on my last flight.  This will save me from posting a bug report.. unless this counts as one.  LOL!   ;D
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on October 28, 2020, 07:08:54 PM
I am currently on a short flight with version 0.3.3.0 and unfortunately encountered a CTD with the same error messages again.
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on October 28, 2020, 07:11:18 PM
can you post the log again?
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on October 28, 2020, 07:31:33 PM
Sure, these are the three entries:
-----------------------------------------------------------------------------
Fehlerbucket 1450051154690254188, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: AIGTech - Traffic Controller.exe
P2: 0.3.3.0
P3: e4b345a4
P4: clr.dll
P5: 4.8.4250.0
P6: 5f2a059c
P7: c0000005
P8: 0000000000166025
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B1A.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C34.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C44.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C42.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C53.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AIGTech - Traffi_f623b3253ba35e62d8918a14672863b94b8c57c_23a456f9_01160408-203c-473b-b2d6-40cf1f145a42

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: afa38b00-2dec-4758-8ad5-2890d1f03b61
Berichtstatus: 268435456
Bucket mit Hash: 89572e06984ad1d2f41f9dd7ad75256c
CAB-Datei-Guid: 0
-----------------------------------------------------------------------------------------------------------------
Name der fehlerhaften Anwendung: AIGTech - Traffic Controller.exe, Version: 0.3.3.0, Zeitstempel: 0xe4b345a4
Name des fehlerhaften Moduls: clr.dll, Version: 4.8.4250.0, Zeitstempel: 0x5f2a059c
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000166025
ID des fehlerhaften Prozesses: 0x2dc
Startzeit der fehlerhaften Anwendung: 0x01d6ad51daa6fb70
Pfad der fehlerhaften Anwendung: C:\Users\Max\Downloads\AIG_TrafficController_0.3.1.2\AIGTech - Traffic Controller.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Berichtskennung: afa38b00-2dec-4758-8ad5-2890d1f03b61
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
--------------------------------------------------------------------------------------------------------
Anwendung: AIGTech - Traffic Controller.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund eines internen Fehlers in der .NET-Laufzeit beendet. bei IP 00007FF8DCBE6025 (00007FF8DCA80000) mit Exitcode 80131506.
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on October 28, 2020, 07:35:15 PM
thanks, I will look at it again :stirpot:
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on October 28, 2020, 07:38:28 PM
what .NET Version are you using?
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on October 28, 2020, 08:11:03 PM
Seems like quite a few are installed (s. attachment)
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on October 29, 2020, 04:33:55 AM
please install .NET 4.8
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on October 31, 2020, 03:02:02 PM
Looks like it is already installed and was just not showing up in the app that I screenshot.
When  I run v4.8 setup, it says that it is already installed and the registry entries confirm this.
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on October 31, 2020, 03:07:24 PM
try to repair 4.8
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on November 01, 2020, 10:48:16 AM
I ran the repair setup but unfortunately TC keeps crashing with the same error.
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on November 01, 2020, 10:53:26 AM
I found this possible solution:

Quote

Had the same exact error on WinXP box with latest build of my .NET 4 code. Checked previous builds - now they crash too! Ok, so it's not me :). No suggestions here/above helped.

Much more recent (2018-05-09) report of the same problem: Application Crash with exit code 80131506.

    A: We were receiving a similar error, but we believe ours was caused by the Citrix memory optimizer.
    The resolution was to force a regeneration of the .Net core libraries on the host(s) where the issue was occurring:
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update /force

Root cause is still unknown (machine is not being updated and has little use), but that did it for me!

maybe you can give it a try
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on November 01, 2020, 04:15:56 PM
I did that as well and just witnessed another crash  :-\
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on November 01, 2020, 04:23:56 PM
ok, more then strange. What Antivirus tool are you using?
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on November 01, 2020, 04:35:41 PM
Just Windows Defender
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on November 01, 2020, 04:59:49 PM
when was the last time you run a Windows integrity check?
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on November 01, 2020, 05:04:00 PM
I don't recall having ever run that. I suppose I should?
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on November 01, 2020, 05:14:47 PM
yeah, The ErrorID your log shows is often related to a bug that was in an older .NET version but was resolved. Since no other report has yet been posted here with the same ErrorID it seems it is specific to your system. So we need to find the cause for it on your system:


sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth


run the 2 lines as admin in CMD
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on November 01, 2020, 05:18:12 PM
Thanks for the explanation and your patience.
I'll do that as soon as I have time to, next weekend at the latest.
Title: Re: [OPEN] .NET-related CTD
Post by: Stichi24 on November 01, 2020, 11:54:16 PM
Just updated to V 0.3.3.0 and its frozen not responding. Missing the previous version (had no issues with it)
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on November 02, 2020, 05:12:09 AM
Quote from: Stichi24 on November 01, 2020, 11:54:16 PM
Just updated to V 0.3.3.0 and its frozen not responding. Missing the previous version (had no issues with it)

please make a seperate topic and post the logs
Title: Re: [OPEN] .NET-related CTD
Post by: bopalka on November 04, 2020, 04:25:48 AM
@Stichi24, just curious.. is what you saw with or without the sim running?  I did notice that the last time I fired up TC without P3D running it became unresponsive and I had to close via the task manager.


Thanks,
Bryan
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on November 06, 2020, 06:26:07 PM
Alright, I ran the commands you provided. To me, it doesn't look like anything was changed. I'll check what happens during a flight tomorrow.
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on November 07, 2020, 11:41:13 AM
Unfortunately, the crash with the same error messages still appears  :-\
Title: Re: [OPEN] .NET-related CTD
Post by: davidsuter on November 11, 2020, 02:52:06 AM
Quote from: max1806 on October 28, 2020, 07:31:33 PM
Sure, these are the three entries:
-----------------------------------------------------------------------------
Fehlerbucket 1450051154690254188, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: AIGTech - Traffic Controller.exe
P2: 0.3.3.0
P3: e4b345a4
P4: clr.dll
P5: 4.8.4250.0
P6: 5f2a059c
P7: c0000005
P8: 0000000000166025
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3B1A.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C34.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C44.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C42.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C53.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AIGTech - Traffi_f623b3253ba35e62d8918a14672863b94b8c57c_23a456f9_01160408-203c-473b-b2d6-40cf1f145a42

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: afa38b00-2dec-4758-8ad5-2890d1f03b61
Berichtstatus: 268435456
Bucket mit Hash: 89572e06984ad1d2f41f9dd7ad75256c
CAB-Datei-Guid: 0
-----------------------------------------------------------------------------------------------------------------
Name der fehlerhaften Anwendung: AIGTech - Traffic Controller.exe, Version: 0.3.3.0, Zeitstempel: 0xe4b345a4
Name des fehlerhaften Moduls: clr.dll, Version: 4.8.4250.0, Zeitstempel: 0x5f2a059c
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000166025
ID des fehlerhaften Prozesses: 0x2dc
Startzeit der fehlerhaften Anwendung: 0x01d6ad51daa6fb70
Pfad der fehlerhaften Anwendung: C:\Users\Max\Downloads\AIG_TrafficController_0.3.1.2\AIGTech - Traffic Controller.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Berichtskennung: afa38b00-2dec-4758-8ad5-2890d1f03b61
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
--------------------------------------------------------------------------------------------------------
Anwendung: AIGTech - Traffic Controller.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund eines internen Fehlers in der .NET-Laufzeit beendet. bei IP 00007FF8DCBE6025 (00007FF8DCA80000) mit Exitcode 80131506.

I'm Encountering this too...I have NET 4.8...It is Installed.
Title: Re: [OPEN] .NET-related CTD
Post by: mspencer on November 17, 2020, 04:55:24 AM
Getting this too.. specifically at EKCH

Faulting application name: AIGTech - Traffic Controller.exe, version: 0.3.3.0, time stamp: 0xe4b345a4
Faulting module name: clr.dll, version: 4.8.4250.0, time stamp: 0x5f2a059c
Exception code: 0xc0000005
Fault offset: 0x0000000000166025
Faulting process id: 0x2d84
Faulting application start time: 0x01d6bc9077c8af35
Faulting application path: C:\Users\Matt\Documents\Prepar3D v5 Add-ons\AIG Traffic Controller\AIGTech - Traffic Controller.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 113c770b-0cae-4b2b-a802-79bc46161609
Faulting package full name:
Faulting package-relative application ID:
Title: Re: [OPEN] .NET-related CTD
Post by: max1806 on October 09, 2021, 12:01:41 PM
Hi Kai,

unfortunately it seems like the .NET issue is back with version 0.4.1.1.
I got two CTDs today, one during descent into LIRF, one during descent into LFPG.
Here are the latest logs from a crash at 13:43:34:

Name der fehlerhaften Anwendung: AIGTech - Traffic Controller.exe, Version: 0.4.1.1, Zeitstempel: 0x8f2c193c
Name des fehlerhaften Moduls: clr.dll, Version: 4.8.4300.0, Zeitstempel: 0x5f7e616e
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000091105
ID des fehlerhaften Prozesses: 0x1798
Startzeit der fehlerhaften Anwendung: 0x01d7bcf12f41cfd5
Pfad der fehlerhaften Anwendung: C:\Users\Max\Downloads\AIG_TrafficController_0.3.3.2\AIGTech - Traffic Controller.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Berichtskennung: d18cc32a-df6a-48c9-909c-4af346465fb2
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Anwendung: AIGTech - Traffic Controller.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund eines internen Fehlers in der .NET-Laufzeit beendet. bei IP 00007FFAB05C1105 (00007FFAB0530000) mit Exitcode 80131506.
Title: Re: [OPEN] .NET-related CTD
Post by: matthiasmjf@yahoo.de on November 07, 2021, 12:11:17 PM
Hi,

since today I also have a .net related issue. basically the traffic manager starts up, loads everything and when teh window is supposed to appear it just closes down. No matter whether I open it by itself or it starts up triggered by P3d.

Here are the logs:

Name der fehlerhaften Anwendung: AIGTech - Traffic Controller.exe, Version: 0.4.1.1, Zeitstempel: 0x8f2c193c
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00007ffd78d8e520
ID des fehlerhaften Prozesses: 0x6430
Startzeit der fehlerhaften Anwendung: 0x01d7d3cf420be97d
Pfad der fehlerhaften Anwendung: C:\Users\mace\Desktop\AIG_AIManager_0.8.4.6 (1)\AIGTC\AIGTech - Traffic Controller.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: 351c7b94-c552-425c-9d12-ae37e99c9197
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:


Anwendung: AIGTech - Traffic Controller.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.NullReferenceException
   bei AIGTech.TrafficController.Classes.Files.XMLFile_AirportInformation.readRunwaysNode(AIGTech.TrafficController.Classes.Files.XML_AirportInformation, System.Xml.XmlNode)
   bei AIGTech.TrafficController.Classes.Files.XMLFile_AirportInformation.readAirportNode(System.Xml.XmlNode)
   bei AIGTech.TrafficController.Classes.Files.XMLFile_AirportInformation.LoadFile(System.String)
   bei AIGTech.TrafficController.Classes.Manager.Moduls.AirportManager.loadData()
   bei AIGTech.TrafficController.Classes.Manager.Moduls.AirportManager..ctor(AIGTech.TrafficController.Classes.Manager.TrafficManager)
   bei AIGTech.TrafficController.Classes.Manager.TrafficManager..ctor(AIGTech.TrafficController.Controller.TCController)
   bei AIGTech.TrafficController.Controller.TCController.<ConnectToSim>b__43_4(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
   bei System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.DispatcherOperation.InvokeImpl()
   bei MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   bei MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   bei System.Windows.Threading.DispatcherOperation.Invoke()
   bei System.Windows.Threading.Dispatcher.ProcessQueue()
   bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   bei System.Windows.Application.RunDispatcher(System.Object)
   bei System.Windows.Application.RunInternal(System.Windows.Window)
   bei AIGTech.TrafficController.App.Main()


Hope there will be a solution..

Best,

Mace

Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on November 07, 2021, 12:14:28 PM
Quote from: matthiasmjf@yahoo.de on November 07, 2021, 12:11:17 PM
Hi,

since today I also have a .net related issue. basically the traffic manager starts up, loads everything and when teh window is supposed to appear it just closes down. No matter whether I open it by itself or it starts up triggered by P3d.

Here are the logs:

Name der fehlerhaften Anwendung: AIGTech - Traffic Controller.exe, Version: 0.4.1.1, Zeitstempel: 0x8f2c193c
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00007ffd78d8e520
ID des fehlerhaften Prozesses: 0x6430
Startzeit der fehlerhaften Anwendung: 0x01d7d3cf420be97d
Pfad der fehlerhaften Anwendung: C:\Users\mace\Desktop\AIG_AIManager_0.8.4.6 (1)\AIGTC\AIGTech - Traffic Controller.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: 351c7b94-c552-425c-9d12-ae37e99c9197
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:


Anwendung: AIGTech - Traffic Controller.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.NullReferenceException
   bei AIGTech.TrafficController.Classes.Files.XMLFile_AirportInformation.readRunwaysNode(AIGTech.TrafficController.Classes.Files.XML_AirportInformation, System.Xml.XmlNode)
   bei AIGTech.TrafficController.Classes.Files.XMLFile_AirportInformation.readAirportNode(System.Xml.XmlNode)
   bei AIGTech.TrafficController.Classes.Files.XMLFile_AirportInformation.LoadFile(System.String)
   bei AIGTech.TrafficController.Classes.Manager.Moduls.AirportManager.loadData()
   bei AIGTech.TrafficController.Classes.Manager.Moduls.AirportManager..ctor(AIGTech.TrafficController.Classes.Manager.TrafficManager)
   bei AIGTech.TrafficController.Classes.Manager.TrafficManager..ctor(AIGTech.TrafficController.Controller.TCController)
   bei AIGTech.TrafficController.Controller.TCController.<ConnectToSim>b__43_4(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
   bei System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.DispatcherOperation.InvokeImpl()
   bei MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   bei MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   bei System.Windows.Threading.DispatcherOperation.Invoke()
   bei System.Windows.Threading.Dispatcher.ProcessQueue()
   bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   bei System.Windows.Application.RunDispatcher(System.Object)
   bei System.Windows.Application.RunInternal(System.Windows.Window)
   bei AIGTech.TrafficController.App.Main()


Hope there will be a solution..

Best,

Mace

will have a look. Wich files do you have in <OCI>\Airports\AIGTC?
Title: Re: [OPEN] .NET-related CTD
Post by: matthiasmjf@yahoo.de on November 07, 2021, 12:37:17 PM
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EG8A_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EG8B_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EG8C_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EG8D_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EG8E_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EG8F_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EG8G_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EG8H_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EG8I_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EGSC_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\EGSH_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\PHLI_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\PHNL_KPK_P3D.xml"
"D:\AIGAIM\AIGAIM - OCI\Airports\AIGTC\PHOG_KPK_P3D.xml"


Hello!

The files above.
I do recall having installed the updates for United Express and AA today and there was something with the last three Hawaiian airports in the OCI. I assume some files were scanned or installed. I do definitely recall those Hawaiian ICAO codes.. Could those be faulty? Before the update it did work, far as I recall..

Best

M

PS: I´ll try and remove said files and see what happens
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on November 07, 2021, 12:41:42 PM
seems so, will check the AIGTC code, I fixed there some stuff in the last days, might be not made it into the current one ;D
Title: Re: [OPEN] .NET-related CTD
Post by: matthiasmjf@yahoo.de on November 07, 2021, 12:47:30 PM
HI,

thanks for the effort!
Deleting the three Hawaiian files allowed the TC to work just fine so I suppose the problem lies with one of thoes three xmls.

Best regards,

Mace
Title: Re: [OPEN] .NET-related CTD
Post by: Kaiii3 on November 07, 2021, 01:01:08 PM
the files are fine, just TC has not the new code to read them :)
Title: Re: [OPEN] .NET-related CTD
Post by: matthiasmjf@yahoo.de on November 07, 2021, 01:13:43 PM
Okay, makes sense.