1369343 - Thunderbird/52.1.1 - Auto Update - All folder selections missing! 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server] 1 folderUtils.jsm:61

Status: RESOLVED WORKSFORME

(Thunderbird :: Preferences, defect)

Description

[potterpg]

Attachment: Example No Available Folders

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce:

Auto Updated to TB 52.1.1
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
Build :  	20170509142926

Extensions:
Adblock Plus	2.9	true	{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
Lightning	5.4.1.1	true	{e2fda1a4-762b-4020-b5ad-a41df1933103}
Manually sort folders	1.1.1	true	[e-mail]
Provider for Google Calendar	3.3	true	{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}
Remove Duplicate Messages	0.1.14	true	{12345678-1234-1234-1234-123456789abc}

Tried Restart with add-ons disabled, to no effect.

I don't have time to play with this, so intend to go back to a previous release, as this one doesn't work!


Actual results:

All locations where a folder needs selecting, there is no list to select...
ie.
Get messages - no other choice.
Set message filter - no folder available to move to
settings - place a copy in - No available folders



Error console has many errors:

NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
	gFolderTreeView.getImageSrc chrome://messenger/content/folderPane.js:919:1
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  mailWidgets.xml:2608
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  mailContextMenus.js:362
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:2484
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  mail3PaneWindowCommands.js:103
An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/mail3PaneWindowCommands.js :: UpdateDeleteLabelsFromFolderCommand :: line 103"  data: no]  globalOverlay.js:89
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  mail3PaneWindowCommands.js:103
An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/mail3PaneWindowCommands.js :: UpdateDeleteLabelsFromFolderCommand :: line 103"  data: no]  globalOverlay.js:89
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  mail3PaneWindowCommands.js:103
An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/mail3PaneWindowCommands.js :: UpdateDeleteLabelsFromFolderCommand :: line 103"  data: no]  globalOverlay.js:89
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  mailWindowOverlay.js:184
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  mail3PaneWindowCommands.js:103
An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/mail3PaneWindowCommands.js :: UpdateDeleteLabelsFromFolderCommand :: line 103"  data: no]  globalOverlay.js:89
An error occurred updating the cmd_undo command: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/mailWindowOverlay.js :: SetupUndoRedoCommand :: line 2859"  data: no]  globalOverlay.js:89
An error occurred updating the cmd_redo command: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/mailWindowOverlay.js :: SetupUndoRedoCommand :: line 2859"  data: no]  globalOverlay.js:89
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  mail3PaneWindowCommands.js:103
An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/mail3PaneWindowCommands.js :: UpdateDeleteLabelsFromFolderCommand :: line 103"  data: no]  globalOverlay.js:89
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
Error getting selected account: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/msgAccountCentral.js :: GetSelectedServer :: line 234"  data: no]
  msgAccountCentral.js:57
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderWidgets.xml:120
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderWidgets.xml:111
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderUtils.jsm:61
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server]  folderPane.js:919



Expected results:

A choice of folders...

Comment 1

[potterpg]

Just to note, I have now reverted back a version, and it all works fine again... so something is wrong in the new version...

Comment 2

[Jorg K (CEST = GMT+2)]

