answered The new Vector 1.51 has error exception windows...

Orbx Flyer · March 24, 2017

I just installed it. I then ran the Airport Configurator, on both FSX boxed and P3D.

The minute I ran the configurator, a white error-exception window opened up with a slew of errors. This is a bug in the new update. BOTH P3D and FSX had the error window come up on Airport Elevation running attempts.

Did Central 3 bugger up the install on both P3D and FSX? Both simulators via Central 3, reported a successful Vector 1.51 installation, at the end of the update routine.

Nick Cooper · March 24, 2017

Hello,

what was the slew of errors please.

This has been tested and the results were not what you are reporting.

I have had this update for a good while now and no error messages.

Museumkeeper · March 24, 2017

Hi Nick

I agree with PNW User. Here exception text.

Kind regards

Ian

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** 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.(Object , EventArgs )
   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.50.0.0
    Win32 Version: 1.50.0.0
    CodeBase: file:///D:/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
    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.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.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
----------------------------------------
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
----------------------------------------
?
    Assembly Version: 0.0.0.0
    Win32 Version: 1.50.0.0
    CodeBase: file:///D:/Lockheed%20Martin/Prepar3D%20v3/ORBX/FTX_VECTOR/FTX%20GLOBAL%20VECTOR%20Configuration%20Tool.exe
----------------------------------------

************** 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:

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.

MikeFlight · March 24, 2017

The same by me:

Jedi928 · March 24, 2017

I have the same error...

Nick Cooper · March 24, 2017

Oh dear

Would you try this copy of the control panel

FTX GLOBAL VECTOR Configuration Tool.exe

Orbx Flyer · March 24, 2017

4 minutes ago, Ian S said:

Hi Nick

I agree with PNW User. Here exception text.

Kind regards

Ian

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** 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.(Object , EventArgs )
   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.50.0.0
    Win32 Version: 1.50.0.0
    CodeBase: file:///D:/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
    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.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.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
----------------------------------------
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
----------------------------------------
?
    Assembly Version: 0.0.0.0
    Win32 Version: 1.50.0.0
    CodeBase: file:///D:/Lockheed%20Martin/Prepar3D%20v3/ORBX/FTX_VECTOR/FTX%20GLOBAL%20VECTOR%20Configuration%20Tool.exe
----------------------------------------

************** 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:

<configuration>
    <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.

Those are the ones....both attempts to run the Auto-Config with either P3D or FSX, continually brings up this window.

Orbx Flyer · March 24, 2017

3 minutes ago, Nick Cooper said:

Oh dear

Would you try this copy of the control panel

FTX GLOBAL VECTOR Configuration Tool.exe

Same...the minute I ran this Nick, the white ERROR EXCEPTION window opened up....

Must we uninstall Vector 1.51 with Central 3...and then reboot the system and try to install via Central 3? It certainly did not do a clean update.

Mickel · March 24, 2017

Oddly, FSX worked fine but P3D didn't for me.

Museumkeeper · March 24, 2017

Hi Nick

Same here

Kind regards

Ian

Jedi928 · March 24, 2017

same error with the new configuration FTX Global Vector configuration tool.exe Nick.

MikeFlight · March 24, 2017

9 minutes ago, Nick Cooper said:

Oh dear

Would you try this copy of the control panel

FTX GLOBAL VECTOR Configuration Tool.exe

Nick, sorry, but this new Configuration Tool doesn't work for me. The same error.

Orbx Flyer · March 24, 2017

I am right now, as I type this, having UNINSTALLED Vector 1.51, and then am REINSTALLING via my back-up download of Vector 1.51 into P3D. I'll report back by EDIT to this post if I can run the Auto-Config AFTER having totally removed and installed Vector 1.51 That might be what one needs to do....as the update of the already installed product certainly does not work.

Will report as soon as the clean installation is attempted.

PNW User

The whole new install is massive...only about half way downloading...and already over 8GB's!

B777LR · March 24, 2017

Same error after updating to 1.51 when trying to run the AEC tool within the control panel.

volki127 · March 24, 2017

same error 1.51

Orbx Flyer · March 24, 2017

OK...here's the deal....you CAN NOT update to v1.51 from an already installed Vector product. You will get a broken AEC function.

