March 3, 201511 yr I was running EFB very well with FSX, until I had a system problem that required me to uninstall FSX completely. I re-installed with FSX SE, and began to re-install all of my prior FSX apps. Haven't had any problems, until I got to Aivlasoft's EFB. I cannot get the data provider to run...it installed and did it's initial construction, and at the end it crashed. The reason I'm posting up here is that the Aivlasoft forum seems to be putting the onus of solving the problem on other users - a typical reply from the Aivlasoft crew says (in effect), "Why don't you look up the error and see what's wrong?" It seems that they have no idea how to deal with this. Anyway, here is my post from their forum and the error I keep getting: I completely removed FSX and all of its components and re-installed FSX SE. I was running EFB on two computers (both running Win7/64), and all was running fine. Now, however, the data provider will not install - it looks good and runs through all of its paces, but at the end, ir crashes, with the enclosed message. Since I am running Win7, the docs say that I am already running .Net framework 3.5, so I don't think that's the problem, but here's the rest of the data from the box: ************** Exception Text **************System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)at bh.c(Object A_0, EventArgs A_1)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 **************mscorlibAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5477 (Win7SP1GDR.050727-5400)----------------------------------------AivlaSoft.Efb.DataProviderAssembly Version: 1.5.1.15704Win32 Version: 1.5.1.0----------------------------------------log4netAssembly Version: 1.2.10.0Win32 Version: 1.2.10.0----------------------------------------System.Windows.FormsAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)----------------------------------------SystemAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)----------------------------------------System.DrawingAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)----------------------------------------DevExpress.Utils.v9.1Assembly Version: 9.1.4.0Win32 Version: 9.1.4.0----------------------------------------Rhino.CommonsAssembly Version: 2.0.0.0Win32 Version: 2.0.0.1414----------------------------------------Castle.WindsorAssembly Version: 1.0.3.0Win32 Version: 1.0.3.5114----------------------------------------Castle.CoreAssembly Version: 1.0.3.0Win32 Version: 1.0.3.5114----------------------------------------Castle.MicroKernelAssembly Version: 1.0.3.0Win32 Version: 1.0.3.5114----------------------------------------System.ConfigurationAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)----------------------------------------System.XmlAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)----------------------------------------Rhino.Commons.ClrAssembly Version: 2.0.0.0Win32 Version: 2.0.0.1414----------------------------------------System.WebAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)----------------------------------------Castle.DynamicProxy2Assembly Version: 2.0.3.0Win32 Version: 2.0.3.5114----------------------------------------AivlaSoft.Efb.CommonAssembly Version: 1.5.1.15699Win32 Version: 1.5.1.0----------------------------------------System.CoreAssembly Version: 3.5.0.0Win32 Version: 3.5.30729.5420 built by: Win7SP1----------------------------------------DevExpress.Data.v9.1Assembly Version: 9.1.4.0Win32 Version: 9.1.4.0----------------------------------------DevExpress.XtraEditors.v9.1Assembly Version: 9.1.4.0Win32 Version: 9.1.4.0----------------------------------------System.DataAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)----------------------------------------DevExpress.XtraGrid.v9.1Assembly Version: 9.1.4.0Win32 Version: 9.1.4.0----------------------------------------DevExpress.XtraBars.v9.1Assembly Version: 9.1.4.0Win32 Version: 9.1.4.0----------------------------------------Desaware.MachineLicense35Assembly Version: 1.6.0.0Win32 Version: 1.6.3.0----------------------------------------Microsoft.VisualBasicAssembly Version: 8.0.0.0Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)----------------------------------------Desaware.Dls.Interfaces20Assembly Version: 1.0.0.0Win32 Version: 1.0.0.0----------------------------------------System.SecurityAssembly Version: 2.0.0.0Win32 Version: 2.0.50727.5475 (Win7SP1GDR.050727-5400)----------------------------------------************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.For example:<configuration><system.windows.forms jitDebugging="true" /></configuration>When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box.************************************************************************************I'd love to get this working. Any help would be greatly appreciated. -= Gary Barth =-
March 3, 201511 yr Commercial Member I completely removed FSX and all of its components and re-installed FSX SE So have you checked to see that -SE is installed as FSX would have? For example, you can check the correct folders exist, e.g. "C:\Users\<you>\Documents\Flight Simulator X - Steam Edition Files" will not do, should be "C:\Users\<you>\Documents\Flight Simulator X Files". In the registry: "HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\Co-Existence=1" also will not do, should be =0. Folders need to be the same as boxed FSX, except for Program Files where the -SE version installs its program files: C:\Program Files (x86)\Steam\steamapps\common\FSX C:\ProgramData\Microsoft\FSX C:\Users\<you>\AppData\Local\Microsoft\FSX C:\Users\<you>\AppData\Roaming\Microsoft\FSX cfg: C:\Users\<you>\AppData\Roaming\Microsoft\FSX\fsx.CFG documents: C:\Users\<you>\Documents\Flight Simulator X Files pics: C:\Users\<you>\Pictures\Flight Simulator X Files Steve Waite: Engineer at codelegend.com
March 3, 201511 yr Commercial Member Try installing the legacy SimConnect modules, found in the Steam FSX SDK folder under Core Utilities. Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
March 3, 201511 yr To install Data Provider EFB looks for installed fsx. Data Provider needs to be installed on same pc where fsx is installed. EFB does not see fsx steam. I have the same problem. Waiting for update EFB
March 3, 201511 yr Commercial Member To install Data Provider EFB looks for installed fsx. Data Provider needs to be installed on same pc where fsx is installed. EFB does not see fsx steam. I have the same problem. Waiting for update EFB Seems to work fine here -- you do need to have the FSX SimConnect installed. It doesn't appear to need to "see" FSX-SE, it links to it via SimConnect. Maybe the problem is only its access to the NavData? That's normally stored in your FSX\Aivlasoft folder. It should be able to find it in the Steam FSX folder too, for an FSX-SE only install, otherwise it would find it still in the FSX folders. Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
March 3, 201511 yr Commercial Member Although FSX simconnect is left on the system and should remain working when FSX is uninstalled, there may be some problem with it. As Pete suggests, could try running the legacy simconnect installers just in case: ..\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-RTM\SimConnect.msi ..\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1\SimConnect.msi ..\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK\SimConnect.msi Those having installed FSX-SE on a fresh Windows PC (not seen FSX) should at least run the SP1 and XPACK installers. Steve Waite: Engineer at codelegend.com
March 3, 201511 yr Author Thank you very much, Pete & Steve. Installing those SimConnects did the trick. While I hate to bad-mouth developers, it seems that the guys over at AivlaSoft had no idea what was wrong. In almost a week, there was no response or suggestions on what to do. But when I turned to AvSim and you guys, it was an over-night fix! Now I have to go back over there and tell them how to fix their own problem. Again, thanks a whole bunch! -= Gary Barth =-
March 10, 201511 yr Hello everybody, I'm running on the same PC FSX & FSX:SE. It works well and I had no problem to launch my networked EFB. Everything seems OK with Aerosoft Airbus X and PMDG 777 SP1d. EFB on ground is OK too. But when I take off with this aircrafts, a few minutes pass and suddenly FSX:SE crashes! Without EFB I can complete a normal flight. Did you get the same trouble? Any ideas? Skip.
Create an account or sign in to comment