addon manager crash on exit p3d 4.2 **SOLVED**

[Cruachan]

API.DLL is related to Simconnect but, interestingly enough, the bug we FIXED in our program didn't had anything to do with Simconnect. It was purely something of an internal communication between the Addon Manager and Couatl, which use their own communication channel. It's also possibly related to the new PDK.

So, it's possible the issue happens also in combination with other addons, which also use the either  Simconnect or the PDK.

If this is the case then the most likely candidate would be the recently released FSPS FFTF Dynamic utility App** which is configured to load/unload automatically with the sim.

In order to know what changed, we should know which exact release you had before the update.

I returned recently after a short holiday and ran the FSDT Live Updater as part of the sim loading process to the default Flight Situation. All was well until I updated again the following day and that's when the exit issue surfaced. So the version must have been the one immediately preceding the 'bugged' version.

Are you running P3D4 As Administrator, which is NOT how it's installed by default ? I tried it and yes, I DO have the API.DLL crash, but only by changing the Compatibility settings to run As Admin.

Now this struck a chord. I installed GSX Ground Services on 03/12/2017 and up until then it was my habit to install everything as Administrator. **Since then, in connection with FFTF Dynamic, I have had very interesting discussions with Steve Waite who has pointed out the error of my ways. Installers usually create their own permissions for access when it is necessary to do so. Imposing your own permissions can lead to problems and so it's best not to follow this route. Just double-click an installer and let it do what is necessary.

