You are here

Local Directory Path

6 posts / 0 new
Last post
AdrianK_IT
AdrianK_IT's picture
Offline
Last seen: 2 years 3 months ago
Joined: 2011-04-14 14:37
Local Directory Path

[v24.1.0] I am unable to make any changes to any account's server settings, because when I try to OK them, I get a message similar to the following:

The Local Directory path "N:\apps\7.Admin\Thunderbird\Data\profile\accounts\{account}" is not suitable for message storage. Please choose another directory.

I don't know when this issue started, since I haven't tried to make changes for months. Needless to say, all the accounts whose messages are stored in their 'not suitable' {account} folder work perfectly.

What is wrong with the path (now)? Why has in become 'not suitable'?

With thanks.

John T. Haller
John T. Haller's picture
Online
Last seen: 33 min 11 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Thunderbird Itself

That error is coming from Thunderbird itself, not our additions. Could it be that Thunderbird is checking for and not liking storing messages on network drives?

Sometimes, the impossible can become possible, if you're awesome!

AdrianK_IT
AdrianK_IT's picture
Offline
Last seen: 2 years 3 months ago
Joined: 2011-04-14 14:37
Not Network Drive

Thanks for replying, John, but the path is on the removable drive (USB stick) on which Tbird Portable is installed, not a network drive. I assumed it was a Tbird problem, but must be something to do with the (portable) path.

I have posted on Mozillazine forum as well, but I fear I may get a 'it's something to do with it being the portable version' response!

John T. Haller
John T. Haller's picture
Online
Last seen: 33 min 11 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Unaltered Thunderbird

The copy of Thunderbird that's running inside Thunderbird Portable is completely unaltered. It's just using the -profile switch to point it to the profile. All our updates happen on startup to adjust paths in prefs.js and the extensions sqlite db. It's Thunderbird showing you the error (not our code) and it can't be a result of our code as it's not affecting Thunderbird while it's running.

I'd suggest copying the whole thing locally and running it from there to eliminate any issues with the drive. If it still has issues, change it to a more normal path to eliminate the possibility that Thunderbird doesn't like a directory starting with a 7 or with the word Admin in the name.

Sometimes, the impossible can become possible, if you're awesome!

AdrianK_IT
AdrianK_IT's picture
Offline
Last seen: 2 years 3 months ago
Joined: 2011-04-14 14:37
Never Said It Was

John, thanks for your reply, but at no time have I ever thought (or said) that I believed the problem is related to the PortableApps wrapper.

I have assumed from the start it was an internal Tbird problem (possibly related to an update); the mystery for me is why paths that were acceptable before have suddenly stopped being so. I repeat: the paths used to work, could be set, could be changed! (As could other server settings, without throwing the error message.)

I posted in the hope that some user of Tbird (portable version) has encountered a similar problem, and can offer their solution. It occured to me that they might be better able to help me than most users of (non-portable) Tbird, since the former will have experience of non-standard profile paths, the latter will not.

I had already troubleshot whether the wrapper might be a problem, by launching thunderbird.exe directly with the -profile switch pointing to my (portable) path.

John T. Haller
John T. Haller's picture
Online
Last seen: 33 min 11 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Drive

I realize that, just being thorough. You should still try copying it and running it from another location to see if it is a drive issue. Did the change happen on the recent TB upgrade (did it work with 24.0 but not with 24.1, for instance)? My path suggestions were made taking into account that it used to work. Something in TB itself could have changed and now it doesn't like your specific path with the -profile switch. That's why I suggested the path changes. We're trying to get it down to the exact bit that is triggering the issue one piece at a time.

Sometimes, the impossible can become possible, if you're awesome!

Log in or register to post comments