(In reply to potterpg from comment #0)
> I don't have time to play with this, so intend to go back to a previous
> release, as this one doesn't work!
It works for some people, that's why we released it. We don't know what makes your installation fail, but we'll look at the errors reported above.

(In reply to potterpg from comment #1)
> Just to note, I have now reverted back a version, and it all works fine
> again... so something is wrong in the new version...
Yes, but it might be hard to find that something without someone who can reproduce the problem.

folderPane.js:919 reads
  if (folder.server.type != "rss" || folder.isServer)
so there is something wrong with accessing the attributes of a particular folder.

folderUtils.jsm:61 reads
  properties.push("serverType-" + aFolder.server.type);
same problem.

Aceman, why does TB 45 work and TB 52 does not?

Comment 3

[potterpg]

Its a fair comment that if you can't test any remedies how can you know if it works...

I'll try recreating it on another machine, so my main email remains working fine...

Just I may not respond quickly...

Comment 4

[:aceman]

Similar to bug 1360836.

potterpg, please see if your server hostname for that account contains some special characters (accents, punycode encoding, etc.).

Comment 5

[potterpg]

I don't think so, but I haven't checked yet, but what you are saying is that the new version works differently from the old version?

Comment 6

[potterpg]

Ok, recreated the setup on another machine...
I hadn't noticed before, but one of my IMAP connections was somehow showing without a name at all...
on this other machine, deleting that server connection completely seemed to clear the problem entirely !!

Looking at the prefs file, I wonder if this directory address is causing the issue?
user_pref("mail.server.server2.directory", "C:\\Users\\Phil\\AppData\\Roaming\\Thunderbird\\Profiles\\m7fx9gmy.default\\ImapMail\\127.0.01");

Not a folder I chose, but maybe the reason for the failure?

Are full stops an issue?

Finding this for me though, is fine, Turnpike was an old email server I had running, and the old emssages it kept have already been moved out of this extinct server... so I can happily remove it as a connection in a now updated thunderbird...
(back to automatic updates for me)

I still have the old setup though if you would like me to test anything...

Comment 7

[Wayne Mery (:wsmwk)]

user initially reports this issue in https://support.mozilla.org/en-US/questions/1162187 
 error console I see: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server] in folderPane.js and folderUtils.jsm

another user reports https://support.mozilla.org/en-US/questions/1160885 "Thunderbird 52 does not show all mail accounts"

Comment 8

[Jorg K (CEST = GMT+2)]

We have this symptom in three bugs: This one here, bug 1360836 and bug 1361775. Not clue as to the cause yet.

Comment 9

[Wayne Mery (:wsmwk)]

(In reply to Jorg K (GMT+1) [currently bustage-fix only, no NI? or r?] from comment #8)
> We have this symptom in three bugs: This one here, bug 1360836 and bug 1361775. 

Yeah neither of those have gone anywhere

Comment 10

[Jasper Lieber]

I have the issue that the actions for all filters (newly created or already existing) say "No available folders".  (And, as a previous reported, I also have an account with no name, and can't figure out how to delete it).  Thirdly, in error console, I see many error messages like this:

23:10:17.868 NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.server] 1 folderUtils.jsm:61
	getFolderProperties resource://gre/modules/folderUtils.jsm:61:3
	ftvItem.prototype.getProperties chrome://messenger/content/folderPane.js:2373:22
	ftv_getRowProperties chrome://messenger/content/folderPane.js:969:12

I just did a fresh install of TB 52.6.0 hoping a fresh install would fix this.

Comment 11

[Jasper Lieber]

Attachment: screenshot of weird unnamed account, can't delete

screen shot showing unnamed account that i'm unsure how to delete.  one other poster reported this as possibly associated with "No folders available" issue.

Comment 12

[:aceman]

Please see if you have some server name (not account name) with special accented characters. See the process in bug 1374948.

Comment 13

[Jasper Lieber]

FYI, I uninstalled TB 52.6 and installed 54.8 and have no problems with any bad accounts or with filters.

Comment 14

[Jorg K (CEST = GMT+2)]

You mean 45.8? Yes, see comment #1 and comment #2. Something has changed between TB 45 and TB 52 that upsets some profiles. We haven't found it yet since we don't have a reproducible case.

Comment 15

[Jasper Lieber]

gah, sorry -- i meant i installed _45.8_ (not 54.8), and 45.8 exhibits no issues with filters or bad accounts.

could my profile be used?  it's very reproducible for me....

Comment 16

[Jorg K (CEST = GMT+2)]

Yes, we could use your profile or we could analyse the the prefs.js contained in it. Since prefs.js contains private information, and the profile contains all your e-mail, passwords, etc., it's problematic to attach it here. Maybe you could send me your prefs.js in a private message (click onto the JK logo and select Profile). You may want to rename it to prefs.txt before sending.

Comment 17

[Jasper Lieber]

Hmmm -- I am very glad you explained the privacy issue, and so now I'm wondering if there's another way to work on this.  Rather than sharing my prefs.js, would something like the following be possible?
1) I (somehow?) copy my prefs.js to a new_prefs.js 
2) replace the private information
3) verify the issue still exists between v45 & v52 
4) perhaps attempt to winnow the issue down by iteratively removing accounts from new_prefs.js and verifying the issue exists between v45 & 52
5) send you the new_prefs.js

