GSX Installation Causes Couatl Force Quit & Kills other FSDT Scenery

[The Dispatcher]

Hi Umberto,

I've been having an ongoing problem with GSX since it's original release, and to this day, still cannot get it to work. I have attempted to install each new GSX update that has been released, but every time I do, I receive a "Couatl Has Stopped Working" message while still in the main FSX start-up menu (before even launching into the sim), which subsequently kills all of my FSDT scenery (everything except ORD, JFK and the European Scenery becomes deactivated, missing all buildings, etc). If I re-install all the scenery, things work fine, but the second I install GSX, the Couatl error persists and my scenery becomes deactivated. I have allowed the automatic update prompt to download the latest version of Addon Manager, and I have also downloaded it manually and installed it as a stand alone product to no avail. The issue is isolated to installing GSX. Any ideas on how I can solve this problem?

Thank You,
Andrew

[virtuali]

As explained in other threads, you should use the Event Viewer, located under the "Administrative Tools" section of the Windows Control Panel, and look in the Application Log, for errors related to FSX.EXE or COUATL.EXE. Any such event should have details about what really crashed, post it here so we can see what's wrong with your system.

[The Dispatcher]

Log Name:      Application
Source:        Application Error
Date:          9/30/2012 1:01:41 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Andrew-PC
Description:
Faulting application name: couatl.exe, version: 2.0.0.2315, time stamp: 0x4fe8eb03
Faulting module name: couatl.exe, version: 2.0.0.2315, time stamp: 0x4fe8eb03
Exception code: 0xc0000005
Fault offset: 0x0000fbf6
Faulting process id: 0x1600
Faulting application start time: 0x01cd9ed94d87ce0c
Faulting application path: C:\FS2006\fsdreamteam\couatl\couatl.exe
Faulting module path: C:\FS2006\fsdreamteam\couatl\couatl.exe
Report Id: af5c4f1c-0acc-11e2-9239-e088eac33f27
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="2012-09-30T07:01:41.000000000Z" />
    <EventRecordID>19715</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Andrew-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>couatl.exe</Data>
    <Data>2.0.0.2315</Data>
    <Data>4fe8eb03</Data>
    <Data>couatl.exe</Data>
    <Data>2.0.0.2315</Data>
    <Data>4fe8eb03</Data>
    <Data>c0000005</Data>
    <Data>0000fbf6</Data>
    <Data>1600</Data>
    <Data>01cd9ed94d87ce0c</Data>
    <Data>C:\FS2006\fsdreamteam\couatl\couatl.exe</Data>
    <Data>C:\FS2006\fsdreamteam\couatl\couatl.exe</Data>
    <Data>af5c4f1c-0acc-11e2-9239-e088eac33f27</Data>
  </EventData>
</Event>

Here is a second event from the installation prior to this most recent one:

Log Name:      Application
Source:        Application Error
Date:          9/28/2012 9:32:40 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Andrew-PC
Description:
Faulting application name: couatl.exe, version: 2.0.0.2315, time stamp: 0x4fe8eb03
Faulting module name: couatl.exe, version: 2.0.0.2315, time stamp: 0x4fe8eb03
Exception code: 0xc0000005
Fault offset: 0x0000fbf6
Faulting process id: 0x1200
Faulting application start time: 0x01cd9df27c788518
Faulting application path: C:\FS2006\fsdreamteam\couatl\couatl.exe
Faulting module path: C:\FS2006\fsdreamteam\couatl\couatl.exe
Report Id: 5217d533-09e6-11e2-9f17-f36f5546532c
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="2012-09-29T03:32:40.000000000Z" />
    <EventRecordID>19635</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Andrew-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>couatl.exe</Data>
    <Data>2.0.0.2315</Data>
    <Data>4fe8eb03</Data>
    <Data>couatl.exe</Data>
    <Data>2.0.0.2315</Data>
    <Data>4fe8eb03</Data>
    <Data>c0000005</Data>
    <Data>0000fbf6</Data>
    <Data>1200</Data>
    <Data>01cd9df27c788518</Data>
    <Data>C:\FS2006\fsdreamteam\couatl\couatl.exe</Data>
    <Data>C:\FS2006\fsdreamteam\couatl\couatl.exe</Data>
    <Data>5217d533-09e6-11e2-9f17-f36f5546532c</Data>
  </EventData>
