搜索 | 用户支持

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

Learn More

No folders are listed after moving profile

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

more options

After moving my profile Thunderbird shows all my accounts but no folders at all, even under "Local Folders" or an RSS feed I have. I can still see account settings.

This is the error I'm seeing in Error Console:

Timestamp: 1/18/17, 12:38:32 PM Error: [Exception... "Component returned failure code: 0x80550007 [nsIMsgFolder.getStringProperty]" nsresult: "0x80550007 (<unknown>)" location: "JS frame :: chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2780" data: no] Source File: chrome://messenger/content/folderPane.js Line: 2782

After moving my profile Thunderbird shows all my accounts but no folders at all, even under "Local Folders" or an RSS feed I have. I can still see account settings. This is the error I'm seeing in Error Console: Timestamp: 1/18/17, 12:38:32 PM Error: [Exception... "Component returned failure code: 0x80550007 [nsIMsgFolder.getStringProperty]" nsresult: "0x80550007 (<unknown>)" location: "JS frame :: chrome://messenger/content/folderPane.js :: getSmartFolderName :: line 2780" data: no] Source File: chrome://messenger/content/folderPane.js Line: 2782

被采纳的解决方案

I found the problem. The profile was originally symlinked from another location, but Thunderbird had resolved through the symlink, so the base path was stored in a bunch of places in prefs.js. After fixing the absolute paths and fixing a bunch of directory-rel entries things seem to be working again.

定位到答案原位置 👍 0

所有回复 (2)

more options

Most likely, you have not set some path correctly, skipped profiles.ini, or the profile locations or other path settings do not match. Did you use the instructions in the Moving Thunderbird Data to a New Computer and Profiles - Where Thunderbird stores your messages and other user data support articles?

more options

选择的解决方案

I found the problem. The profile was originally symlinked from another location, but Thunderbird had resolved through the symlink, so the base path was stored in a bunch of places in prefs.js. After fixing the absolute paths and fixing a bunch of directory-rel entries things seem to be working again.