How does this sound?  If this sounds like a good plan (with our without step 4), can you recommend how to do this?  Can I simply copy pres.js?  (The only tool I've used regularly is mozbackup.)

Just to be clear, I'm a full-time software developer (currently in the LAMP stack), so I've got basic skills for all of this.  However, like everyong, I'm a bit short on time.  And I'm not sure of all the details for working with the insides of TB.  

-Jasper

PS:  i've tried repeatedly to get bugzilla.mozilla.org to give me notifications for posts to this thread, but it's not happening.  Is there a trick to that?  Thanks

Comment 18

[:aceman]

Jasper, have you tried comment 12? You may spot the problem account even without sending us the prefs.js.

Comment 19

[Jorg K (CEST = GMT+2)]

(In reply to Jasper Lieber from comment #17)
> How does this sound?  If this sounds like a good plan (with our without step
> 4), can you recommend how to do this?  Can I simply copy pres.js?  (The only
> tool I've used regularly is mozbackup.)
It's a text file, you can copy it. You can also safely e-mail it to me as prefs.txt, I won't disclose the private information. Of course you could also do 2) and 4) to save us work. But if you change account information, TB might not run at all any more.

We might also consider a TeamViewer session.

> PS:  i've tried repeatedly to get bugzilla.mozilla.org to give me
> notifications for posts to this thread, but it's not happening.  Is there a
> trick to that?  Thanks
You need to edit your preferences: Click on the icon on the TR (to the right of "My Dashboard"), Preferences, Email Preferences. I'm fighting with the matrix myself at times, the more ticks, the more e-mail you receive.

Comment 20

[Jasper Lieber]

Gah --- sorry, I didn't mean to disappear but the no notifications thing is hampering me.  I don't know what you mean by 'Click on the icon on the TR (to the right of "My Dashboard")' -- what's the TR ? I've again dug around in my email preferences, but they look okay to me!!  I can paste a screen shot if need be.

As to the actual bug -- I don't think I have an account with strange characters in it.  And I simply haven't pulled up my prefs file to send to you, but hope to do so asap.  Perhaps a TeamViewer session could be great.  

Thanks

Comment 21

[Wayne Mery (:wsmwk)]

Assuming you have sorted this out by now ... do you have the same issue after being updated to version 60?

Comment 22

[potterpg]

After removing the one server connection line...
I have since had no issues, and yes currently running without issue on the latest version 60.3.0
I no longer have the old version running for test purposes.

Comment 23

[Wayne Mery (:wsmwk)]

Thanks for the update

Comment 24

[Jasper Lieber]

Hi again -- I just updated to 60.5.1 and this issue is still happening for me. Many months ago, Jorgk offered to look at my prefs.js -- is that still possible?

Again, two issues:
a) folder selections are unavailable when creating or modifying message filters
b) I have an unknown unnamed account that I can't delete.

I also did spend a little time looking at my prefs.js and comment 12 (accented characters in server names), but am not sure I have that issue in my pref.js

I'll go ahead and send my prefs.js to Jorgk -- and see if he can spot anything strange. (I'd rather not post my prefs.js, since it has some private-ish data.)

Thanks. -Jasper

Comment 25

[Jasper Lieber]

(given my prev comment, should this bug be re-opened?)

Comment 26

[Jorg K (CEST = GMT+2)]

Sorry, I got your e-mail, but it "fell off my desk". I actually forwarded it to a developer colleague to take a look at your prefs.js. I must get back to it later.

Comment 27

[Jorg K (CEST = GMT+2)]

I looked at the prefs.js file and inspected the account configuration. Looks like the fifth of eight accounts got a little corrupted, so I suggested steps to correct or remove it in a private message.

This seems to be a support issue, so there's no need to reopen the bug.

Comment 28

[Jorg K (CEST = GMT+2)]

Problem solved by correcting user_pref("mail.server.server6.hostname", "587"); in the preferences file.

Comment 29

[:aceman]

While we do not know why that pref value got corrupt, we could make some mitigations so that a broken account does not break the other ones. Both comment 0 and comment 10 describe the folder picker is busted when one of the accounts is broken so even folders from working accounts aren't presented.
In comment 11 (screenshot), it seems folder pane is already kinda immune to this, the non-broken accounts do show.
We already did protection for this in the account manager, which had the same problem (broken account caused no display of the other ones).

I can try if pref from comment 28 reproduces the account malfunction and then I could make patch for the folder picker.