</Event>

There were no other errors or events related to any other applications or FSX in general. In game, if I bring up the Addon Manager menu and click on GSX, or any of the installed scenery packages, it does say Product ACTIVE for GSX, and Product ACTIVE and Installed for the scenery.

Thanks Umberto!
Andrew

[virtuali]

This kind of problem has never reported before so, it's surely something unusual in your system.

Try to remove the %APPDATA%\Virtuali folder, and see if it changes something, a wrong/corrupted file there might cause a crash.

[The Dispatcher]

Hi Umberto,

Thanks for the quick reply. I went ahead and uninstalled all of my FSDT addons, deleted the Virtuali folder in my APPDATA folder, and re-installed only GSX. After launching FSX, I selected an airport (KLAX) and still got the Couatl crash/error. Here is the latest log file - can you provide some insight about what exactly this error log is reporting so I can troubleshoot other areas of my PC?

Some other things I've tried include converting my entire FSX directory tree to a non-read only format, updating VC++ Runtime and manually updating the Addon Manager via the download links on the website.

My PC is a dedicated FSX system with Windows 7 X64, up to date with the latest Microsoft Update service packs, FSX SP2, and no anti-virus software installed. I ran two independent web based virus scanners, and both came up clean.

Log Name:      Application
Source:        Application Error
Date:          9/30/2012 4:55:26 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Andrew-PC
Description:
Faulting application name: couatl.exe, version: 2.0.0.2315, time stamp: 0x4fe8eb03
Faulting module name: couatl.exe, version: 2.0.0.2315, time stamp: 0x4fe8eb03
Exception code: 0xc0000005
Fault offset: 0x0000fbf6
Faulting process id: 0x12b0
Faulting application start time: 0x01cd9efa0ad04791
Faulting application path: C:\FS2006\fsdreamteam\couatl\couatl.exe
Faulting module path: C:\FS2006\fsdreamteam\couatl\couatl.exe
Report Id: 57097624-0aed-11e2-9239-e088eac33f27
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="2012-09-30T10:55:26.000000000Z" />
    <EventRecordID>19746</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Andrew-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>couatl.exe</Data>
    <Data>2.0.0.2315</Data>
    <Data>4fe8eb03</Data>
    <Data>couatl.exe</Data>
    <Data>2.0.0.2315</Data>
    <Data>4fe8eb03</Data>
    <Data>c0000005</Data>
    <Data>0000fbf6</Data>
    <Data>12b0</Data>
    <Data>01cd9efa0ad04791</Data>
    <Data>C:\FS2006\fsdreamteam\couatl\couatl.exe</Data>
    <Data>C:\FS2006\fsdreamteam\couatl\couatl.exe</Data>
    <Data>57097624-0aed-11e2-9239-e088eac33f27</Data>
  </EventData>
</Event>

Thanks!
Andrew

[virtuali]

Some other things I've tried include converting my entire FSX directory tree to a non-read only format

This is not necessary, all our software is fully UAC and Windows Vista/7 compliant so, it never tries to write into the FSX folder, every write is only made using the correct %APPDATA% folders so, if THESE have a permission problems, there might be issues.

Try to create a new user account, and install GSX into that one, run FSX into that one and see if it makes any difference.


You can also activate a log, to see what's happening: open the Notepad and type the following on a new blank file:

logFile=couatl.log

(please note logFile is written beginning with a lower case l and a capital F )

Save the file as couatl.ini in the FSX\fsdreamteam\couatl folder, so it stays at the same level of the couatl.exe and try launching FSX and see if a Couatl.LOG file has been created in the FSX\fsdreamteam\couatl folder and post its content.

[The Dispatcher]

Hi Umberto,

Here is the log file contents. I'll go create a new user account now, and see if the same thing happens. Thanks!

couatl v2.0 (build 2315)
log started on Sun Sep 30 07:06:31 2012

connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 17 AddOn(s)
Loading addon ZurichX
Addon ZurichX not installed or missing one or more files, skipping
Loading addon OHareX
Addon OHareX loaded
Loading addon JFK
Addon JFK loaded
Loading addon XPOI
Addon XPOI not installed or missing one or more files, skipping
Loading addon LSGG
Addon LSGG not installed or missing one or more files, skipping
Loading addon KLAS
Addon KLAS loaded
Loading addon KFLL
Addon KFLL loaded
Loading addon PHNL
Addon PHNL loaded
Loading addon KDFW
Addon KDFW loaded
Loading addon HAWAII1
Addon HAWAII1 not installed or missing one or more files, skipping
Loading addon HAWAII2
Addon HAWAII2 not installed or missing one or more files, skipping
Loading addon KLAX
Addon KLAX loaded
Loading addon ParkMe
Addon ParkMe not installed or missing one or more files, skipping
Loading addon GSX
Initializing audio...
Available devices:
  Generic Software on Speakers (Realtek High Definition Audio)
  Generic Software on Realtek Digital Output (Realtek High Definition Audio)
  Generic Software on Realtek Digital Output(Optical) (Realtek High Definition Audio)
  Generic Software on Speakers (4- Plantronics Wireless Audio)
  Generic Software on Realtek HD Audio 2nd output (Realtek High Definition Audio)
Created OpenAL device: Generic Software on Speakers (Realtek High Definition Audio)

Device info:
   Major version: 1
   Minor version: 1
   Frequency: 44100
   Refresh: 40
   Sync: 0
   Mono sources: 255
   Stereo sources: 1
   Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_EFX

Context info:
   Vendor: Creative Labs Inc.
   Version: 1.1
   Renderer: Software
   Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE

