Author Topic: Error  (Read 2313 times)

Magic_fubu

  • Hero Member
  • *****
  • Posts: 1035
    • View Profile
Re: Error
« Reply #15 on: January 28, 2012, 03:54:39 PM »
Glad to be of help in the matter! I know I'm that's always willing to help out in any manner needed for the betterment of the program :)
My cowboys shot down your rockets
---
If you send a request to me please send that you got me from here w/your TD name to confirm. Thanks!

jodybingo

  • Hero Member
  • *****
  • Posts: 656
    • View Profile
    • Personal Web Site
Re: Error
« Reply #16 on: January 30, 2012, 12:28:14 PM »
Corey, the error just came up again. This time, the data store was present upon start up. TD shut itself down.

Corey Cooper

  • Administrator
  • Hero Member
  • *****
  • Posts: 5381
    • View Profile
Re: Error
« Reply #17 on: January 30, 2012, 01:41:37 PM »
Which version?

jodybingo

  • Hero Member
  • *****
  • Posts: 656
    • View Profile
    • Personal Web Site
Re: Error
« Reply #18 on: January 30, 2012, 01:55:39 PM »
3.1 (I could have sworn I updated to 3.1.1)

Corey Cooper

  • Administrator
  • Hero Member
  • *****
  • Posts: 5381
    • View Profile
Re: Error
« Reply #19 on: January 30, 2012, 02:12:18 PM »
Glad to hear.  It should be fixed in 3.1.1.  I can't say for certain there isn't another path to the same error, but I certainly did track down at least one exact reason why this error occurs.

FYI, this was all a timing issue.  During the initialization process, the software kicks off a patch download.  When the active Data Store doesn't exist, it causes the warning dialog to show, which essentially "pauses" the initialization process.  When the patch finishes downloading, it expects the Settings dialog to be initialized.  Because the initialization is paused, the Settings dialog remains uninitialized, and boom we get an error.  So conceivably anything that might slow down the initialization process could cause this to happen, so long as a patch is downloaded relatively quickly.  It doesn't have to be that the active Data Store could not be found.