FSDreamTeam forum

Products Support => GSX Support FSX/P3D => Topic started by: NGX12 on September 26, 2013, 08:37:00 am

Title: GSX Error - No Traceback Available **SOLVED**
Post by: NGX12 on September 26, 2013, 08:37:00 am

Hi there, I have been getting an ERROR with GSX on installation. This is what the error log shows:
couatl v2.0 (build 2354)
panic log started on Thu Sep 26 09:54:03 2013

problem raised by addon <no traceback available>TaskletExit: ()

couatl v2.0 (build 2354)
panic log started on Thu Sep 26 09:54:03 2013

problem raised by addon <no traceback available>TaskletExit: ()

After clicking the close button of the error, it reappears whenever anything is selected in FS.

Any Ideas?

Title: Re: GSX Error
Post by: virtuali on September 26, 2013, 11:15:40 am

Does it happen with any airplane ? Do you use a custom airport configuration file ?

Title: Re: GSX Error
Post by: NGX12 on September 27, 2013, 12:26:02 am

This error occurs on start-up of FSX. You can't do anything since the error window pops up every time.

Title: Re: GSX Error
Post by: virtuali on September 27, 2013, 01:20:10 pm

Quote from: NGX12 on September 27, 2013, 12:26:02 am

This error occurs on start-up of FSX. You can't do anything since the error window pops up every time.

Try to reset the GSX preferences, by removing this file:

%APPDATA%\Virtuali\Couatladdons.ini

Title: Re: GSX Error
Post by: NGX12 on September 28, 2013, 12:37:30 am

The problem still persists. I can't think of any add-on causing this.

Title: Re: GSX Error
Post by: virtuali on September 28, 2013, 02:57:44 pm

Another user that had the same problem:

http://www.fsdreamteam.com/forum/index.php?topic=9090.msg72836#msg72836

Said it was fixed by reinstalling FSX so, it must be something caused by another add-on, which we still haven't identified.

Title: Re: GSX Error
Post by: NGX12 on September 29, 2013, 01:05:03 am

Ok, the only thing I am worried about is the register part of the installation since the servers are down? Thanks for the Support anyway :)

Title: Re: GSX Error
Post by: virtuali on September 29, 2013, 12:21:36 pm

Quote from: NGX12 on September 29, 2013, 01:05:03 am

Ok, the only thing I am worried about is the register part of the installation since the servers are down?

Why you think servers are down ? They have been for a week, but it has been fixed since a couple of week already.

Title: Re: GSX Error
Post by: NGX12 on September 30, 2013, 03:43:38 am

Oh, I thought the FSX registration servers were cut off? I think you may have thought I meant the FSDT Servers. I've seen people post errors with registration..

Title: Re: GSX Error
Post by: NGX12 on October 03, 2013, 10:35:06 am

I have fixed the problem!!

For anyone wondering, I deleted my BGLMANX.DLL and the corresponding .DAT file and it worked perfectly!http://i1264.photobucket.com/albums/jj487/AlexFS9/fsx-2013-10-03-18-31-48-96.png~original (http://i1264.photobucket.com/albums/jj487/AlexFS9/fsx-2013-10-03-18-31-48-96.png~original)

Title: Re: GSX Error
Post by: virtuali on October 03, 2013, 05:05:58 pm

Quote from: NGX12 on October 03, 2013, 10:35:06 am

For anyone wondering, I deleted my BGLMANX.DLL and the corresponding .DAT file and it worked perfectly!

That's not possible. First, because without a bglmanx.dll running (and of course its .dat files) GSX won't even start so, you surely haven't done that.

If, instead, you meant that you did that, but then you reinstalled GSX and it started to work, the problem is likely that you had another external program (like an antivirus) which *blocked* the installation of the correct bglmanx.dll and bglmanx.dat files that comes with the GSX installers (and are download online), so after you manually removed them, the installer could complete.

The interference from a security-related product like an antivirus or similar, could also explain why you reported errors accessing the activation servers, which have been fixed since a couple of week by now.

Title: Re: GSX Error - No Traceback Available [FIXED]
Post by: NGX12 on October 03, 2013, 11:53:11 pm

Yes, that is what I meant. I just worded it horribly.