Couatl Script Engine error **SOLVED, caused by Lenovo software **

[Daveb]

I am currently looking into purchasing the GSX for FSX but i have the following issue with the trial version.

When I start FSX and get to the Free flight screen the following maessage appears " The Couatl Script Engine has encountered an unrecoverable error and will be restarted. Details can be found at (APPDATA path). Please download the latest stand alone app manager"

I can clear this message and set up any A/c at one of your airports and the GSX starts to load unload etc, but every 30 seconds or so the above message re appears and i then have to re statrt the process.

I am running Windows 7 on I3 core 2.20GHz with 8 gig Ram usng Nvida Geforce card, I have no issues at all with FSX and runs very smoothly.  The only message in the error folder is

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:04:51 2013
Executable integrity compromised

Any ideas / help please, would love to purchase this product

[virtuali]

When I start FSX and get to the Free flight screen the following maessage appears " The Couatl Script Engine has encountered an unrecoverable error and will be restarted. Details can be found at (APPDATA path). Please download the latest stand alone app manager"

That wasn't everything the message said. The most important part was the indication that the Couatl.err file contains details about the error. Please post its content so we can undertand what's the problem really is.

[Daveb]

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:40:34 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:41:12 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:41:51 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:42:30 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:43:08 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:44:12 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:44:49 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:45:27 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:46:06 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:46:44 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:47:22 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:47:59 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:48:38 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:55:24 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:55:58 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:56:33 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:57:09 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:57:43 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:58:17 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:58:52 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:59:26 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:00:00 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:00:55 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:01:45 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:02:20 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:02:54 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:03:28 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:04:03 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:04:51 2013
Executable integrity compromised


That's every thing in the file

[virtuali]

This has been discussed already on the forum, it's a problem caused by another product which is attaching to all running executables. As of today, we know about these two:

- The free ATI Tray Tools tweaker, if the "automatic over clock" option is turned on.

- The Lenovo Power management program.

These are just two examples we know of, there might be other similar products out there we don't know yet. Other than that, it could be a real virus.

[Daveb]

I found the file I think you are after .  My laptop is Lenovo but not sure what you mean with the Tray bit

withcouatl v2.0 (build 2348)
log started on Fri Feb 22 16:35:31 2013

connecting to SimConnect...
connected to FSX
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 18 AddOn(s)
Loading addon ZurichX
Addon ZurichX not installed or missing one or more files, skipping
Loading addon OHareX
Addon OHareX not installed or missing one or more files, skipping
Loading addon JFK
Addon JFK not installed or missing one or more files, skipping
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 not installed or missing one or more files, skipping
Loading addon KFLL
Addon KFLL not installed or missing one or more files, skipping
Loading addon PHNL
Addon PHNL not installed or missing one or more files, skipping
Loading addon KDFW
Addon KDFW not installed or missing one or more files, skipping
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 not installed or missing one or more files, skipping
Loading addon ParkMe
Addon ParkMe loaded
Loading addon GSX
Initializing audio...
Available devices:
  Generic Software on Speakers (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:/Program Files (x86)/Microsoft Games/Microsoft Flight Simulator X
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)
Airport cache loaded
Addon GSX loaded
Loading addon CYVR
Addon CYVR not installed or missing one or more files, skipping
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping
Loading addon KSFO
Addon KSFO not installed or missing one or more files, skipping
Loading addon KPHX
Addon KPHX not installed or missing one or more files, skipping
Starting system monitors
Current locale is English_United Kingdom.1252
SharedMemInterface connected
GSX is in trial mode (state=0, activation=-25006)
Loading aircraft data from Airplanes\B737_800
aircraftDb.py provides aircraft data with priority 2
Using aircraft data from aircraftDb.py
Found gsx.cfg file at C:\Users\Dave Butterworth\AppData\Roaming\Virtuali\Airplanes\B737_800\gsx.cfg
Loading airport EDDM from C:/Program Files (x86)/Microsoft Games/Microsoft Flight Simulator X/Scenery/0601/scenery/APX51140.bgl
Using airport customization from GSX.airports.eddm
 the following text

[virtuali]

Now your Couatl.LOG file doesn't show anything wrong. Are you still getting an error ? If yes, as explained before, you should post your Couatl.ERR file, not the LOG file.

[Daveb]

Yes still getting exactly the same problem, below is the file you needed, it looks the same as before to me. Very frustrating issue, betting it is something minor.




couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:40:34 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:41:12 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:41:51 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:42:30 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:43:08 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:44:12 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:44:49 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:45:27 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:46:06 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:46:44 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:47:22 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:47:59 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:48:38 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:55:24 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:55:58 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:56:33 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:57:09 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:57:43 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:58:17 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:58:52 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 21:59:26 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:00:00 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:00:55 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:01:45 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:02:20 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:02:54 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:03:28 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:04:03 2013
Executable integrity compromised

couatl v2.0 (build 2346)
panic log started on Wed Feb 20 22:04:51 2013
Executable integrity compromised

[virtuali]

Yes still getting exactly the same problem, below is the file you needed, it looks the same as before to me. Very frustrating issue, betting it is something minor.

No, it doesn't. Unless you never ran FSX for two days, it doesn't shows any errors past Feb. 20th. And, all errors are coming from version 2337 and 2346, but your Couatl.LOG shows the version you are running now is 2348, which is the most current one.

So, your files shows that in the session that produced the Couatl.LOG file, there wasn't any new errors on the Couatl.ERR file.

But as I've said, it's a problem caused by another product which is attaching to all running executables. As of today, we know about these two:

- The free ATI Tray Tools tweaker, if the "automatic over clock" option is turned on.

- The Lenovo Power management program.

These are just two examples we know of, there might be other similar products out there we don't know yet. Other than that, it could be a real virus so, the only way to fix this is to disable the offending product.

[Daveb]

Ok your the expert, I have ran FSX every day, including 5 mins before this post and have got the same issue, The log shows exactly what i posted last time so no idea why it does not show todays date and only shows 2337 & 2346 builds despite running 2348 build. I can assure you there is no Virus on my system FACT.

So if you know there are two issues then why cant you give a staright answer to the problem, Like what do I need to do, how do I dissable the offending product? I dont to my knowledge have ATI tray. So if you cant answer that then I can pruchase another product, that would be a shame because it looks great. But your attitude to a potentail customer stinks. Please either answer the question.

[virtuali]

no idea why it does not show todays date and only shows 2337 & 2346 builds despite running 2348 build.

The Couatl.err file is historical, so it's not cleared after each FSX session so, it's showing when you HAD the error, in previous dates when running the previous version of the program. If the Couatl.LOG shows you are running the current build, and no entry with this one has been added the Couatl.err file, it means that error is not happening anymore.

So if you know there are two issues then why cant you give a staright answer to the problem

I obviously gave you a "straight" answer, which those two issues are the one we KNOW of, but that doesn't mean there might be other products which we DO NOT know, which are causing the same problem.

, Like what do I need to do, how do I dissable the offending product? I dont to my knowledge have ATI tray.

As I've said, the two offending products we know of are the ATI Tray Tools AND the Lenovo Power management software. If you don't have the ATI Tray Tools that excludes ONE possible cause, but since you said your Laptop IS a Lenovo, it's very likely you have that software installed.

Of course, how to disable it should be indicated in the documentation that comes with your computer.

But your attitude to a potentail customer stinks. Please either answer the question.

You have been answered several times, and with the utmost precision, which is exactly how the facts are: that we KNOW of two possible causes, one of them is the Lenovo software, you HAVE a Lenovo laptop, I'd says that everything you needed to know to start fixing the problem, which is *caused* by the Lenovo software and you'll realize that it WILL go away, as soon as you disable it.

I don't know exactly HOW to remove/disable the Lenovo power management utility, I never seen it running, we can only rely on users reports and, as of today (just search the forum for "Lenovo" ), every user that reported it, was able to fix it by disabling it, so I guess it should be reasonably easy to do.

[Daveb]

I disagree entirely with your answer on the Couatl.err file in that the fault is there exactly as it was on previous builds, so why it is not showing I dont know, what I do know is the ERROR is still there still happening but not writing to the file for some reason.

So moving on I have disabled the power management within start up menu along with another file tray IFGS, the problem is now fixed, the programme runs lovely, really smooth and very professional.

Thanks for the pointer, but still think it would have been quicker had you given a bit more direction.

[virtuali]

I disagree entirely with your answer on the Couatl.err file in that the fault is there exactly as it was on previous builds

The answer is correct, based on the Couatl.err file you posted. Maybe you haven't posted the most updated one.

So moving on I have disabled the power management within start up menu along with another file tray IFGS, the problem is now fixed, the programme runs lovely, really smooth and very professional.

That's what I've said, right from the start. The problem was caused by an external program, as far as we know, the ones that caused this are the ATI Tray Tool and the Lenovo power management software, which is what I've indicated to check from my first reply.

Thanks for the pointer, but still think it would have been quicker had you given a bit more direction.

As I've said, I never seen that Lenovo software in action, so I don't have any idea of what option it offers to be disabled (or if it needs to be uninstalled), I only know about that issue from other users reports, which is why I've listed it as a possible cause, and it turned out to be the case.

[thomas320]

hello evrybody 

i'have bought the GSX and i flight online , when i flight not online all it's okay my GSX is very good but when i flight online i'have evry minutes a message error as that : the coualt scripting engine has encountered an unrecoverable error and will be restarted. detail can be found in
c:/.../..../.... etc.
please download and install the latest stand-alone addon manager from
http://fsdreamteam.com/sa-addon-manager.com

so please help me 

[virtuali]

detail can be found in
c:/.../..../.... etc.

This thing you omitted is the only important information about the error. Please post the content of your Couatl.err file which that message refers to.

[thomas320]

detail can be found in
c:/.../..../.... etc.

This thing you omitted is the only important information about the error. Please post the content of your Couatl.err file which that message refers to.

hello : this is my message error : couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:40:34 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:41:12 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:41:51 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:42:30 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:43:08 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:44:12 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:44:49 2013
Executable integrity compromised

couatl v2.0 (build 2337)
panic log started on Wed Feb 20 21:45:27 2013
Executable integrity compromised