GSX install problem with Steam **SOLVED**

[carl42]

First I have been using all of the FSDT software for years with little or no problems. I had a recent dual install with FSX and FSX-SE with no problems.  I now use only steam version.  Deleted all prior files including steam version and then reinstalled steam only and added all FSDT including GSX and latest Addon Manager. All FSDT appeared to show up with no problem. I then installed Airbus X A318-321. Then on start up of FSX I started getting the message "FSX attempting to start "Couatl version 2.0.0.2.2.278 config entry number 1" do you want to run this program-yes or no." I then decided to re-install GSX and after reinstall I got the message "Couatl scripting engine for FSX/ESP setup unable to auto close all of applications using files that need to be up dated by setup." I have uninstalled the airbuses, addon manager, and GSX.  FSX is ok however after uninstalls but I still get the first message. I am at a lost on what to do next.  
I apologize if I am not able to explain this in better detail but would appreciate any guidance on what to do next. Maybe a complete reinstall of Steam FSX?

Added:
Deleted virtuali folder and I have recently tried to install the addon manager and still get the message"Couatl scripting engine for FSX/ESP.  Abort.

Note: (1) uninstall "GSX" , removed "Addon Mgr, and "couatl engine" products". (2) Reinstalled with no problem; however when I went to any FSDT airport fsx will lockup after receiving message about couatl problems with addon ..  Have deleted several recent scenery addons but no changes. 
   
Below is what was found in virtuali file: couatl.err, which I really don't have a clue what all that means.


   couatl v2.0 (build 2378)
panic log started on Tue Feb 03 10:15:42 2015

problem raised by engine or unspecified addonBglmanx disconnected prematurely

couatl v2.0 (build 2378)
panic log started on Wed Feb 04 17:03:19 2015

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 109, in _setPreference
  File "couatl\common\preferences.py", line 46, in writePreferencesToDisk
IOError: (13, 'Permission denied', u'C:\\Users\\Owner\\AppData\\Roaming\\Virtuali\\CouatlAddons.ini')

couatl v2.0 (build 2378)
panic log started on Wed Feb 04 17:41:12 2015

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 109, in _setPreference
  File "couatl\common\preferences.py", line 46, in writePreferencesToDisk
IOError: (13, 'Permission denied', u'C:\\Users\\Owner\\AppData\\Roaming\\Virtuali\\CouatlAddons.ini')

couatl v2.0 (build 2378)
panic log started on Wed Feb 04 17:57:53 2015

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 109, in _setPreference
  File "couatl\common\preferences.py", line 46, in writePreferencesToDisk
IOError: (13, 'Permission denied', u'C:\\Users\\Owner\\AppData\\Roaming\\Virtuali\\CouatlAddons.ini')

couatl v2.0 (build 2378)
panic log started on Wed Feb 04 18:06:55 2015

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 109, in _setPreference
  File "couatl\common\preferences.py", line 46, in writePreferencesToDisk
IOError: (13, 'Permission denied', u'C:\\Users\\Owner\\AppData\\Roaming\\Virtuali\\CouatlAddons.ini')

[carl42]

One further data point, which I wonder could this be the problem. Below is my EXE.XML.  Thanks for any help..


<?xml version="1.0" encoding="WINDOWS-1252"?>

-<SimBase.Document version="1,0" Type="Launch">

<Descr>Launch</Descr>

<Filename>EXE.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>True</Launch.ManualLoad> (should this be False not True)??


-<Launch.Addon>

<Name>Couatl</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>fsdreamteam\couatl\couatl.exe</Path>

<CommandLine>--mode=fsxse</CommandLine>  (Why mode=fsxse)??

</Launch.Addon>


-<Launch.Addon>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Name>Addon Application</Name>

<Path>C:\MyPath\Addon.exe</Path>

<CommandLine/>

<NewConsole>True</NewConsole>

</Launch.Addon>

</SimBase.Document>

[pete_auau]

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

[virtuali]

The problem with your EXE.XML file has already been linked in the above post.

The error message you see from the Log:

IOError: (13, 'Permission denied', u'C:\\Users\\Owner\\AppData\\Roaming\\Virtuali\\CouatlAddons.ini')

Seems to indicate either a permission issue in your %APPDATA% folder, or just a corrupted file on your system.

Try to manually remove the C:\\Users\\Owner\\AppData\\Roaming\\Virtuali\\CouatlAddons.ini' file first, then reinstall GSX.

[carl42]

Guys thanks for your help.  Umberto, before I got your message I deleted all the FSDT/FD software. Started fresh after deleting the Couatladdon.ini.but have not  edited my exe.dll. Also removed the couatl error file and proceeded to add a few FSDT airports and so far so good.  All are working. Will install the addon manager after completing all the installs. So far no errors are showing up.

 I do get each time starting FSX the "Do you want to start Couatl....". which I allow.  Maybe if I modify the  exe.dll as shown is the cause.?

[virtuali]

I do get each time starting FSX the "Do you want to start Couatl....". which I allow.  Maybe if I modify the  exe.dll as shown is the cause.?

Yes, the problem is the EXE.XML has a wrong (or should I say, "not normally used except for debugging" ) parameter. Not sure it's a Steam install issue, or they made it on purpose to warn you about 3rd party modules starting.

[carl42]

Umberto, I had to change one line in my exe.xml from"true" to "false" as you suggested in another post. So far all the FSDT and FD airports are working and no more problems.  Sure appreciate all the help. 

regards,