Using EFX 1.0 extension, with 1 auxiliary send(s)
Using EAX reverb
Current directory is C:/FS2006
Looking for scenery.cfg in C:/ProgramData/Microsoft/FSX/scenery.cfg
  using Scenery/World (layer 1)
  using Scenery/BASE (layer 2)
  using Scenery/0000 (layer 3)
  using Scenery/0001 (layer 4)
  using Scenery/0002 (layer 5)
  using Scenery/0003 (layer 6)
  using Scenery/0004 (layer 7)
  using Scenery/0005 (layer
  using Scenery/0006 (layer 9)
  using Scenery/0007 (layer 10)
  using Scenery/0100 (layer 11)
  using Scenery/0101 (layer 12)
  using Scenery/0102 (layer 13)
  using Scenery/0103 (layer 14)
  using Scenery/0104 (layer 15)
  using Scenery/0105 (layer 16)
  using Scenery/0106 (layer 17)
  using Scenery/0107 (layer 18)
  using Scenery/0200 (layer 19)
  using Scenery/0201 (layer 20)
  using Scenery/0202 (layer 21)
  using Scenery/0203 (layer 22)
  using Scenery/0204 (layer 23)
  using Scenery/0205 (layer 24)
  using Scenery/0206 (layer 25)
  using Scenery/0207 (layer 26)
  using Scenery/0300 (layer 27)
  using Scenery/0301 (layer 28)
  using Scenery/0302 (layer 29)
  using Scenery/0303 (layer 30)
  using Scenery/0304 (layer 31)
  using Scenery/0305 (layer 32)
  using Scenery/0306 (layer 33)
  using Scenery/0307 (layer 34)
  using Scenery/0400 (layer 35)
  using Scenery/0401 (layer 36)
  using Scenery/0402 (layer 37)
  using Scenery/0403 (layer 38)
  using Scenery/0404 (layer 39)
  using Scenery/0405 (layer 40)
  using Scenery/0406 (layer 41)
  using Scenery/0407 (layer 42)
  using Scenery/0500 (layer 43)
  using Scenery/0501 (layer 44)
  using Scenery/0502 (layer 45)
  using Scenery/0503 (layer 46)
  using Scenery/0504 (layer 47)
  using Scenery/0505 (layer 48)
  using Scenery/0506 (layer 49)
  using Scenery/0507 (layer 50)
  using Scenery/0600 (layer 51)
  using Scenery/0601 (layer 52)
  using Scenery/0602 (layer 53)
  using Scenery/0603 (layer 54)
  using Scenery/0604 (layer 55)
  using Scenery/0605 (layer 56)
  using Scenery/0606 (layer 57)
  using Scenery/0607 (layer 58)
  using Scenery/0700 (layer 59)
  using Scenery/0701 (layer 60)
  using Scenery/0702 (layer 61)
  using Scenery/0703 (layer 62)
  using Scenery/0704 (layer 63)
  using Scenery/0705 (layer 64)
  using Scenery/0706 (layer 65)
  using Scenery/0707 (layer 66)
  using Scenery/0800 (layer 67)
  using Scenery/0801 (layer 68)
  using Scenery/0802 (layer 69)
  using Scenery/0803 (layer 70)
  using Scenery/0804 (layer 71)
  using Scenery/0805 (layer 72)
  using Scenery/0806 (layer 73)
  using Scenery/0807 (layer 74)
  using Scenery/0900 (layer 75)
  using Scenery/0901 (layer 76)
  using Scenery/0902 (layer 77)
  using Scenery/0903 (layer 78)
  using Scenery/0904 (layer 79)
  using Scenery/0905 (layer 80)
  using Scenery/0906 (layer 81)
  using Scenery/0907 (layer 82)
  using Scenery/1000 (layer 83)
  using Scenery/1001 (layer 84)
  using Scenery/1002 (layer 85)
  using Scenery/1003 (layer 86)
  using Scenery/1004 (layer 87)
  using Scenery/1005 (layer 88)
  using Scenery/1006 (layer 89)
  using Scenery/1007 (layer 90)
  using Scenery/1100 (layer 91)
  using Scenery/1101 (layer 92)
  using Scenery/1102 (layer 93)
  using Scenery/1103 (layer 94)
  using Scenery/1104 (layer 95)
  using Scenery/1105 (layer 96)
  using Scenery/1106 (layer 97)
  using Scenery/1107 (layer 98)
  using Scenery/AFRI (layer 99)
  using Scenery/ASIA (layer 100)
  using Scenery/AUST (layer 101)
  using Scenery/EURE (layer 102)
  using Scenery/EURW (layer 103)
  using Scenery/NAMC (layer 104)
  using Scenery/NAME (layer 105)
  using Scenery/NAMW (layer 106)
  using Scenery/OCEN (layer 107)
  using Scenery/SAME (layer 108)
  using Scenery/Cities/Oshkosh (layer 109)
  using Scenery/Cities/StMaarten (layer 110)
  using Scenery/Cities/Rio (layer 111)
  using Scenery/Cities/LasVegas (layer 112)
  using Scenery/Global (layer 113)
  using Scenery/Props (layer 114)
  using Addon Scenery (layer 115)
  using Addon Scenery/Bellingham (layer 116)
  using Addon Scenery/Oakland (layer 117)
  using Addon Scenery/Palm Springs (layer 118)
  using Addon Scenery/Seattle (layer 119)
  using Addon Scenery/Portland (layer 120)
  using aerosoft/Anchorage-Terrain (layer 121)
  using aerosoft/Anchorage-Airport (layer 122)
  using C:/FS2006/PacSim/Marshall Islands (layer 123)
  using PacSim/Kosrae International (layer 124)
  using Addon Scenery/Barcelona (layer 125)
  using Addon Scenery/Grand Forks (layer 126)
  using Aerosoft/Madrid Barajas 2008 (layer 127)
  using aerosoft/Iceland X/Iceland X - priority 2 (layer 128)
  using aerosoft/Iceland X/Iceland X - priority 1 (layer 129)
  using Addon Scenery/Iqualuit (layer 130)
  using Addon Scenery/St. John's (layer 131)
  using Addon Scenery/Ankara (layer 132)
  using Aerosoft/Tahiti X (Base) (layer 133)
  using Aerosoft/Tahiti X (layer 134)
  using Addon Scenery/Nauru (layer 135)
  using Addon Scenery/Nadi (layer 136)
  using Addon Scenery/Pago Pago (layer 137)
  using Addon Scenery/Manilla/Buildings (layer 138)
  using Addon Scenery/Manilla (layer 139)
  using Addon Scenery/Midway Island (layer 140)
  using Addon Scenery/Guam (layer 141)
  using Addon Scenery/Salt Lake City (layer 143)
  using Addon Scenery/Denver (layer 144)
  using Addon Scenery/KelownaX (layer 145)
  using aerosoft/Keflavik X (layer 146)
  using C:/FS2006/SimMarket/Latin VFR MHTG FSX (layer 147)
  using Addon Scenery/San Diego (layer 148)
  using Scenery/UtExcl (layer 149)
  using Addon Scenery/Milan (layer 150)
  using Addon Scenery/Phoenix (layer 151)
  using Addon Scenery/Calgary (layer 152)
  using TropicalSim/TNCAx (layer 153)
  using TropicalSim/TNCCx (layer 154)
  using TropicalSim/TSim_X (layer 155)
  using Aerosoft/AES (layer 156)
  using Scenery/UtLcVeg (layer 157)
  using Scenery/UtAkRoad (layer 158)
  using Scenery/UtAkRail (layer 159)
  using Scenery/UtAkWater (layer 160)
  using Scenery/UtAkCities (layer 161)
  using Scenery/UtAkMesh (layer 162)
  using Addon Scenery/Colorado Springs (layer 163)
  using Addon Scenery/Hayden (layer 164)
  using Addon Scenery/San Jose Del Cabo (layer 165)
  using Addon Scenery/Macau (layer 166)
  using Addon Scenery/Orange County (layer 167)
  using Addon Scenery/Long Beach (layer 168)
  using Addon Scenery/San Antonio (layer 169)
  using Addon Scenery/Buffalo (layer 170)
  using FsDreamTeam/JFK (layer 171)
  using FsDreamTeam/KLAS (layer 172)
  using FsDreamTeam/KFLL (layer 173)
  using FsDreamTeam/KLAX_V2 (layer 174)
  using FsDreamTeam/PHOG (layer 175)
  using FsDreamTeam/PHKO (layer 176)
  using FsDreamTeam/PHLI (layer 177)
  using FsDreamTeam/PHTO (layer 178)
  using FsDreamTeam/PHNL (layer 179)
  using FsDreamTeam/kdfw (layer 180)
  using FsDreamTeam/OHareX (layer 181)
  using FlightBeam/KSFO (layer 182)
  using Addon Scenery/Omaha (layer 183)
  using Addon Scenery/Detroit (layer 184)
  using Addon Scenery/Mexico City (layer 185)
  using Addon Scenery/Burbank (layer 186)
  using Addon Scenery/St. Louis (layer 187)
  using Addon Scenery/Kansas City (layer 188)
  using Addon Scenery/Vancouver (layer 189)
  using C:/FS2006/Addon Scenery/FlyTampa-Tampa/ (layer 190)
  using Addon Scenery/Reno (layer 191)
  using Addon Scenery/Austin (layer 192)
  using Addon Scenery/Sacramento (layer 193)
  using ORBX/FTX_NA/FTX_NA_PNW08_CUSTOM (layer 194)
  using ORBX/FTX_NA/FTX_NA_PNW07_MESH (layer 195)
  using ORBX/FTX_NA/FTX_NA_PNW06_CVX (layer 196)
  using ORBX/FTX_NA/FTX_NA_PNW05_SCENERY (layer 197)
  using ORBX/FTX_NA/FTX_NA_NRM08_CUSTOM (layer 198)
  using ORBX/FTX_NA/FTX_NA_NRM07_MESH (layer 199)
  using ORBX/FTX_NA/FTX_NA_NRM06_CVX (layer 200)
  using ORBX/FTX_NA/FTX_NA_NRM05_SCENERY (layer 201)
  using ORBX/FTX_NA/FTX_NA_CRM08_CUSTOM (layer 202)
  using ORBX/FTX_NA/FTX_NA_CRM07_MESH (layer 203)
  using ORBX/FTX_NA/FTX_NA_CRM06_CVX (layer 204)
  using ORBX/FTX_NA/FTX_NA_CRM05_SCENERY (layer 205)
  using ORBX/FTX_NA/FTX_AA_KJAC (layer 206)
  using ORBX/FTX_AU/FTXAA_YBCS (layer 207)
  using ORBX/FTX_AU/FTXAA_ORBXLIBS (layer 208)
  using FlightBeam/KPHX (layer 209)
  using C:/FS2006/SimMarket/Nauru International (layer 210)
Airport cache not valid: file meta.txt not found or malformed
Regenerating airport cache, looking for scenery files under C:/FS2006/
Worker thread started
Addon GSX loaded
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping
Loading addon KSFO
Addon KSFO loaded
Loading addon KPHX
Addon KPHX loaded
Starting system monitors
SharedMemInterface connected

[The Dispatcher]

Any ideas based on this log?

Thanks!
Andrew

[virtuali]

The only thing not usual, is the message about the cache not valid, try to reset the FSX scenery cache, by removing the C:\ProgramData\Microsoft\FSX\SceneryIndexes folder.

[The Dispatcher]

Hi Umberto,

Thanks for the quick reply. After deleting the SceneryIndexes folder, GSX no longer crashes Couatl.exe. But now it seems to get stuck at "Regenerating Airport Cache - (20%)" and will not go past there. I left it for 20 minutes, and it's still stuck at that same spot. Sorry to be a pain, but do you have any other thoughts?

Thanks again,
Andrew

[virtuali]

But now it seems to get stuck at "Regenerating Airport Cache - (20%)" and will not go past there. I left it for 20 minutes, and it's still stuck at that same spot

Are you sure it was stuck there ? That message doesn't stay on screen up to 100%, it will only stay for a few seconds, and if you want to check the current progress, you'll have to press CTRL+F12 again but, chances are if you left it for several minutes, it was already finished.

If the cache couldn't be regenerated completely, perhaps you have a corrupted AFCAD somewhere, which is blocking the process. You might try in this case to disable all your addon airports in the Scenery Library, then re-enable them ONE AT A TIME, until you see GSX stuck again, so you could identify at least the folder/scenery that contains the problem file.

[808CruzControl]

Heads up.

I was having problems with my Catalyst Control Center program. It would never start (and still never starts). It has something to do with a driver i guess but anyways, i updated the CCC because I was having flickering problems on my desktop. I then installed the newest drivers for my gpu and I just noticed that GSX is now working. I can finally open fsx with out having a couatl error and I can also see the couatl menu.

So check to see if not, install the latest drivers for your GPU (from their website) maybe?

edit: Okay I only had GSX installed. When I saw that it started to work, I installed the FSDT Honolulu addon. I opened up FSX and i got the error again....... 

[virtuali]

edit: Okay I only had GSX installed. When I saw that it started to work, I installed the FSDT Honolulu addon. I opened up FSX and i got the error again....... 

This simply can't be, since the Couatl.exe which is downloaded by the PHNL installer is exactly the same (same url and location) of the Couatl.exe downloaded by GSX.

Your system problem (probably a Windows C++ runtime missing/corrupted) that affected the Catalyst control center, is affecting Couatl.exe too. Try to install GSX after everything else OR try to install the Stand-Alone Addon Manager after everything else.

[808CruzControl]

Hey Umberto

Well GSX WORKED without any scenery addon from FSDT. Once installed FSDT Honolulu i got the error. I did try installing GSX before all other FSDT addons and it didnt help. I also downloaded and installed the standalone and nothing. I cleared all C+++ and installed them. Before i installed GSX (when it worked) i deleted the FSDT folder from the FSX folder. GSX was then the only program I installed then came the FSDT Honolulu and thats when i got the error so now im stuck again. I noticed that after i got the error, building textures were missing. I could only see the jetways, ground textures, and the black areas that the buildings go on.
 

[Eisbahn]

I think you should read the replies from Umberto exactly.
He has said many times, and also in the reply above:
"Try to install GSX after everything else OR try to install the Stand-Alone Addon Manager after everything else"