December 18, 201312 yr Hi folks - Hoping some of the local CTD gurus have some ideas as to what's causing this one. It happens relatively infrequently (maybe 1 out of every 3 flights). I've done some research (googling and searching here), but I can't figure out the source. Problem with a .NET install? Simconnect? Note that I tried uninstalling and re-installing UT2 on a hunch, but no change. Thanks in advance! System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.FlightSimulator.SimConnect.SimConnect.RequestDataOnSimObjectType(Enum RequestID, Enum DefineID, UInt32 dwRadiusMeters, SIMCONNECT_SIMOBJECT_TYPE type) at .?.(? timeRecvr, DateTime FSXStarted, DateTime FlightStarted) at .?.?() at ..?(Object sender, EventArgs e) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.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.5472 (Win7SP1GDR.050727-5400) ---------------------------------------- UT2Services Assembly Version: 2.1.0.0 Win32 Version: 2.1.0.0 ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400) ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400) ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400) ---------------------------------------- System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5476 (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.Data Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) ---------------------------------------- System.Transactions Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900) ---------------------------------------- System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400) ---------------------------------------- System.EnterpriseServices Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) ---------------------------------------- System.Management Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) ---------------------------------------- System.ServiceModel Assembly Version: 3.0.0.0 Win32 Version: 3.0.4506.5452 (Win7SP1GDR.030729-5400) ---------------------------------------- SMDiagnostics Assembly Version: 3.0.0.0 Win32 Version: 3.0.4506.5452 (Win7SP1GDR.030729-5400) ---------------------------------------- System.Web Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5474 (Win7SP1GDR.050727-5400) ---------------------------------------- System.Runtime.Serialization Assembly Version: 3.0.0.0 Win32 Version: 3.0.4506.5452 (Win7SP1GDR.030729-5400) ---------------------------------------- System.IdentityModel Assembly Version: 3.0.0.0 Win32 Version: 3.0.4506.5452 (Win7SP1GDR.030729-5400) ---------------------------------------- System.Core Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.5420 built by: Win7SP1 ---------------------------------------- System.Xml.Linq Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.5420 built by: Win7SP1
December 18, 201312 yr SimConnect appears to be installed correctly. Perhaps there is a problem with the dll.xml or exe.xml files. There appears to be an issue with the interaction between SimConnect and UT2. You can try disabling all the items in the dll.xml and exe.xml (except the top one) and see if that fixes the problem. If so, you'll need to reenable them one at a time to see which one might be causing the problem. Edit the line <Disabled>False</Disabled> to <Disabled>True</Disabled>. The other problem might be your Microsoft.net installation - Make sure required Microsoft.net Framework Packages are installed and up-to-date - The appropriate Microsoft.net Framework packages are normally installed when you first install FSX/Acceleration/P3D and commercial add-on programs if the appropriate package is not found. You will need versions 1.1 through the latest. You can see what versions are installed by going to your Windows Explorer and look for Windows/Microsoft.net/Framework/(then the versions installed). Once the packages are installed, Windows Update will periodically update the packages. You can verify whether your versions are properly installed and up-to-date by using the .Net Framework Setup Verification Tool User's Guide. Microsoft.net packages are used by developers to make sure the program runs in the way they intended, including memory management. The packages are, for the most part, not backward compatible. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
December 20, 201312 yr Author Jim - thank you very much for you reply. I did a little bit more testing, which suggested that the flaw lies in uiautomationcore.dll. Following the advice in the AVSIM hardware/software guide, I added to my FSX directory the earlier version of that file mentioned in the guide. So far, so good, so I will keep my fingers crossed.
Create an account or sign in to comment