April 29, 201610 yr Any suggestions, I was looking around to see if anyone had this error but I could not find similar issues in my search. I installed P3d v3.2 and at startup when loading a scenaro, I am now getting a fatal error Faulting application path: D:\Prepar3Dv3\Prepar3D.exeFaulting module path: D:\Prepar3Dv3\bglmanx.dll I know it has to do with the fsdt/couatl applications but I dont own any of the sceneries or GSX. I did own have the QW757 but I deleted it from 3.1. Anyone else run into this issue? Also are there other developers who use this..I forget.(Flightbeam,etc..) I dont think so but I want to be sure. Thanks in advance. Lyle Jayma
April 29, 201610 yr I know it has to do with the fsdt/couatl applications but I dont own any of the sceneries or GSX. I did own have the QW757 but I deleted it from 3.1. Have you checked your exe.xml and dll.xml file for these Old Entries Located here AppData ► Roaming ► Lockheed Martin ► PreparD v3
April 29, 201610 yr You can try reinstalling the legacy Simconnect files and that fixes this many times. I had one issue that would not go away and found this on the Virtuali forums. Fixed it for me. ---------------------------- copy the following from : C:\Users\Your Name\AppData\Roaming\Lockheed Martin\Prepar3D v3 "dll.xml" file to C:\ProgramData\Lockheed Martin\Prepar3D v3 "dll.xml" Quote <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> Mark CYYZ
April 30, 201610 yr Author Have you checked your exe.xml and dll.xml file for these Old Entries Located here AppData ► Roaming ► Lockheed Martin ► PreparD v3 Here are the entries in the exe.dll and dll.xml exe.xml <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Couatl</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>fsdreamteam\couatl\couatl.exe</Path> </Launch.Addon> <Launch.Addon> <Name>as_btstrp_config_manager</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp_config_manager.exe</Path> </Launch.Addon> </SimBase.Document> dll.xml <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> You can try reinstalling the legacy Simconnect files and that fixes this many times. I had one issue that would not go away and found this on the Virtuali forums. Fixed it for me. ---------------------------- copy the following from : C:\Users\Your Name\AppData\Roaming\Lockheed Martin\Prepar3D v3 "dll.xml" file to C:\ProgramData\Lockheed Martin\Prepar3D v3 "dll.xml" Quote <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> Mark, Based on what I added in Poppet's question is this still the case to copy the dll.xml to the program folder? You can try reinstalling the legacy Simconnect files and that fixes this many times. I had one issue that would not go away and found this on the Virtuali forums. Fixed it for me. ---------------------------- copy the following from : C:\Users\Your Name\AppData\Roaming\Lockheed Martin\Prepar3D v3 "dll.xml" file to C:\ProgramData\Lockheed Martin\Prepar3D v3 "dll.xml" Quote <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> Additionally, my dll.xml file in the ProgramData folder is the following: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="AceXML" version="3,0" id="dll"> <Descr>AceXML Document</Descr> <Filename>dll.xml</Filename> <Launch.Addon> <Name>SODE Animation Module</Name> <Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Flight Recorder</Name> <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path> </Launch.Addon> </SimBase.Document> Lyle Jayma
April 30, 201610 yr I can see in your exe.xml and dll.xml file you have old Entries for FSDT Products. \couatl and bglmanx.dll I have removed this Entry in your exe.xml file, Copy and paste this into your exe.xml file. The Entry at the bottom is for your Active Sky Next. <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>as_btstrp_config_manager</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp_config_manager.exe</Path> </Launch.Addon> </SimBase.Document> Option 1 Your dll.xml file. Is this the only Entry you have in your dll.xml file? Remove this Entry as well. Option 2 Right Click and delete both files complete, dll.xml and exe.xml file. Prepar3D will create new files when you start again. After you delete these files, Start Active Sky Next and it will insert the appropriate Entries again in both files Additionally, my dll.xml file in the ProgramData folder is the following: Edit Sorry, I did't see read post above me properly. When you Install Software, In "some cases" Entries will be added to both dll.xml files located in ProgramData and AppData\Roaming, These 2 Entries will merge together when you start Prepar3D, But if one of these Entries is corrupt or wrong you might just have the above problem. Check both locations
April 30, 201610 yr Author I can see in your exe.xml and dll.xml file you have old Entries for FSDT Products. \couatl and bglmanx.dll I have removed this Entry in your exe.xml file, Copy and paste this into your exe.xml file. The Entry at the bottom is for your Active Sky Next. <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>as_btstrp_config_manager</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp_config_manager.exe</Path> </Launch.Addon> </SimBase.Document> Option 1 Your dll.xml file. Is this the only Entry you have in your dll.xml file? Remove this Entry as well. Option 2 Right Click and delete both files complete, dll.xml and exe.xml file. Prepar3D will create new files when you start again. After you delete these files, Start Active Sky Next and it will insert the appropriate Entries again in both files Edit Sorry, I did't see read post above me properly. When you Install Software, In "some cases" Entries will be added to both dll.xml files located in ProgramData and AppData\Roaming, These 2 Entries will merge together when you start Prepar3D, But if one of these Entries is corrupt or wrong you might just have the above problem. Check both locations In AppRoaming should I delete this entry as well? AppRoaming> dll.xml </Launch.Addon> <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> AppRoaming>exe.dll Use this to remove the references to coutl and fsdreamteam <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>as_btstrp_config_manager</Name> <Disabled>False</Disabled> <Path>as_srv\as_btstrp_config_manager.exe</Path> </Launch.Addon> </SimBase.Document> ProgramData Folder > dll.xml - No change becuase there is no reference to bglmanx.dll </Launch.Addon> <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> ProgramDate>exe.dll No change - to confirm <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="AceXML" version="3,0" id="exe"> <Descr>AceXML Document</Descr> <Filename>exe.xml</Filename> <Launch.Addon> <Name>SODE</Name> <Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectDisplayEngine.exe</Path> <CommandLine>P3Dv3</CommandLine> </Launch.Addon> </SimBase.Document> Lyle Jayma
April 30, 201610 yr Mark, Based on what I added in Poppet's question is this still the case to copy the dll.xml to the program folder? I am not sure, you will have to try it. Mark CYYZ
April 30, 201610 yr Lyle, first get your Sim up and running again Stable with no Entries in either file, Basically you want to start with a fresh slate. The quickest way to sort this would be delete these files located here (C:) ►ProgramData ► Lockheed Martin ► PreparD v3 exe.xml + dll.xml (C:) ► Users ► you ► AppData ► Roaming ► Lockheed Martin ► PreparD v3 exe.xml + dll.xml --------------------------- Uninstall Addon_Manager in Programs and Features Start Prepar3D and then close it down. First insure you have your SimConnect installed. You might have a corrupt or missing SimConnect.msi file. Located here Prepar3D v3 ► redist ► Interface. Click into each one, Click into lib. Right Click and Install each one ------------------------- After you have Prepar3D up and running with no error's. From what i can see from both files you have posted you are running SODE + Active Sky Next and your running Addon_Manager (1) Sim Object Display Engine requires an Entry in both your exe.xml and your dll.xml file to function located in ProgramData ► Lockheed Martin ► PreparD v3. So if you want to run Sode again go to the SODE Plateform Manager usually located in C\Programfiles(86) and Click activate, this will add these 2 Entries back again. ------- (2) When you start Active Sky Next it will create and add an Entry to your exe.xml and your dll.xml file Automatically located here AppData ► Roaming ► Lockheed Martin ► PreparD v3. -------- (3) If you want to run Addon_Manager again bglmanx (If you have Software that Requires it) you need to disable your Antivirus Software when Installing Addon_Manager and your UAC User Account Control https://www.fsdreamteam.com/products_addonmanager.html See if that helps
May 2, 201610 yr Great Stuff :smile: Yes, when you have all these different Entries in your dll.xml and exe.xml file all working together they can get a bit mixed up alright
Create an account or sign in to comment