Products Support > GSX Support FSX/P3D
couatl scripting engine has encountered when calling the gsx service **SOLVED**
virtuali:
--- Quote from: Captain Kevin on January 24, 2022, 01:56:37 pm ---Umberto, you said that to somebody else who chimed in. The guy who said his problem is still not resolved actually did post his couatl.log in his post.
--- End quote ---
Yes, but that log wasn't made during a session in which the error occurred. It must have been reset on a subsequent session, because there's no error there.
virtuali:
--- Quote from: huyvipasna on January 19, 2022, 09:08:29 pm ---this is the couatl log file. how to fix this error?
--- End quote ---
Sorry for the mixup, I was replying to somebody else. Your log wasn't made during a session in which the error occurred. It must have been reset on a subsequent session, because there's no error there.
Please be sure you don't restart the sim (or reply Yes to restart Couatl ) after you see the error, if you do that, the log will be overwritten.
huyvipasna:
--- Quote from: virtuali on January 24, 2022, 02:03:54 pm ---
--- Quote from: huyvipasna on January 19, 2022, 09:08:29 pm ---this is the couatl log file. how to fix this error?
--- End quote ---
Sorry for the mixup, I was replying to somebody else. Your log wasn't made during a session in which the error occurred. It must have been reset on a subsequent session, because there's no error there.
Please be sure you don't restart the sim (or reply Yes to restart Couatl ) after you see the error, if you do that, the log will be overwritten.
--- End quote ---
this is the latest log file, hope you can figure out how to fix this for me
virtuali:
Your error indicates ths simulator can't find an object ( FSDT_SODE_JW_TB_2_5_LOGO_PARIS) that is surely included with GSX so, if the sim can't see it, it might because it's missing from the add-on.xml
Of course, it's not normal paths for Simobjects would be missing from the add-on.xml, since BOTH our installer AND the Live Update will surely add it if it's missing.
This might be due to one of the following:
- Your antivirus is blocking the updater from updating itself, so you are still running an old updater, one that won't add the extra P3DV5 object path, because it was made before we add these objects. Configure the antivirus to exclude the WHOLE Addon Manager folder, and start the FSDT Live Update again.
- You are starting the update with Couatl_Updater2.exe manually, instead of starting it from the Desktop icon, which points to Couatl_Updater.exe. This will also prevent the updater to "update itself", that's why we have an icon, so you won't start the wrong program.
- You are using a 3rd party utility that handles add-on.xml files, and it's restoring from a backup, one that was made before our updater added the path for the new objects. If such utility has a backup feature, you must backup AFTER you let the FSDT Live Update to add the path to the add-on.xml, otherwise you'll keep restoring an outdated version.
- There's some problem (permissions or antivirus ) with accessing the Documents\Prepar3d V5 Add-ons folder, which prevent the Live Update to update the add-on.xml there.
- An external utility that handles add-on.xml files has corrupted our add-on.xml, preventing our updater to update it.
ska133:
Okay, so basically, I'm stuck since few days with the same error, I tried what Umberto suggested : add an exception on the antivirus (which actually is only windows defender on my computer) then update, or reinstalling via the full updater. I even tried both updating then reinstalling with defender deactivated, still got that error, I'm out of solutions. So I'll post that log with the error generated from yesterday evening. I hope we can find a solution because I can't use any of GSX/couatl service atm.
Regards
Lilian
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version