So, I tried modifying the Users permissions to the Addon Manager folder by allowing Modify and Write (the latter is checked automatically once Modify is checked. I've been through all my relevant P3D-related installations and treated them in the same way. This appears to have had no negative effects over the past couple of months so must be doing something right    Unfortunately this didn't resolve the exit issue so perhaps the 'damage' was not reversible in this instance. At this point I decided to carry out a clean reinstall of GSX.   

"Has the original main installer been updated? If so, then perhaps the logical next step would be for me to start again by obtaining a fresh download of the product from my account and then perform a clean reinstall."

I doubt it will make any difference, because the installer would download the same file as the updater. In fact, the installer *starts* the Live Updater, same as if you launched it manually.

I'm sure you're right. However, too late..lol! GSX has been uninstalled earlier this afternoon (Scotland) and I'm about to carry out a fresh install using the latest downloaded installer.

Fingers crossed! I'll be sure to let you know the outcome.

Regards,
Mike

[Cruachan]

Hi Umberto,

Okay, here are my findings.

Prepar3D v4.2 EXIT RESULTS

Each occasion sim crashes on exit:


(1) CLEAN reinstall of GSX Ground Services  [E:\Program Files (x86)\Addon Manager]
(Run as administrator NOT selected):

Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> CRASH
End Scenario -> Exit Prepar3D -> Yes -> CRASH
Exit (from Prepar3D Scenario screen) -> NO Crash

(2) FFTF Dynamic disabled:

Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> CRASH
End Scenario -> Exit Prepar3D -> Yes -> CRASH
Exit (from Prepar3D Scenario screen) -> NO Crash

(3) Add-ons... DISABLED:




Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> NO Crash
Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> CRASH

End Scenario -> Exit Prepar3D -> Yes -> CRASH
Exit (from Prepar3D Scenario screen) -> NO Crash

(4) AppData

DLL.XML (Disabled = True):


Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> CRASH
End Scenario -> Exit Prepar3D -> Yes -> CRASH
Exit (from Prepar3D Scenario screen) -> NO Crash

EXE.XML (Disabled = True)

Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> CRASH
End Scenario -> Exit Prepar3D -> Yes -> CRASH
Exit (from Prepar3D Scenario screen) -> NO Crash

(5) ProgramData (dll.xml)
 
XMLTools64 (Disabled = True)
PMDG_HUD_interface (Disabled = True)
RAASPRO (Disabled = True)

Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> CRASH
End Scenario -> Exit Prepar3D -> Yes -> CRASH
Exit (from Prepar3D Scenario screen) -> NO Crash

(6) ProgramData (exe.xml)

FFTF Dynamic P3Dv4 (Disabled = True)

See item (2)

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


(7) RE-ENABLED (4, 5 and 6)

Prepar3D CRASHED within a few seconds of appearance of splash screen
during initial load!

Log Name:      Application
Source:        Application Error
Date:          23/05/2018 22:55:10
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Prometheus
Description:
Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time

stamp: 0x5a7c832c
Faulting module name: api.dll, version: 4.2.21.24048, time stamp:

0x5a7c83e1
Exception code: 0xc0000005
Fault offset: 0x0000000000015611
Faulting process id: 0x2154
Faulting application start time: 0x01d3f2e048737023
Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\Lockheed Martin\Prepar3D v4\api.dll
Report Id: f60330a3-5ed3-11e8-9f06-40e230989421
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-05-23T21:55:10.000000000Z" />
    <EventRecordID>234800</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Prometheus</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.2.21.24048</Data>
    <Data>5a7c832c</Data>
    <Data>api.dll</Data>
    <Data>4.2.21.24048</Data>
    <Data>5a7c83e1</Data>
    <Data>c0000005</Data>
    <Data>0000000000015611</Data>
    <Data>2154</Data>
    <Data>01d3f2e048737023</Data>
    <Data>D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>D:\Lockheed Martin\Prepar3D v4\api.dll</Data>
    <Data>f60330a3-5ed3-11e8-9f06-40e230989421</Data>
  </EventData>
</Event>

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

[8] SYSTEM RESTART:

Prepar3D Loaded successfully.

RE-ENABLED (3)

Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> CRASH


[9] Prepar3D Loaded successfully.

DISABLED FsDreamTeam Addon Manager and RESTART SIM

Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> NO Crash

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

So, the conclusion appears to be that no other Add-on is implicated in causing this behaviour.



Kind regards,
Mike

[virtuali]

As I've said in my previous post, are you running P3D4 As Administrator, which is NOT how it's installed by default ? I tried it and yes, I DO have the API.DLL crash, but only by changing the Compatibility settings to run As Admin.

That explains why I couldn't replicate it before: I was running the sim as installed by default by LM. Now that I can sill replicate it, there might be a chance of really fixing it.

Could you please check if resetting P3D to default (NO Admin mode), fixes the crash ? We would like to know, which doesn't mean we'll not try to find the cause but, at least, it would be best being sure the issue is only caused by a configuration of the sim altered from the default installation.

[Cruachan]

As I've said in my previous post, are you running P3D4 As Administrator, which is NOT how it's installed by default ? I tried it and yes, I DO have the API.DLL crash, but only by changing the Compatibility settings to run As Admin.

That explains why I couldn't replicate it before: I was running the sim as installed by default by LM. Now that I can sill replicate it, there might be a chance of really fixing it.

Could you please check if resetting P3D to default (NO Admin mode), fixes the crash ? We would like to know, which doesn't mean we'll not try to find the cause but, at least, it would be best being sure the issue is only caused by a configuration of the sim altered from the default installation.

Hi Umberto,

I do apologise, I’m afraid I overlooked that for some reason. I became too focussed on the possibility that an Addon might be involved. At least we know now that is not the case. I’ll check ASAP. However, as part of my aforementioned discussions with Steve Waite I think that would have been checked and, if necessary, changed. I do recall changing Users permissions on the Lockheed Martin folder to allow Modify and Write.

Regards,
Mike

[virtuali]

maybe I found something, could you please try this version, to overwrite the one in \Addon Manager ?

http://update.fsdreamteam.com/LOG/bglmanx.dll

[Cruachan]

maybe I found something, could you please try this version, to overwrite the one in \Addon Manager ?

http://update.fsdreamteam.com/LOG/bglmanx.dll

Hi Umberto,

Like you, I too thought I had stumbled on something but, sadly, it was not to be.

I checked the Priviledge Level of Prepar3D.exe and was somewhat surprised to find:


So, the box was unchecked and I ran P3D only to have this popup appear during initial loading:


The Sim crashed on EXIT as on previous occasions. I rechecked the Priviledge Level of Prepar3D.exe:


So, at this point, it was reasonable to assume that FSLabs might be the culprit as it was resetting the Privilege Level!

I ran the Sim again and disabled Flight Sim Labs Products, but not Flight Sim Labs Spotlights, and tried again.
This time the Priviedge Level of Prepar3D.exe remained unchanged (box unchecked).
The Sim was restarted and crashed on EXIT as before. Same error, etc.

I tried the substitution of bglmanx.dll with the new one you provided but, again, with the same result: Sim crashed on EXIT.

Frustrating!

Regards,
Mike

[virtuali]

I tried the substitution of bglmanx.dll with the new one you provided but, again, with the same result: Sim crashed on EXIT.

Please be sure of this:

- Is P3D now running as default, with No Admin rights ?

- Are you sure you temporarily disabled ALL addons, except the Addon Manager. To do this, you must be sure you disabled each and every addon in the Options->Add-ons menu AND each and every addon in all 4 XML files:

%APPDATA%\Lockheed Martin\Prepar3d v4\DLL.XML
%APPDATA%\Lockheed Martin\Prepar3d v4\EXE.XML
%PROGRAMDATA%\Lockheed Martin\Prepar3d v4\DLL.XML
%PROGRAMDATA%\Lockheed Martin\Prepar3d v4\EXE.XML

- Are you using the bglmanx.dll I just posted ?

I'm trying to let you ending in the same situation as I'm now: no crashes on exit with the Addon Manager enabled, and nothing else.

[Cruachan]

Hi Umberto,

I didn’t test your posted bglmanx.dll with that configuration as everything had been re-enabled after testing (see 6 posts above) with the exception of the FSLabs Flight Sim Products Add-on entry.

I will do so now.

Regards,
Mike

[Cruachan]

Okay Umberto, first to confirm we are now both on the same page:













Note: No Add-ons item on the Menu bar


EXIT RESULTS:

(1a) Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> NO Crash
(1b) Exit (from fully loaded Prepar3D Default Scenario) -> Yes -> "Couatl Scripting Engine for FSX/ESP has stopped working"

Log Name:      Application
Source:        Application Error
Date:          24/05/2018 16:01:37
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Prometheus
Description:
Faulting application name: Couatl.exe, version: 3.2.0.3995, time stamp: 0x5b03513f
Faulting module name: Couatl.exe, version: 3.2.0.3995, time stamp: 0x5b03513f
Exception code: 0xc0000005
Fault offset: 0x00056fa4
Faulting process id: 0x28b4
Faulting application start time: 0x01d3f36fdbcf4d33
Faulting application path: E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe
Faulting module path: E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe
Report Id: 5b0a2d18-5f63-11e8-816d-40e230989421
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-05-24T15:01:37.000000000Z" />
    <EventRecordID>235000</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Prometheus</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Couatl.exe</Data>
    <Data>3.2.0.3995</Data>
    <Data>5b03513f</Data>
    <Data>Couatl.exe</Data>
    <Data>3.2.0.3995</Data>
    <Data>5b03513f</Data>
    <Data>c0000005</Data>
    <Data>00056fa4</Data>
    <Data>28b4</Data>
    <Data>01d3f36fdbcf4d33</Data>
    <Data>E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe</Data>
    <Data>E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe</Data>
    <Data>5b0a2d18-5f63-11e8-816d-40e230989421</Data>
  </EventData>
</Event>

(2) End Scenario -> Exit Prepar3D -> Yes -> "Couatl Scripting Engine for FSX/ESP has stopped working"


Log Name:      Application
Source:        Application Error
Date:          24/05/2018 15:48:47
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Prometheus
Description:
Faulting application name: Couatl.exe, version: 3.2.0.3995, time stamp: 0x5b03513f
Faulting module name: Couatl.exe, version: 3.2.0.3995, time stamp: 0x5b03513f
Exception code: 0xc0000005
Fault offset: 0x00056fa4
Faulting process id: 0x33e0
Faulting application start time: 0x01d3f36e1472edfe
Faulting application path: E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe
Faulting module path: E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe
Report Id: 90074d73-5f61-11e8-816d-40e230989421
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-05-24T14:48:47.000000000Z" />
    <EventRecordID>234996</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Prometheus</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Couatl.exe</Data>
    <Data>3.2.0.3995</Data>
    <Data>5b03513f</Data>
    <Data>Couatl.exe</Data>
    <Data>3.2.0.3995</Data>
    <Data>5b03513f</Data>
    <Data>c0000005</Data>
    <Data>00056fa4</Data>
    <Data>33e0</Data>
    <Data>01d3f36e1472edfe</Data>
    <Data>E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe</Data>
    <Data>E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe</Data>
    <Data>90074d73-5f61-11e8-816d-40e230989421</Data>
  </EventData>
</Event>

(3) Exit (from Prepar3D Scenario screen) -> "Couatl Scripting Engine for FSX/ESP has stopped working"

Log Name:      Application
Source:        Application Error
Date:          24/05/2018 15:54:26
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Prometheus
Description:
Faulting application name: Couatl.exe, version: 3.2.0.3995, time stamp: 0x5b03513f
Faulting module name: Couatl.exe, version: 3.2.0.3995, time stamp: 0x5b03513f
Exception code: 0xc0000005
Fault offset: 0x00056fa4
Faulting process id: 0x30e4
Faulting application start time: 0x01d3f36efde9610d
Faulting application path: E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe
Faulting module path: E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe
Report Id: 59d00134-5f62-11e8-816d-40e230989421
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-05-24T14:54:26.000000000Z" />
    <EventRecordID>234998</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Prometheus</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Couatl.exe</Data>
    <Data>3.2.0.3995</Data>
    <Data>5b03513f</Data>
    <Data>Couatl.exe</Data>
    <Data>3.2.0.3995</Data>
    <Data>5b03513f</Data>
    <Data>c0000005</Data>
    <Data>00056fa4</Data>
    <Data>30e4</Data>
    <Data>01d3f36efde9610d</Data>
    <Data>E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe</Data>
    <Data>E:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe</Data>
    <Data>59d00134-5f62-11e8-816d-40e230989421</Data>
  </EventData>
</Event>

Regards,
Mike

[p3dx3]

If you change each dll and exe xml to utf-8 encoding instead of windows-1252? I am not at home to test yet

[p3dx3]

My compatibility check box for run as admin is not checked, but I right click the P3D shortcut and select run as administrator, every time I start. I do this to Activesky also

[Cruachan]

If you change each dll and exe xml to utf-8 encoding instead of windows-1252? I am not at home to test yet

That’s odd. I’m quite certain all these files were encoded UCS-2 LE BOM as I have been using Notepad++ to preserve the encoding and perform any editing. Yet now I see they have all been changed to Windows-1252 encoding.

I checked Prepar3D.cfg, Scenery.cfg and LWcfg.cfg.xml (just selected at random) and their encoded format remains as UCS-2 LE BOM.

Not sure whether this could be significant as the sim seems to be reading all these Windows-1252 encoded files without apparent problems as all my Add-ons are working.

I would be interested to read Umberto’s take on this and whether I should change the encoding. Why would it have an influence on the ‘Crash on EXIT’ issue with the FSDT Addon Manager in play?

Mike

[p3dx3]

If you change each dll and exe xml to utf-8 encoding instead of windows-1252? I am not at home to test yet

That’s odd. I’m quite certain all these files were encoded UCS-2 LE BOM as I have been using Notepad++ to preserve the encoding and perform any editing. Yet now I see they have all been changed to Windows-1252 encoding.

I checked Prepar3D.cfg, Scenery.cfg and LWcfg.cfg.xml (just selected at random) and their encoded format remains as UCS-2 LE BOM.

Not sure whether this could be significant as the sim seems to be reading all these Windows-1252 encoded files without apparent problems as all my Add-ons are working.

I would be interested to read Umberto’s take on this and whether I should change the encoding. Why would it have an influence on the ‘Crash on EXIT’ issue with the FSDT Addon Manager in play?

Mike

my reading of lockheed martin trying to set the standards, xml files are utf-8 and cfg files should be usc-2

[Cruachan]

Converted those 4 files to UTF-8 encoding. To make this stick I discovered I had to change the encoding first line entry in each file before running the conversion in Notepad++ (<?xml version="1.0" encoding="UTF-8"?>)

Carried out a System Reset - first of the day - and then reloaded the sim:


Spot the difference? The Add-ons menu bar item has reappeared!

EXIT RESULTS:

Sim still crashing on exit with the original reported error implicating the api.dll as the faulting module. Had to test numerous times as the crash seemed more intermittent this time but overall was happening more often than not via all 3 aforementioned EXIT paths from the sim.

NO reappearance of the "Couatl Scripting Engine for FSX/ESP has stopped working" message.

Mike

[virtuali]

I would be interested to read Umberto’s take on this and whether I should change the encoding. Why would it have an influence on the ‘Crash on EXIT’ issue with the FSDT Addon Manager in play?

There was (we thought it was fixed) a bug in P3D 4.0 that, if one DLL/EXE.XML was corrupted/illegal, it would prevent the sim from loading all addons, including the proper one (like our own), which DO NOT use the DLL/EXE.XML anymore, but use the add-on.xml method. Apparently, the bug is still there somehow.

As discussed in other threads, .CFG files are supposed to be UTF16-LE and they *must* be like that, because a .CFG file doesn't have any means to specify its encoding so, applications must agree on some standard.

XML files, instead, CAN specify their encoding so, the only requirement for them to be considered legal, is that the actual encoding of the file must be COHERENT with the encoding specified in their header. If there's NO header, the encoding is assumed to be UTF-8 with NO BOM. So, it's perfectly fine to have an XML encoded in ANSI or Latin-1 (windows 1252), as long the XML header says so. It's only when there's no header, that the file *must* be UTF-8 with no BOM.

But this doesn't have any relationship with the crash on Exit. A module is either loaded or not, it won't work any differently, just because it's XML was more or less correct.

There's not need to report back: we asked help to the "mothership" (Lockheed Martin), and they are helping us finding the cause.