Closed
Bug 612914
Opened 15 years ago
Closed 15 years ago
Error: [Exception... "Component returned failure code: 0x80550007 [nsIMsgFolder.getStringProperty]" nsresult: "0x80550007 (<unknown>)" location: "JS frame :: chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2441" data: no] Source
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jbecerra, Unassigned)
Details
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13pre) Gecko/20101116 Lanikai/3.1.7pre
I felt lucky today and tried checking my mail after having removed all my folders' .msf files in an attempt to fix my problem from bug 609674. When it came up I didn't get any new mail. There are tons of messages in the error console that look like this:
Error: [Exception... "Component returned failure code: 0x80550007 [nsIMsgFolder.getStringProperty]" nsresult: "0x80550007 (<unknown>)" location: "JS frame :: chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2441" data: no] Source
At this point, I welcome any suggestions. Should I just start from scratch? Make it an IMAP account instead? It's just hard to let go of all that filter, folder, message, tag organization.
Comment 1•15 years ago
|
||
We're catching that error and logging it, and you will get that error if your .msf files are missing, and your panacea.dat file is missing entries. But it shouldn't be fatal. You can regenerate your local folder .msf files by doing an advanced search over all folders, for any particular string you want (edit, find, search messages, pick a pop3 or local folders account, and do a search.)
This bug is essentially invalid since you went and removed all the .msf files. We should go back to bug 609674.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•