active Unhandled exception has occurred Airport Elevation Correction

bill721 · January 13, 2017

Matt, any update?

Matthew Webb · January 15, 2017

On ‎14‎/‎01‎/‎2017 at 1:09 AM, bill721 said:

Matt, any update?

Hi,

Can you see any files in c:\fsx\ORBX\FTX_VECTOR\Temp ? If so close all programs delete this file and try again.

If the problem persists, can you zip the runways.txt file and PM it to me?

Also confirm your error is not when the program loads, but when the "Auto Elevation Corrections" button is pressed?

Thanks,

Matt.

bill721 · January 16, 2017

Matt, thanks for the reply. I deleted the file in the temp folder and ran program and it still failed. The failure happens about 1 to 2 minutes after pressing the Auto Elevation button. It runs for a while then errors.

How do I get the zip file to you? I can only attach .07MB and the file is bigger than that?

Thank you,

Bill

Matthew Webb · January 17, 2017

Hi Bill,

Thanks for sending the file - much appreciated. I'll run a few tests against it to try to pinpoint where the issue is. It will take a few days at least.

Thanks,

Matt.

bill721 · January 17, 2017

OK. Glad u got it.

Bill

Matthew Webb · January 19, 2017

Hi Bill,

What is the version shown in the title bar of FTX GLOBAL VECTOR Configuration Tool on your machine?

Thanks,

Matt.

bill721 · January 19, 2017

Matt, it is version 1.40

Bill

Matthew Webb · January 19, 2017

Thanks Bill. I am seeing the same error as described, but the code it catching and dealing with it, I am trying to find a scenario when it's not caught.

Thanks,
Matt.

Sent from my SM-N920I using Tapatalk

bill721 · January 19, 2017

Hey great. Matt, I really appreciate your help. Let me know what you find.

Bill

ron6468 · January 21, 2017

Hi - similar problem for me today. Using 1.40. Everything works except the Elevation tool. I tried adding EGCC (recently added the scenery) and it immediately gave me the same "Unhandled Exception Error" as mentioned above.

Ripcord · January 21, 2017

Guys I am still having the same troubles here with this Vector Config Tool.

It shows also that I have version 1.4 installed (config tool) -- Since I am installing using FTX Central3 I obviously have version 1.45 of the product itself.

I have followed instructions in this thread (several times now), which is to say I have removed/uninstalled Vector, deleted the FTX Vector File, and reinstalled the product. Same result. I'll run through it one more time (just to prove I am insane) and I will then go about downloading whatever file you require.

Regards,

Mark

Nick Cooper · January 21, 2017

To ron6468 and Mark.

Given that there are two completely different errors being reported here,

which one do each of you see?

" the same "Unhandled Exception Error" as mentioned above" is of little use as there

are two.

Ripcord · January 21, 2017

Yes sir, just reinstalled it once again. Running the airport elevation scan right now.

EDIT: Ok here we are:

Quote

Given that there are two completely different errors being reported here,

which one do each of you see?

It would appear that this time it is neither -- I have a third error, if I am not mistaken:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

at System.String.CtorCharArrayStartLength(Char[] value, Int32 startIndex, Int32 length)

at System.IO.StreamReader.ReadLine()

at System.IO.File.ReadAllLines(String path, Encoding encoding)

at System.IO.File.ReadAllLines(String path)

at FtxVector.Configurator.Ui.Forms.MainForm.Aec_AutoBtn_Click(Object sender, EventArgs e)

at System.Windows.Forms.Control.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

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

FtxVector.Configurator

Assembly Version: 1.35.0.0

Win32 Version: 1.35.0.0

CodeBase: file:///D:/Program%20Files/Lockheed%20Martin/Prepar3D%20v3/ORBX/FTX_VECTOR/FTX%20GLOBAL%20VECTOR%20Configuration%20Tool.exe

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

Microsoft.VisualBasic

Assembly Version: 8.0.0.0

Win32 Version: 8.0.50727.8745 (WinRel.050727-8700)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

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

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

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

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.8750 (QFE.050727-8700)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

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

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

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

Accessibility

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

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

System.Runtime.Remoting

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

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

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

Ripcord · January 21, 2017

On ‎12‎/‎7‎/‎2016 at 0:16 AM, Nick Cooper said:

You can try resetting all your Vector control panel options to on and then search

