Open Bug 1558955 Opened 6 years ago Updated 3 years ago

nsIMsgFolder.server failure after creating a new account

Categories

(MailNews Core :: Account Manager, defect)

defect

Tracking

(Not tracked)

People

(Reporter: aceman, Unassigned)

References

Details

After creating a new mail account in Thunderbird's account manager, the account tree is rebuilt with the new account, but I get this error in the console:

NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server] 8 folder-menupopup.js:59

There are warnings in the terminal preceding this error:
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file mailnews/base/util/nsMsgDBFolder.cpp, line 2953
[8559, Main Thread] WARNING: '!aFile', file mozilla/xpcom/io/nsLocalFileCommon.cpp, line 128
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file mailnews/base/util/nsMsgDBFolder.cpp, line 2953
[8559, Main Thread] WARNING: '!aFile', file mozilla/xpcom/io/nsLocalFileCommon.cpp, line 128
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80520015: file mailnews/base/util/nsMsgDBFolder.cpp, line 1227
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file mailnews/base/util/nsMsgDBFolder.cpp, line 2953
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file mailnews/db/msgdb/src/nsMsgDatabase.cpp, line 98
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file mailnews/base/util/nsMsgDBFolder.cpp, line 2953
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file mailnews/db/msgdb/src/nsMsgDatabase.cpp, line 344
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file mailnews/imap/src/nsImapMailFolder.cpp, line 546
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file mailnews/base/util/nsMsgDBFolder.cpp, line 2953
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file mailnews/base/util/nsMsgDBFolder.cpp, line 2953
[8559, Main Thread] WARNING: '!aFile', file mozilla/xpcom/io/nsLocalFileCommon.cpp, line 128
[8559, Main Thread] WARNING: NS_ENSURE_TRUE(!pathKey.IsEmpty()) failed: file mailnews/base/src/nsMsgFolderCache.cpp, line 227
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file mailnews/base/util/nsMsgDBFolder.cpp, line 2953
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file mailnews/db/msgdb/src/nsMsgDatabase.cpp, line 98
[8559, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file mailnews/base/util/nsMsgDBFolder.cpp, line 2953

This only happens once the account is created. Then visiting the various panes seems to work OK, especially the Copies & Folders pane seems fine with all folder pickers populated.

May this be a problem from the new folder-menupopup OR some of the recent URI changes?

I get these when creating an IMAP account:

[5768, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file c:/mozilla-source/comm-central/comm/mailnews/base/util/nsMsgDBFolder.cpp, line 2953
[5768, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file c:/mozilla-source/comm-central/comm/mailnews/db/msgdb/src/nsMsgDatabase.cpp, line 98
[5768, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file c:/mozilla-source/comm-central/comm/mailnews/base/util/nsMsgDBFolder.cpp, line 2953
[5768, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file c:/mozilla-source/comm-central/comm/mailnews/db/msgdb/src/nsMsgDatabase.cpp, line 344
[5768, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file c:/mozilla-source/comm-central/comm/mailnews/imap/src/nsImapMailFolder.cpp, line 546

That's a subset of what you quoted. Glancing at the top and bottom of the stack, it looks like some access is attempted to a folder that doesn't exist for the account yet.

Blocks: 1560391
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.