Mike
  • Mike
  • 51.2% (Neutral)
  • Nestling Topic Starter
2007-03-16T08:31:51Z
When exiting RD Tabs, I often get an error stating the following:

"RD Tabs encountered an unexpected error while sending the previous error report. This is pretty much as bad as it can get, wouldn't you say? If you could report this occurance to the author through the Avian Waves forums that would help tremendously! I apologize for this problem. Thank you."

This problem did begin occuring until I upgraded to the current version of 1.1.2


Timothy
  • Timothy
  • 100% (Exalted)
  • Flock Leader
2007-03-16T09:53:40Z
Thanks for the notice!

If it only happens during application exit, then it's probably this...

There are a few instances where the RDP control does exit as fast as the .Net framework would like and it generates certain exceptions. I thought I caught them all, but I guess not! 🙂 In this case, RD Tabs forces a termination and everything cleans up correctly. I added some new error reporting code in the 1.1.2 update to trap more critical problems for the error reporting agent and apparently the error reporter is not correctly ignoring the "forced termination" error, so it's failing to send an error report (because the application is basically exited at this point and it can't instantiate the error reporter) and pops up that notice.

Sorry about that! I'll comb through that code and see about a 1.1.3 which will relieve that.

Just to confirm, this only happens on application exit, right? And does it happen every time or intermittently?
Mike
  • Mike
  • 51.2% (Neutral)
  • Nestling Topic Starter
2007-03-19T17:20:38Z
Yes, this problem only occurs on application exit and it occurs intermittently.
full film