FTX_VECTOR for .inactive and delete all the results.

If that does not work, the only other option is to delete the FTX_VECTOR folder

and re-install the products.

Nick, what do you mean exactly by "the only other option is to delete the FTX_VECTOR folder and re-install the products".....? Other than Vector, what products should be reinstalled?

Nick Cooper · January 21, 2017

It's only a typing error, it should read "the product", FTX Vector.

The point I am trying to make is that too many customers are posting

"I have exactly the same problem" when they do not but which does fall under

the general heading of "an unhandled exception".

ron6468 has made just such a post and we have no idea what his problem is because

"an unhandled exception" is no more detailed than "it didn't work".

I am not at all sure that your error is a result of the original problem

posted in this topic and I don't want you to waste any more time going

round in circles.

Matthew is the only expert here and you should follow any advice he can give you.

Of course, as ever, there is total silence from the people who should be supporting their product, Pilot's.

Ripcord · January 21, 2017

Yes, I suppose I am guilty of hi-jacking this thread, thinking I had exactly the same issue going on. I should apologize for that.

BTW I just ran the config tool for FSX Steam and it worked as it should. The major difference there is I have almost no third-party add-on scenery installed in that sim, other than ORBX. I really only use it for testing.

I think I will do this -- I will 'swap out' my scenery.cfg file (which has hundreds and hundreds of entries) for one that is relatively free of third party addons, other than ORBX and run the thing again.

Ripcord · January 21, 2017

OK that worked.

1> I took my scenery.cfg file and saved it as a backup. Then I removed a good 60%-70% of my entries, leaving just a handful of entries above my ORBX entries. Named that scenery.cfg and just for good measure I reordered the entries (using a scenery config editor tool) -- not sure that step is relevant.

2> In the FTX_VECTOR/Scenery folder I had already removed all files that end in .inactive and move those to another folder, just to keep them handy.

3> Ran the Vector airport config tool again. Worked like a champ.

So what now does this tell me? Should infer that I had too many airports installed? I'll be testing that again here shortly, as I will begin repeat this process while gradually adding back in groups of entries for third party scenery.

bill721 · January 22, 2017

Folks, Matt has found the Issue I'm having and is working on a solution so I don't want that work to be messed up. Ripcord would you mind opening up a separate post with the problem you are having so we have a single stream for each issue. thank you so much.

Bill

Hani849 · January 22, 2017

On 1/10/2017 at 0:06 AM, skitzo420 said:

heya guys i had same problem and tried something wich was manualy disable ymml in vector config then clicked auto config and it worked

Hey everyone,

This way solve my issue too (Unhandled exception has occurred Airport Elevation Correction). just to let you know.

Ripcord · January 22, 2017

2 hours ago, bill721 said:

Folks, Matt has found the Issue I'm having and is working on a solution so I don't want that work to be messed up. Ripcord would you mind opening up a separate post with the problem you are having so we have a single stream for each issue. thank you so much.

Bill

Bill, I think we both hijacked another guys thread here. However I think the thread may prove useful to others in the sense that we have three guys with 'unhandled exception errors' and all three are different.

That said I think I am getting mine sorted without Matt's help so I'll go ahead and bow out at this point.

bill721 · January 24, 2017

Matt, any progress on bypassing the error successfully or doing a clean install of the tool?

Bill

sfdeham · January 24, 2017

Hi Bill,

hi Matt,

I am running into same issue.

FTX Global Vector is up-to-date as per FTX Central. As soon as I go to FTX GLOBAL VECTOR Configuration Tool - Version 1.40 > Airport Elevation Corrections > Run Auto-Configuration and click "OK" I am getting the following unhandled exception (in German, but its the same as previously reported):

Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.IO.IOException: Eine Datei kann nicht erstellt werden, wenn sie bereits vorhanden ist.

   bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   bei System.IO.__Error.WinIOError()
   bei System.IO.File.Move(String sourceFileName, String destFileName)
   bei FtxVector.Configurator.Ui.Forms.MainForm.Aec_AutoBtn_Click(Object sender, EventArgs e)
   bei System.Windows.Forms.Control.OnClick(EventArgs e)
   bei System.Windows.Forms.Button.OnClick(EventArgs e)
   bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
   bei System.Windows.Forms.Button.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladene Assemblys **************
