Unhandled exception

[bailout3]

This is not an ORBX complaint but instead a general question. Since I know nothing about PC errors I thought I would throw this out to see if any one has an answer that I can understand. As I said previously I have been getting this error long before Global vector and I believe even before I downloaded the first FTX region. At any time during a flight and sometimes when the a/c is sitting on the apron I get this error  "unhandled  exception HRESULT:0xC000014B. has occured in app " then it says ignore ( but it will crash if I do) or quit & restart. I am using FSX on win7 with a medium PC 8 gig ram quad etc.

Any ideas?

[PeterSuranyi86]

Next time check which file is causing the error (it is also in the error report, in the list at the bottom). that can help. Might be an uiautomationcore.dll error, but first we need to which file is the culprit. If you have the filename, just google around quickly, its probably a generic error that tons of people are having. Installing FSUIPC can also help (if you dont have it already). Without the filename, however, i guess it is hard to answer this question.

[bailout3]

ok thanks...I will look for it.

[bailout3]

Here is the information that I could find...I have no idea what it means.

 

System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B

   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

   at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal)

   at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage()

   at rexwxengine2.controls.ucLoadAircraftLocation.DefWndProc(Message& m)

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

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

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

   at System.Windows.Forms.UserControl.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)

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

rexwxengine2

    Assembly Version: 2.5.2010.38549

    Win32 Version: 2.5.2010.1027

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

System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)

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

System

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

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

System.Drawing

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

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

Microsoft.FlightSimulator.SimConnect

    Assembly Version: 10.0.61259.0

    Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

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

msvcm80

    Assembly Version: 8.0.50727.6195

    Win32 Version: 8.00.50727.6195

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

System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)

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

System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)

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

System.Data

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

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

 

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

[PeterSuranyi86]

Wow... I though it will simply give you a .dll name (something like this, in this case it's ntdll.dll)

http://i1115.photobucket.com/albums/k542/sgw86/AirbusX-BritishAirwaysError.png

With that kind of error I might have some ideas, but with your kind, I have no idea, sorry...

[jrrbolkin]

I used to get that error using REX I think it is REX related.if I remember correctly there is a few posts in the REX forum that should give you an answer.

If I recall it has something to do with permissions or settings in the REX GUI head over there and have a look, if I have time I will look myself later and give you a shout back if I find anything.

Good luck.

Gary

Quick look found this may be worth a go http://answers.microsoft.com/en-us/windows/forum/windows_other-gaming/whilt-playing-flight-sim-fsx-received-error-net/3f4d8949-09d3-4135-ab66-e09316a34b91

 

And this http://forum.avsim.net/topic/398403-microsoft-net-framework-exception-from-hresult-0xc000014b/

[bailout3]

Thanks much...I will have a look there as well but not sure I will understand it.

[bailout3]

I tried the suggestion in answers micro and found the rex folder with simconnect but when I did the right click "repair" wasn't one of the options.

 

I'm considering even removing REX and maybe getting a different wx machine. I had a difficult time installing REX when I purchased it and I would say that I get this error about 40% of the time which is rather annoying. Before I do I will try the avsim forum.