Hi there,
Dunno if any of you guys can help - my Bet Angel has suddenly stopped working.
I'm getting a fatal exception error when I try to load it along the lines of External Component has thrown an exception - Infragistics.Win.DrawUtility ... etc etc. it goes on for a while.
I've tried reinstalling BA, and the updating the .NET Framework, entirely without success. I've emailed the guys at BA, but I suspect they've gone home by now!
Has anyone else come across this error - I've not installed anything new on the PC btw, this machine is solely for trading.
Cheers all,
Russ...
Bet Angel stopped working and won't start up - arrgh!
Morning Squirtle, all,
Sorted it last night, with the very kind assistance of the good folks at BA - do they ever sleep?
Anyhow, should you come across this here's how I solved it...
I went through a few iterations of the uninstall/reinstall process - but the one that finally worked was to uninstall BA, restart, uninstall all versions of the .NET framework (I had v1, v2, and the v2 SDK, for some reason), restart, and then reinstall BA, which started by reinstalling .NET v2, restart and kick off the BA reinstall again, which just loaded your software.
Part of the problem might have been that even though BA seemed to have abended with the error message, it actually left an instance running which could only be seen in Task Manager/Processes tab. This might have been holding onto to those troublesome dll's which were causing the fatal exception error.
No criticism of BA implied here, btw, I'm sure this was a windows glitch rather than a problem with the software, which I've always found very reliable.
Cheers again for the help...
Sorted it last night, with the very kind assistance of the good folks at BA - do they ever sleep?
Anyhow, should you come across this here's how I solved it...
I went through a few iterations of the uninstall/reinstall process - but the one that finally worked was to uninstall BA, restart, uninstall all versions of the .NET framework (I had v1, v2, and the v2 SDK, for some reason), restart, and then reinstall BA, which started by reinstalling .NET v2, restart and kick off the BA reinstall again, which just loaded your software.
Part of the problem might have been that even though BA seemed to have abended with the error message, it actually left an instance running which could only be seen in Task Manager/Processes tab. This might have been holding onto to those troublesome dll's which were causing the fatal exception error.
No criticism of BA implied here, btw, I'm sure this was a windows glitch rather than a problem with the software, which I've always found very reliable.
Cheers again for the help...