mscorlib
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll.
----------------------------------------
FtxVector.Configurator
    Assembly-Version: 1.35.0.0.
    Win32-Version: 1.35.0.0.
    CodeBase: file:///D:/FSX/ORBX/FTX_VECTOR/FTX%20GLOBAL%20VECTOR%20Configuration%20Tool.exe.
----------------------------------------
Microsoft.VisualBasic
    Assembly-Version: 8.0.0.0.
    Win32-Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
----------------------------------------
System
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.8686 (QFE.050727-8600).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Windows.Forms
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System.Drawing
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5495 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
System.Runtime.Remoting
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5488 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.
----------------------------------------
mscorlib.resources
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll.
----------------------------------------
System.Windows.Forms.resources
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

Changing the manual configuration and then clicking "Apply" appears to work OK.

I appreciate a fast solution as manual enabling/disabling of entries is not really an option with a high amount of changes to the scenery.cfg.

Best regards,

Stefan

Nick Cooper · January 24, 2017

Your error report is the same as that of the author of this topic.

The answer is therefore the same as the answer in post number 3.

From your point of view there is nothing else of relevance in this topic.

sfdeham · January 25, 2017

23 hours ago, Nick Cooper said:

Your error report is the same as that of the author of this topic.

The answer is therefore the same as the answer in post number 3.

From your point of view there is nothing else of relevance in this topic.

Hi Nick,

apparently I got lost while reading through the discussion. Will try instructions from #3 and advise outcome.

Regards,

Stefan

Matthew Webb · January 25, 2017

Hi Guys,

Thanks for your patience.

Attached is a version to test and see if it resolves the issue.

This file needs to be manually copied to your <flight sim path>\ORBX\FTX_VECTOR folder.

Please rename the original file first to keep it as a backup.

Please let us know how you go!

Cheers,

Matt.

(Edit: File removed. Please PM me for a copy if you need it. Thanks.)

bill721 · January 25, 2017

That worked..... It ran completely through and completed properly.... Way to go Matt....

Thank you so much...

Bill Ditz

Matthew Webb · January 25, 2017

Great! Thanks for letting us know. I'll contact the developer and let him know the fix worked and we'll work on distribution of the updated version.

Cheers,

Matt.

bill721 · January 25, 2017

it looks like it didn't catch KMEM which is an add-on scenery I have installed. Is there something different I need to do with add-on sceneries I have?

Matthew Webb · January 25, 2017

This topic may help:

Cheers,

Matt.

bill721 · January 25, 2017

No I have KMEM first. Just must be it doesn't see the elevation of KMEM so it doesn't remove it. It caught a whole bunch of other ones though. I like that a lot. I can sure live with KMEM being missed. Just wanted to let you know.

Bill

Matthew Webb · January 25, 2017

Thanks Bill. Probably best you create a new topic for that one so it catches the attention of the appropriate staff.

Cheers,

Matt.

tBredie · January 29, 2017

i have this problem in GERMAN:

'Unbehandelte Ausnahme in der Anwendung.'

Quote

Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.InvalidOperationException: Die Anforderung kann nicht verarbeitet werden, da der Prozess beendet wurde.
   bei System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
   bei System.Diagnostics.Process.Kill()
   bei FtxVector.Configurator.Ui.Forms.MainForm.Aec_AutoBtn_Click(Object sender, EventArgs e)
   bei System.Windows.Forms.Control.OnClick(EventArgs e)
   bei System.Windows.Forms.Button.OnClick(EventArgs e)
   bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
   bei System.Windows.Forms.Button.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Geladene Assemblys **************
mscorlib
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll.
----------------------------------------
FtxVector.Configurator
    Assembly-Version: 1.35.0.0.
    Win32-Version: 1.35.0.0.
    CodeBase: file:///D:/Spiele%20(x86)/MSGames/FSX/ORBX/FTX_VECTOR/FTX%20GLOBAL%20VECTOR%20Configuration%20Tool.exe.
----------------------------------------
Microsoft.VisualBasic
    Assembly-Version: 8.0.0.0.
    Win32-Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
----------------------------------------
System
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.8686 (QFE.050727-8600).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Windows.Forms
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System.Drawing
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5495 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
System.Runtime.Remoting
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5488 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.
----------------------------------------
mscorlib.resources
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400).
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll.
----------------------------------------
System.resources
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.resources/2.0.0.0_de_b77a5c561934e089/System.resources.dll.
----------------------------------------
System.Windows.Forms.resources
    Assembly-Version: 2.0.0.0.
    Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400).
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

