Thunderbird freezes because of a bad data entry in Lightening Calendar.
I added a date to Lightening Calendar, and instead of entering 2017 as the year, I accidentally entered 20170 and didn't catch it. I added the date, and Thunderbird froze up. I could see the bad date, but couldn't change it. Couldn't do anything. So I went to Task Manager and closed Thunderbird. Now, when I reopen Thunderbird, it immediately refreezes. It is still trying to deal with the bad date, and there seems to be no error trapping. I could be wrong about the diagnosis, as I'm not a computer guru, but the symptoms I have described are real. Thunderbird is totally disfunctional now, because of a misplaced 0; and I have no idea how to fix it.
Chosen solution
OKAY -- Problem solved. I did it myself. I went back into the Lightening Calendar database file (located at: C:\Users\UserName\AppData\Roaming\Thunderbird\Profiles\dtbp4obn.default\calendar-data\local.SQLite) and searched for another record with the same title as the one I deleted before. There was a second one. Apparently the Calendar tried to make a second record instead of updating the one I was working on. This second record was the one that was corrupted. I deleted it, and restored the database (renamed it from .bak file), and Thunderbird started up and the Calendar worked again.
Not sure that Lightening has adequate error checking, because a single year mistake (20170 instead of 2017) broke the calendar program and froze up Thunderbird.
I love T'Bird, and I use Lightening Calendar exclusively (having abandoned Microsoft Outlook). But this even had me truly frightened. I would hate to lose all my calendar entries!
Read this answer in context 👍 0All Replies (5)
Is this a local calendar or a network one, i.e. on a server?
To my knowledge Lightening Calendar is stored on my PC.
Okay, I located the calendar database on my PC. it is a SQLite file. I changed this database file's extension to .bak, and restarted Thunderbird. Problem with Thunderbird solved! But, I have lost all my data from my calendar. So I found a SQLite browser, and found the bad entry, and deleted it. Then I deleted the new database file and removed the .bak extension from the old database file. Restarted Thunderbird, and it freezes again. So, I know that the Lightening Calendar database is local; that it is absolutely the problem; but there must be something more corrupted in the database. Apparently no database repair function available with Lightening.
Chosen Solution
OKAY -- Problem solved. I did it myself. I went back into the Lightening Calendar database file (located at: C:\Users\UserName\AppData\Roaming\Thunderbird\Profiles\dtbp4obn.default\calendar-data\local.SQLite) and searched for another record with the same title as the one I deleted before. There was a second one. Apparently the Calendar tried to make a second record instead of updating the one I was working on. This second record was the one that was corrupted. I deleted it, and restored the database (renamed it from .bak file), and Thunderbird started up and the Calendar worked again.
Not sure that Lightening has adequate error checking, because a single year mistake (20170 instead of 2017) broke the calendar program and froze up Thunderbird.
I love T'Bird, and I use Lightening Calendar exclusively (having abandoned Microsoft Outlook). But this even had me truly frightened. I would hate to lose all my calendar entries!
I would hate to lose all my calendar entries!
This is what backups are for. https://support.mozilla.org/kb/profiles-where-thunderbird-stores-user-data#w_backing-up-a-profile