Jump to content

FTX Central Unhandled exception


BizzyB

Recommended Posts

FTX Central (and Orbx/FTX ) were working fine until I downloaded and installed NZNI; that finished with FTX Central, so apparently all OK. Afterwards, the scenery for NZNI was OK until I went back to FSX Default (to fly some missions there), but when I tried to go back to Oceania I got the dreaded "unhandled exception" and nothing has worked since then. I tried re-instaing NZNI (concluding with FTX Central), but still "unhandled exception", although with a different error message.

(Before NZNI, I had AUS, PNW, NRM, CRM, PJF and ENG installed and working ).

Help please.

P.S. I can't see where to put my order numbers as per instructions; I'll do that next post.

TIA

David

Link to comment
Share on other sites

FTX Central (and Orbx/FTX ) were working fine until I downloaded and installed NZNI; that finished with FTX Central, so apparently all OK. Afterwards, the scenery for NZNI was OK until I went back to FSX Default (to fly some missions there), but when I tried to go back to Oceania I got the dreaded "unhandled exception" and nothing has worked since then. I tried re-instaing NZNI (concluding with FTX Central), but still "unhandled exception", although with a different error message.

(Before NZNI, I had AUS, PNW, NRM, CRM, PJF and ENG installed and working ).

Help please.

P.S. I can't see where to put my order numbers as per instructions; I'll do that next post.

TIA

David

You can find here how to put in your order numbers; http://www.orbxsyste...ig-for-support/

Peter

Link to comment
Share on other sites

Sorry about that. I hope i've fixed up my signature (But don't know how to use it, so I've just copied the relevant info at the bottom of this .)

FTX Central (and Orbx/FTX ) were working fine until I downloaded and installed NZNI; that finished with FTX Central, so apparently all OK. Afterwards, the scenery for NZNI was OK until I went back to FSX Default (to fly some missions there), but when I tried to go back to Oceania I got the dreaded "unhandled exception" and nothing has worked since then. I tried re-instaing NZNI (concluding with FTX Central), but still "unhandled exception", although with a different error message.

(Before NZNI, I had AUS, PNW, NRM, CRM, PJF and ENG installed and working ).

I've also applied the latest ORBX Libs

Help please.

TIA

David

FTX Australia SP3 FSS ??? ; YCDR100SP3 FSS0112679; YBBN FSS0112679; ORBX-FTX NZSI FSS0140975; Orbx-FTX NA Blue Pacific Northwest FSS0144767; Lancair IV-P FSS0144796; Orbx-FTX Gold Central Rocky Mountains FSS0146726 ; Orbx-FTX NA Blue USA/Canada Northern Rocky Mountains FSS0146754 ; Orbx/FTXNZNI100 FSS0176295 ; Cushman Meadows FSS0163612 ; USA/Canada Pacific Fjords FSS0163612 : KORS Orcas Island FSS0163612 ; OrbxFTXNAKJAC100 FSS01658 ; Orbx-FTX: EU England FSS089795

Link to comment
Share on other sites

Below is the current error message.

However, several of the previous ones were to do with "The requested operation cannot be performed on a file with a user-mapped section open "; when I got this, I shut down the computer and restarted, but that didn't help.

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: The requested operation cannot be performed on a file with a user-mapped section open.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)

at System.IO.File.Copy(String sourceFileName, String destFileName, Boolean overwrite)

at FTXCentral.FTX_Environment.CopyBuildRestoreBat()

at FTXCentral.FTX_Environment.ApplyRegionChanges()

at FTXCentral.FTXC.Apply()

at FTXCentral.FTXC.lblApplyButton_Click(Object sender, EventArgs e)

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

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

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

at System.Windows.Forms.Label.WndProc(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.5466 (Win7SP1GDR.050727-5400)

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

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

FTXCentral

Assembly Version: 1.0.2.9

Win32 Version: 1.0.2.9

CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Games/Microsoft%20Flight%20Simulator%20X/ORBX/Scripts/FTXCentral/FTXCentral.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.5467 (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.5420 (Win7SP1.050727-5400)

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

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

System.Configuration

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

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

System.Xml

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

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

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

xof6lyac

Assembly Version: 1.0.2.9

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

Assembly Version: 3.5.0.0

Win32 Version: 3.5.30729.5420 built by: Win7SP1

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

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

a0i1e1-o

Assembly Version: 1.0.2.9

Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.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:

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

Link to comment
Share on other sites

Hello David,

sorry, looks like we lost track of your response. Unfortunately, I'm not familiar with that particular error message though it does seem to indicate that something is preventing access to one or more FTX Central files; see Tim's suggestions here: http://www.orbxsystems.com/forum/topic/51709-problem-with-fsx-central-ftx-eng/#entry455646

Cheers, Holger

Link to comment
Share on other sites

By chance, my grandson visited this weekend. I got him to have a look at my computer, mainly to try to improve the response time of FSX when starting,(which was about 10 min ).

He looked at all the programs which were running in the background and which loaded at startup ( but were not on Startup menu). He found about 75 running, of which he disabled about 50.

The effect on FSX startup time was dramatic, down to about 2 min, which is tolerable. Purely as a byproduct, the "Unhandled exception" problem seems to have gone away; I have since installed the Eng update/patch (which ended with a return to FTX Central ) and had a couple of flights in England, which appeared to be as expected, then returned to Oceana and Apply, followed by a couple of flights, which also appeared normal. Late today, I restarted the computer, checked FTX central again and flew in NZNI - all seemed normal.

So, I have no real idea of what the probllem was, but it seems to have gone way.

(I had previously tried most of the approaches suggested in this Forum, including Smart_PC_Fixer, with no success )

Cheers

David

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...