FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: SkyblueX on September 03, 2015, 01:48:19 am
-
Hey guys, I seem to have run into a weird problem today...
I was playing around with the Ezdok camera I just purchased. GSX was working like normally after I initially installed Ezdok. However, I added a new camera into Ezdok, and all of a sudden my GSX menu disappears. I've been through that disappearance problem before, so normally, I just reinstalled the Addon manager. Midway through the installation, I encountered a message I never seen before - it was something about the coatll engine being shutdown in order to a update (I don't remember exactly). I let the engine get shut down, and the installation was completed like normall. Before I launched FSX, I shut down my Internet connection (I use a hotspot). FSX started up like normally but this time, a error message appeared-
Flight simulator has detected a problem with a third party software program:
Name: bglmanx Dynamic Link Library
Version: 3, 0, 0, 7
Company: VIRTUALI Sagl
File: bglmanx.dll
Do you want to run this software?
... I click yes, and then another error message appears...
bglmanx.dll - Entry Point Not Found
The procedure entry point SimConnect_Text could not be located in the dynamic link library simconnect.dll
... FSX immediately shuts down after I click OK. I have no idea how to fix it. Any help is greatly appreciated.
-
Here's some extra information if needed-
I'm running FSX Gold Edition (both SP installed), along with numerous other addons
My computer is using Windows 8,64 bit (yes, UAC is turned off)
The last time I updated GSX was around August 18. That installation was successful
This time I downloaded the main addon manager from the GSX purchase site
Due to my Internet limitations, I usually download the installer into my phone, and then run the exe on the computer. Sometimes I let the computer connect to the Internet only for the installation.
-
I was playing around with the Ezdok camera I just purchased. GSX was working like normally after I initially installed Ezdok. However, I added a new camera into Ezdok, and all of a sudden my GSX menu disappears.
We have had some reports of Ezdok causing problems with GSX, most likely because of ways to deal with keys.
I've been through that disappearance problem before, so normally, I just reinstalled the Addon manager. Midway through the installation, I encountered a message I never seen before - it was something about the coatll engine being shutdown in order to a update (I don't remember exactly). I let the engine get shut down, and the installation was completed like normall.
It seems that Ezdok caused the GSX menu to disappear, but Couatl.exe was still running so, it's normal you would have seen such message, and the installer dealt with correctly.
Do you want to run this software?
... I click yes, and then another error message appears...
bglmanx.dll - Entry Point Not Found
The procedure entry point SimConnect_Text could not be located in the dynamic link library simconnect.dll
... FSX immediately shuts down after I click OK. I have no idea how to fix it. Any help is greatly appreciated.
That looks like a mismatch of old/new versions, which might have been caused by a problem with the internet connection, perhaps some files the installer was supposed to download weren't downloaded correctly.
That error message is a generic panic message from FSX, when it cannot load a module. It's clear that it wasn't able to load bglmanx.dll because bglmanx.dll wasn't able to load Simconnect.dll or, more precisely, it couldn't find the SimConnect_Text function in simconnect.dll. Meaning, it HAS found simconnect.dll, but it couldn't find that function, so I suspect Windows is supplying bglmanx.dlll with an OLDER (pre-SP2) Simconnect version that is installed in your system, but it's not the one bglmanx.dll needs ( it needs the SP2/Acceleration Pack version ).
Now, since bglmanx.dll requires the the SP2/Acceleration Pack version of simconnect since many years, and nothing has changed, it's possible your Windows Side-by-side loading subsystem is acting up and trying to load the wrong version.
It's also possible that, because another addon you installed that requested the pre-SP2 version, Windows is not able to sort out the (very complex) system that would allow TWO modules running in the same memory space, to each one request and use a DIFFERENT .DLL, which is exactly what the Side-by-side system is supposed to do WHEN IT WORKS.
I'd try with this:
- Download and install the latest Addon Manager now. This will ensure that, in addition to *download* the latest files, it also *contains* the latest files so, even if you had a problem while downloading, there cannot be any version mismatch due to incomplete downloads.
- Do all of this AFTER a WINDOWS RESTART. This should prevent other loaded modules to cause issues in memory.
-
Thanks for the detailed response.
Initially I did download the installer through the main site, like I always had. However, I never did a restart, so maybe this might help? I'll report back soon
-
Unfortunately it seems like it didn't work. The same error messages appear.
-
Same problem here, extremely irritating. Same version of error too (3, 0, 0, 7). I've tried so many things from different threads and this one, including uninstalling everything FSDreamteam related and then reinstalling only Standalone Addon Manager.
This started happening only after installing GSX; I already had KLAS, LSGG, and a few other airports installed.
I have disabled antivirus and am running Windows 10.
Images:
http://i59.tinypic.com/2qncexe.png (http://i59.tinypic.com/2qncexe.png)
http://i58.tinypic.com/2sbrjmx.png (http://i58.tinypic.com/2sbrjmx.png)
-
Also having the exact same problem and error messages as the previous posts after updating Couatl and the Addon Manager.
I have also just recently reinstalled FSX with just a few addons. I have GSX and all other FSdreamteam scenery.
-
Yes, I also forgot to mention that this only happens in the newest version. I've purchased a lot of addons before, but this is my first experiencing this error. I've done all the suggested solutions, but I still get this error. And it's driving me crazy, as I absolutely refuse to fly on FSX without GSX.
-
The only way I can get FSX to run as before is to click on the NO option, as on the screen similar to the first pic as posted by fsx100. Obviously then the Addon Manager option is not present at all in FSX and no FSdreamteam scenery works. I have also tried other options as posted in other threads I have read.
-
Same issue here on Windows 10 x64 after a reinstall of GSX. Couldn't it be related to a corrupt file on your side? Since these issues rise since a couple of days?
-
Same issue here on Windows 10 x64 after a reinstall of GSX. Couldn't it be related to a corrupt file on your side? Since these issues rise since a couple of days?
Before replying to users reporting such problem, I ALWAYS check if the problem can be replicated, doing exactly what the user said it did, for example reinstalling GSX so, if the file was really corrupted on our side, it would be immediately noticeable.
In addition to that, all our executables are digitally signed, so you don't have to "guess" if a file might have been corrupted or you got a bad download, because if you had, the digital signature would become invalid, and you'll see a warning from FSX that the publisher is unknown, which should alert you that something is not right with the file. If you haven't got that warning and you saw the normal request to authorize the module, with the "Virtuali" signature, you can be sure that's nothing is corrupted.
We HAD a small change in the installer though, and I suspect this might have something to do with your error.
Following a user report of a problem of the installer crashing when trying to write the DLL.XML file, that happened ONLY on Windows in Slovak language (nobody ever reported it before, and I couldn't reproduce the crash with the user file on my system, which leads to believe Windows treats XML files a bit different on some OS versions), we decided to make a small change and, instead of always placing the bglmanx.dll line as the first entry in the DLL.XML file (like we used to), the line will now placed at the end.
This fixed the issue immediately for that user, and he told me this change would grant us the gratitude of a whole forum in Slovakia, when everybody basically had that error and couldn't install anything from FSDT.
I do recall that we had to place bglmanx.dll always on top, because another 3rd party module had a problem that, anything loaded after it and using a different version of the Simconnect library, would crash. I *think* it was FS Copilot, but I'm not 100% sure. In any case, I assumed that after all these years, no developer would still use the original Simconnect anymore (the version we use has been released in 2007), considering that is also slower, since it always used a TCP connection, even when no networking was involved, and of course it has less features and many bugs.
Under NORMAL conditions, the loading order shouldn't matter but, it's POSSIBLE (this is just a guess) that, if you have OTHER 3rd party modules that are linked against an OLDER version of the Simconnect library, which now are loaded *before* the Addon Manager, the Windows Side-by-side mechanism, which is supposed (WHEN IT WORKS), to allow multiple versions of the same .DLL to be and run in the same memory address space at the same time, is not working correctly and, the fist module loaded will load the outdated version, and so bglmanx.dll will be forced to run with that version too, even if it has specifically indicated to Windows it needs the CURRENT one.
That's why you are seeing the error about Simconnect_text() not found. This API call wasn't available in the original Simconnect RTM, the one that was included with plain FSX before any Service Packs. It was added only with the SP1 and beyond.
The most likely explanation of this is that, because another 3rd party module that uses the original Simconnect is loading *before* bglmanx.dll, your FSX will load the old Simconnect, but it won't re-load the new one when bglmanx.dll asks for it. SInce the old one doesn't have the Simconnect_text() function, you get that error.
Unfortunately, the DLL.XML file I used for testing, which includes many other 3rd party modules, like the ones from PMDG, FSUIPC, Aerosoft, Level-D, FSX, VRS, doesn't have any problems, regardless if I place the bglmanx.dll at the start or at the end of the file. And this is how is supposed to work but, maybe, none of these modules is trying to load the old Simconnect, so no conflicts happens.
There would be an easy way to test this, for those affected:
- Open your %APPDATA%\Microsoft\FSX\DLL.XML file
- Look for these lines ( they are probably on the bottom of the file now:
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
Cut all these lines (from the <Launch.Addon> tag to the </Launch.Addon> closing tag), and paste them as the first section, after the first lines of the file, so it will end up to something similar to this:
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
<Launch.Addon>
....
</Launch.Addon>
<Launch.Addon>
....
</Launch.Addon>
<Launch.Addon>
....
</Launch.Addon>
<Launch.Addon>
....
</Launch.Addon>
<Launch.Addon>
....
</Launch.Addon>
</SimBase.Document>
If we are lucky, and the theory of the loading order is correct, it might fix your error. If not, then I've guessed wrong, and the problem lies elsewhere.
-
Thank you, it worked!
The first time I loaded FSX the 3,0,0,7 warning came up, but after pressing OK FSX loaded normally. It hasn't come up again.
-
Yup same here got the 1st warning screen but clicked YES and everything seems to load fine now :) Thanks.
-
Yes! I finally have ground services. I did run into another minor problem- Somehow, the AFCAD files were deleted, but I quickly solved it by reinstalling the Addon manager (the bglmanx.dll error came up again, but I just applied your solution again) and the problem was solved.
Once again, thank you so much for your quick response time and detailed response!
-
Include me as one of those who found this solution to be what was needed.
Ground support has been restored.
-
Thanks guys. I had the same problem, and this solution also worked for me.
-
Many thanks Umberto. This also solved the issue for me. Did not want to blame you for not testing, just was looking for similarities. I think it is wise to add this to the FAQ. Found a lot of users who had this issue.
-
Works for me too. Thanks Umberto :)
-
Many thanks Umberto. This also solved the issue for me. Did not want to blame you for not testing, just was looking for similarities. I think it is wise to add this to the FAQ. Found a lot of users who had this issue.
The only users that had this problem are:
- Those that downloaded GSX in the last couple of days, after we modified the installer, following that report of that user from Slovakia that, THANKS to that change, was finally able to install it correctly. He, and a whole forum of users in that country
AND
- In *addition* to the above, the only users affected, are those with ANOTHER 3rd party module that still uses the original Simconnect from FSX RTM that, by loading before bglmanx.dll, has forced FSX to use the old version, which is something that should happen in the first place, thanks to the Windows SxS mechanism.
But that's all history now, because I've already changed the installers (it was just the GSX and the Stand-Alone Addon Manager installers), and now they have bglmanx.dll on top of the DLL.XML, as they always had, but there's also a separate handling of the case which affected Windows in Slovak ( and possibly other less common language versions, although we never had any other reports before ), so it should work in any case now.
I would be interested to know which modules you had installed, to identify which one was causing FSX to load only the original Simconnect. I really cannot see why any developer would want to link against the original Simconnect, since the SP2 version has been out since 8 years...
-
The only payware addons I own are-
iFly 737, Aerosoft A32X, New York City X and KJFK X, and REX Soft Clouds. (all of these worked as normal before the bgl error happened)
I have numerous freeware addons (too many to tell exactly). But the most recent one I installed was Schiphol scenery from NL2000.
-
My DLL's are (in the correct order):
- LHBP_objectPlacer.dll (LHSimulations Budapest)
- AFXModuleFSX.dll (Airport Facilitator X)
- ViMaCoreX.dll (Vistamare)
- AS-FlightRecorder.dll (Aerosoft Flight Recorder (Airbus series))
- RAASPRO.dll (RAAS Professional for Airbus)
- FSUIPC4.dll (FSUIPC 4.944)
- as_btstrp.dll (Active Sky Next)
-
The only payware addons I own are-
iFly 737, Aerosoft A32X, New York City X and KJFK X, and REX Soft Clouds. (all of these worked as normal before the bgl error happened)
Rather than indicating your payware addon, you should list all the modules ( regardless if they are pawware or freeware ) in your DLL.XML. Not all payware addons use modules in the DLL.XML, and some freeware do.
They worked before, because previous versions of our installer AND the very latest one, always placed the bglmanx.dll line before everything else, so another module using an older version of Simconnect didn't had a chance to break the Windows SxS system that should allow many modules to obtain their own preferred version.
-
My DLL's are (in the correct order):
I made a quick check on these and, according to their manifest file, they requires the following Simconnect versions:
LHBP_objectPlacer.dll (LHSimulations Budapest) - 10.0.61242 - FSX SP1
AFXModuleFSX.dll (Airport Facilitator X) - 10.0.60905 - FSX RTM
ViMaCoreX.dll (Vistamare) - Doesn't have a manifest, it probably loads Simconnect dynamically.
AS-FlightRecorder.dll (Aerosoft Flight Recorder (Airbus series)) - This one includes ALL different Simconnect versions in its manifest file. This doesn't seem to be a good idea, according to this post on a MSDN blog:
http://blogs.msdn.com/b/nikolad/archive/2007/03/29/a-solution-to-two-references-to-different-versions-of-crt-mfc-atl-in-one-application-manifest-file.aspx
RAASPRO.dll (RAAS Professional for Airbus) - 10.0.60905 - FSX RTM
FSUIPC4.dll (FSUIPC 4.944) - Doesn't have a manifest, so it loads Simconnect dynamically.
I don't have the as_btstrp.dll, but I tested other modules too:
PMDG_HUD_interface.dll and PMDG_Interface.dll - 10.0.61259 - FSX SP2
ObjectFlow.dll from OrbX FTX - Doesn't have Simconnect referenced in the manifest, but the are references in the code to the 10.0.61259 ( FSX SP2 ) version, which seems to be loaded explicitly.
LeonardoSH.dll (from the Maddog) - 10.0.60905 - FSX RTM
LVLD.DLL - 10.0.61259 - FSX SP2
SimObjectAnimationModule.DLL ( SODE ) - 10.0.61259 - FSX SP2
To sum up:
1) PMDG, Level-D, SODE, ViMaCoreX, FSUIPC4 and ObjectFlow.dll all require the latest Simconnect version, the one released with FSX SP2, either from their manifest, or by loading it dynamically, so they cannot have been the cause of the problem.
2) LHBP_objectPlacer.dll requires the FSX SP1 version, which DOES have the Simconnect_text() function call, so this wouldn't be a problem either.
3) AFXModuleFSX.dll, RAASPRO.dll, and LeonardoSH.dll require the FSX RTM Simconnect, so any of them might have caused this. However, I use AFX myself, and never had a problem with it, regardless of the loading order.
4) AS-FlightRecorder.dll - This one look odd, so I'll try to test it more now...
-
Hi I've started getting this error on launching P3D v3.1. I have tried all suggestions included in this thread with no joy. I have since uninstalled and re-installed the P3D v3.1 client, Simconnect clients v10.0.60905.0, 10.0.61242.0, 10.0.61259, as well as ESP Simconnect v1.0.20.0. I even repaired the VC++ Redistirbutables. Still getting the same "entry point" error.
Is there anything else I can try to resolve the issue?
-
Hi I've started getting this error on launching P3D v3.1. I have tried all suggestions included in this thread with no joy. I have since uninstalled and re-installed the P3D v3.1 client, Simconnect clients v10.0.60905.0, 10.0.61242.0, 10.0.61259, as well as ESP Simconnect v1.0.20.0. I even repaired the VC++ Redistirbutables. Still getting the same "entry point" error.
Is there anything else I can try to resolve the issue?
Same here - also P3D v3.1 - tried anything and even reinstalled P3D! Wasted Sunday only to find that issue popping up again :'(
-
Same here - also P3D v3.1 - tried anything and even reinstalled P3D! Wasted Sunday only to find that issue popping up again :'(
There wasn't any need to reinstall P3D and we surely haven't suggest this. The problem is the FSX Simconnect client version SP2 is not correctly installer. See this thread for all known solutions:
http://www.fsdreamteam.com/forum/index.php/topic,13029.0.html
-
Thanks Umberto. Will have a look at these options and will report back. FYI, I did not uninstall P3D in it's entirety. I only uninstalled and re-installed the client module, leaving all the content unaffected. That's the beauty of the new modular structure of P3D.
-
FYI, I did not uninstall P3D in it's entirety. I only uninstalled and re-installed the client module, leaving all the content unaffected. That's the beauty of the new modular structure of P3D.
Yes, at least it was quick. However, just keep in mind that, nothing in the P3D install/uninstall process relates to the backward-compatible FSX Simconnect clients.
They are never installed/uninstalled by P3D, and are always optional installations that you are supposed to install manually from their .MSI files in the SDK/Legacy folder under P3D. Our installer will automatically launch the .MSI file but, it's possible that either the Simconnect installation itself has an issues OR your system is also missing OTHER dependencies that the FSX Simconnect clients requires, like the VC++ 2005 SP1 redistributable runtimes, which also need to be correctly installed.
-
Many thanks Umberto. The bglmanx.dll issue has been resolved. Unfortunately, I am now getting a couatl.exe application error ("The application was unable to start correctly (0xc0150004)"). I am aware of other threads dealing with such errors and will follow up there.