You need to uninstall your current Vector v.x, and install a full, clean Vector v1.51 (12.57 GB's!)

From Nick Cooper : Before you do this, please refer to the last post in this topic.

I just finished my clean install, and the AEC Tool is doing its thing.

Unless you want to download almost 13 GB's...DON'T try to update your current Vector. This will leave you with a broken AEC Tool function.

Post Edit: In P3D, my Vector 1.51 AEC Tool just finished its function, and I APPLIED successfully. No errors, no windows...it worked as you'd expect it to. So..bottom line...if you want Vector 1.51, bite the bullet...uninstall, and then install a full fresh v1.51, and you will get a fully functioning latest Vector product. Now..do do the same for my FSX Boxed. What a PITA, but it is...what it is....

tom2rific · March 24, 2017

6 minutes ago, PNW User said:

Unless you want to download almost 13 GB's...DON'T try to update your current Vector. This will leave you with a broken AEC Tool function.

thannk you PNW .. this has all been a little messy for me...your post has helped ..

keino333 · March 24, 2017

Same issue here I'm downloading the full 1.51 installer now. I'll have to go back and uninstall 1.50 as I already broke the tool. It appears that the update did not register 1.51.

Billo · March 24, 2017

Thanks for the update guys!! I was just in the process of downloading the update which was nearly finished. I don't know what made me look in the forum at that particular time but I'm glad I did just in time to close FTXC before it did it's dirty deed!!

uncle_adolph · March 24, 2017

The moral is.....always check the forum before updating.

I was just about to "press the button"....now I'll wait.

gregmorin · March 24, 2017

I have the same issue. I was however able to add a older profile I had saved. This profile was not up to date but at least it gets me going again.

Greg

gaab · March 24, 2017

3 hours ago, Ian S said:

Hi Nick

I agree with PNW User. Here exception text.

************** 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.(Object , EventArgs )

Hello,

It would be useful to get from Pilot the name of the offending file(s), saving uninstall and full reinstall of 13 Gb (and saving bandwith ...)

Just my 2 cents

Gérard

shermank · March 24, 2017

Glad I stumbled across this thread. How do I uninstall Vector? thanks...It does not show up in the program list

Sherm

WebMaximus · March 24, 2017

Same issue here, glad I always keep good backups of my system

onlineflug · March 24, 2017

sorry, but same here. this update broke my Vector!

DrumsArt · March 24, 2017

Hoppefully I have not updated yet, so by now I'll wait to have a fix for that. No way for me to deinstall and download the 13G again !

Thank you and Regards,

Richard Portier

Lucien Bramard · March 24, 2017

Same pb here. And no way I redl the entire Vector with my slow co. Please fix it.

ve2dgz · March 24, 2017

Come on guys, can we have an update on this issue?

At the very least, someone should identify the problem in the new product download so people are aware before they break their software.

hwh86 · March 24, 2017

I am downloading it again, for the third time since last night, at the moment 5 am local time. Hope it works this time. Why does life keep repeating itself? It should all be so simple, we are updating programs all the time, why only Vector?

Sturmgewehr57 · March 24, 2017

KUDOS to "PNW User"... I also had broken FS Global Vector after v1.51 update via FTX Central v3.1.0.2 with same problem(s) & followed your instructions for uninstall & clean install of v1.51 via FTX Central w/ manually downloaded .zip file & PROBLEM SOLVED.... Vector's Airport Elevation Run Auto Configuration operates correctly w/o error..... Hope this helps fellow simmers.... Thanks again & Happy Flying....

FSS0529945 2016-10-26 FTX: NA PAVD Valdez Pioneer Field & all Orbx products offered to date

Nick Cooper · March 24, 2017

Hello,

I will ask what has happened.

Triplane · March 24, 2017

I have a new install of P3D. I just installed 1.51 using a manual download and there are no problems.........Doug

The Merowinger · March 24, 2017

Yes, De- and Newinstallation solved it. But in addition I had to use the configurator-exe given from Nick to get rid of the error using "run auto configuraton" too. The versionnumber of the configurator is called 1.50 instead of 1.51. Is that correct?

Kai

Nick Cooper · March 24, 2017

The configurator version is 1.50, yes.

hwh86 · March 24, 2017

46 minutes ago, Nick Cooper said:

Hello,

I will ask what has happened.

As described in the first post by PNWuser. As I remember this is a replica of the v1.50 update.

shermank · March 24, 2017

Uninstalled VECTOR as instructed elsewhere on the forum....began install of 1.50 and got the same popup as so many others.

Sherm

Nick Cooper · March 24, 2017

There hasn't been a 1.50 update has there?

Lots of requests to modify the text file to 1.45 though.

To shermank, the duplicate files error message, though you had uninstalled?

specialist · March 24, 2017

Well, just like everyone else, had the same issue. Took the advised of the forum to uninstall Vector completely, and reinstall. Did so successfully, and I'm running the configuration tool now, but noticed the configuration tool says version 1.50, is that right, or is it suppose to say 1.51?

Nick Cooper · March 24, 2017

As above

fueliehead · March 24, 2017

Having the same issue, fwiw.

Sign In

answered The new Vector 1.51 has error exception windows...

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