AND i saw this in the Runways.txt created from the ''MakeRwy.exe'' of ACE

Quote

Make Runways File: Version 4.693 by Pete Dowson
Reading FSX SCENERY.CFG ...
CFG file being used is: "C:\ProgramData\Microsoft\FSX\SCENERY.CFG"

.

.153.005.496 bytes later

.

***ERROR C0000005 at 77272A62:
*** Access violation trying to read address 00000004
*** EAX 13AA81A0 EBX 13A50050 ECX 00000000 EDX 00000000 EDI 0ECC0000 ESI 13AA8198

the latest MakeRwy.exe is v4.6991 - manuelly started - everything works fine, no error in Runways.txt

Quote

Make Runways File: Version 4.6991 by Pete Dowson
Reading FSX SCENERY.CFG ...
CFG file being used is: "C:\ProgramData\Microsoft\FSX\SCENERY.CFG"

.

.197.449.038 bytes later

.

=============================================================================

When i manuelly start the MakeRwy.exe of ACE (this time 45edfbce-a551-4f82-9b03-7b4a2f40f164.exe)

- the Runwys.txt shows

Quote

Make Runways File: Version 4.693 by Pete Dowson
Reading FSX SCENERY.CFG ...
CFG file being used is: "C:\ProgramData\Microsoft\FSX\SCENERY.CFG"

.

.197.449.038 bytes later

.

=============================================================================

.--- there was no error ????? every file created successfully

greeting from Germany, Kiel

ron6468 · January 30, 2017

Hate to pile on here but here are the details of my exception error.

************** Exception Text **************
System.IO.IOException: Cannot create a file when that file already exists.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.__Error.WinIOError()
   at System.IO.File.Move(String sourceFileName, String destFileName)
   at FtxVector.Configurator.Ui.Forms.MainForm.Aec_AutoBtn_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5477 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FtxVector.Configurator
    Assembly Version: 1.35.0.0
    Win32 Version: 1.35.0.0
    CodeBase: file:///G:/Lockheed%20Martin/Prepar3D%20v3/ORBX/FTX_VECTOR/FTX%20GLOBAL%20VECTOR%20Configuration%20Tool.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------

Nick Cooper · January 30, 2017

On 24/01/2017 at 9:11 PM, Nick Cooper said:

Your error report is the same as that of the author of this topic.

The answer is therefore the same as the answer in post number 3.

From your point of view there is nothing else of relevance in this topic.

ron6468 · January 30, 2017

Tried the new replacement exe file from Matthew but for my issue did not work either.

Using FSX Central 3, I uninstalled Vector and reinstalled it. I decided then to use the new Vector Configuration file from Matt instead of the default FTX version.

Glad to say - everything worked perfect including the Elevation/Flattening Tool.

Thanks to everyone for the ideas.

bill721 · January 30, 2017

Glad you got it working...

Bill

tBredie · February 1, 2017

On 30.1.2017 at 6:22 PM, Nick Cooper said:

just deleted Vector-Folder and then reinstalled Vecor.

BUT i run AEC -

- and same errors as posted above

- SAME runways.txt filesize

- SAME

Quote

***ERROR C0000005 at 7726E43E:
*** Access violation trying to read address 741E4A8E
*** EAX 4221E0F0 EBX 13006150 ECX 00300000 EDX 13006150 EDI 13006148 ESI 741E4A8A

at the end of runways.txt

bill721 · February 1, 2017

You may want to MSG Matt and ask him to send you the link to the FTX GLOBAL VECTOR Configuration Tool file and see if it corrects the issue.

This file needs to be manually copied to your <flight sim path>\ORBX\FTX_VECTOR folder.

Please rename the original file first to keep it as a backup.

Please let us know how you go!

Cheers,

Matt.

(Edit: File removed. Please PM me for a copy if you need it. Thanks.)

Ripcord · February 2, 2017

FTX Central has been updated just in the last 24 hours. Maybe give that a try? Probably the fixes that Matt provided have been included in that.

tBredie · February 3, 2017

no change for me

Sign In

active Unhandled exception has occurred Airport Elevation Correction

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment