Haveing issues with fsx se and couatl **SOLVED**

[Davidmf1982]

okay fsx will load fine but than i get this message about couatl has crashed and it shows me where i can get to my err log but i can not make since of it can any one help me please? I really enjoy all the add on's you guys have and would love to keep flying fsx se with this add ons here is my log

ouatl v2.0 (build 2364)
panic log started on Tue Sep 02 14:41:36 2014

problem raised by addon <unknown>Traceback (most recent call last):
  File "couatl\common\__init__.py", line 52, in checkBglmanVersion
  File "couatl\common\liveUpdate.py", line 75, in liveUpdate
  File "couatl\common\preferences.py", line 101, in _setPreference
  File "couatl\common\preferences.py", line 46, in writePreferencesToDisk
IOError: (13, 'Permission denied', u'C:\\Users\\David\\AppData\\Roaming\\Virtuali\\CouatlAddons.ini')

couatl v2.0 (build 2364)
panic log started on Tue Sep 02 14:41:59 2014

problem raised by addon <unknown>Traceback (most recent call last):
  File "couatl\common\__init__.py", line 52, in checkBglmanVersion
  File "couatl\common\liveUpdate.py", line 75, in liveUpdate
  File "couatl\common\preferences.py", line 101, in _setPreference
  File "couatl\common\preferences.py", line 46, in writePreferencesToDisk
IOError: (13, 'Permission denied', u'C:\\Users\\David\\AppData\\Roaming\\Virtuali\\CouatlAddons.ini')

couatl v2.0 (build 2364)
panic log started on Sun Nov 16 16:47:02 2014

problem raised by engine or unspecified addon
TaskletExit: ()

couatl v2.0 (build 2376)
panic log started on Sat Jan 03 11:53:32 2015

problem raised by engine or unspecified addonBglmanx disconnected prematurely

couatl v2.0 (build 2376)
panic log started on Wed Jan 14 22:04:47 2015

problem raised by engine or unspecified addonBglmanx disconnected prematurely

couatl v2.0 (build 2378)
panic log started on Sun Feb 01 16:30:40 2015

problem raised by engine or unspecified addonBglmanx disconnected prematurely

couatl v2.0 (build 2378)
panic log started on Wed Feb 18 22:47:43 2015

problem raised by engine or unspecified addonBglmanx disconnected prematurely

couatl v2.0 (build 2378)
panic log started on Thu Feb 19 18:51:58 2015

problem raised by engine or unspecified addonBglmanx disconnected prematurely

couatl v2.0 (build 2378)
panic log started on Thu Feb 19 19:50:20 2015

problem raised by engine or unspecified addonBglmanx disconnected prematurely

couatl v2.0 (build 2378)
panic log started on Sat Feb 21 11:22:59 2015

problem raised by engine or unspecified addonBglmanx disconnected prematurely

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 22:00:26 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 22:04:52 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 22:10:10 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 22:42:23 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 22:51:20 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 23:01:29 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 23:32:57 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 23:39:12 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 23:39:46 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 23:40:20 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 23:40:55 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 23:41:29 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 23:42:04 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 23:42:38 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Thu Mar 05 23:43:12 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 20:24:51 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 20:28:13 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 21:32:12 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 21:50:44 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 21:51:19 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 21:51:53 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 21:52:27 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 21:53:02 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 21:53:36 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 21:54:11 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 22:54:01 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Fri Mar 06 22:57:51 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Sat Mar 07 08:42:48 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Sat Mar 07 08:55:18 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Sat Mar 07 09:40:46 2015

problem raised by engine or unspecified addonExecutable integrity compromised

couatl v2.0 (build 2378)
panic log started on Sat Mar 07 09:46:54 2015

problem raised by engine or unspecified addonExecutable integrity compromised

[Davidmf1982]

18 views and yet no one has an answer? I thought I did but guess I was wrong is this how ever customer is treated?

[virtuali]

18 views and yet no one has an answer? I thought I did but guess I was wrong is this how ever customer is treated?

What kind of reply is this ? You posted on Saturday. Do you expect any customer support must be always available 24/7 ? Do you always work on weekends ? We USUALLY do, but not ALWAYS...

And besides, if you were hard pressed to find a solution, you could simply have searched the "addonExecutable integrity compromised" using the Search function of the forum. Just placing the "addonExecutable integrity compromised" text into the search window, would have resulted in many threads, all indicating many different causes and solutions.

There was already a thread about this a couple of days ago, confirming the problem was caused by a GeForce Experience Beta version, and reverting to the normal version fixed the issue for the user that reported it:

http://www.fsdreamteam.com/forum/index.php/topic,11656.0.html

And, there was another thread, with all the other known causes, all related to other programs that attach to every running executable in your system ( a very questionable practice )

http://www.fsdreamteam.com/forum/index.php/topic,11651.msg89491.html#msg89491

[Davidmf1982]

Sorry about the reply i had in i did unistalled CPU-Z and disabled shadow play and have manged to get in to fsx with out any problems this far. Yes I have worked jobs in my past that worked me on weekends this job im doing now i do not but i deal with kids as i drive a school bus so i was just wanting this problem fixed sorry if i came out to be a bit rude was just hating to see fsx keep crashing on me and not working as i use fsx for enjoyment and to get away from the world for a bit. So hopefully with doing both of that I will not have a problem thanks for pointing me in the right way to getting this fixed.