Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Exception getSmartFolderName

  • 8 个回答
  • 2 人有此问题
  • 1 次查看
  • 最后回复者为 oyle

more options

Suddenly folders gone on exchange (office365) This is also the case in safe mode. Folders do appear in subscribe window, but will not be subscribed to.

Timestamp: 20/01/16 09:51:53 Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.getStringProperty]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2790" data: no] Source File: chrome://messenger/content/folderPane.js Line: 2792

Suddenly folders gone on exchange (office365) This is also the case in safe mode. Folders do appear in subscribe window, but will not be subscribed to. Timestamp: 20/01/16 09:51:53 Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgFolder.getStringProperty]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2790" data: no] Source File: chrome://messenger/content/folderPane.js Line: 2792

被采纳的解决方案

Apparently this was a change in Office365.

The solution seemed to be to change passwords. (This was required for "Skype for business" but not anywhere associated with mail) Changing lead to IMAP working.

Some of the folder handling seems to have changed as some of the folders in rules where not recognized, but on recreating the rules they work.

In the interim, while they where changing things, it turned out that "display all folders" allowed me to see the folders.

Normal folder subscription is back and working. Some rules need to be recreated.

定位到答案原位置 👍 0

所有回复 (8)

more options

Copy to sent also fails on sending.

more options

Exchange EWS Provider 3.5.0-beta1

(It seems I couldn't write this coherently in one go)

more options

and given safe mode, hopefully the extension is irrelevant

more options

A new profile also does not help.

more options

There have been alot of similar cases with outlook/hotmail/office365 , so something is clearly going on.

Please try this to see if you can subscribe / show in folder pane again.

'tools' > 'Account Settings' > 'Server Settings' for the mail account or Right click on mail account name in Folder Pane and select 'Settings' select 'Server Settings' for the mail account click on 'Advanced' button uncheck: 'Show only subscribed folders'. clickon OK click on OK

then try to subscribe again. Right click on mail account and select 'Subscribe' See if this time you can select the folder. click on OK

Report back on results.

more options

I've created a bug report, asking for this to be checked out.

As this is not actually affecting me - I don't have outlook/hotmail/office365 mail account, then it would be helpful if you could offer information for the bugzilla people. Please tell them : what OS you use. what version of thunderbird. What server you are trying to connect to subscribe folders. state what folders disappeared. state whether you could see folders in the 'subscribe' window etc you would need to register/logon to post comment. It would also be usefult to 'Vote' for the bug. Voting is located in the top section where it says: Importance: (vote)

more options

选择的解决方案

Apparently this was a change in Office365.

The solution seemed to be to change passwords. (This was required for "Skype for business" but not anywhere associated with mail) Changing lead to IMAP working.

Some of the folder handling seems to have changed as some of the folders in rules where not recognized, but on recreating the rules they work.

In the interim, while they where changing things, it turned out that "display all folders" allowed me to see the folders.

Normal folder subscription is back and working. Some rules need to be recreated.