Spletno mesto bo delovalo z omejenimi zmožnostmi, medtem ko na njem izvajamo vzdrževalna dela za vas. Če članki ne rešijo vaše težave in želite zastaviti vprašanje, naša skupnost za podporo čaka na vas na @FirefoxSupport na Twitterju in na /r/firefox na Redditu.

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

Compact error alert associated with Exchange-exquilla account

  • 3 odgovori
  • 2 imata to težavo
  • 4 ogledi
  • Zadnji odgovor od sfhowes

Roz123
Roz123
more options

Using thunderbird 60.5.1, I have two accounts, a gmail and microsoft exchange account (using exquilla). Often when I switch from the exchange inbox to the gmail inbox I receive the errors: "The folder 'Inbox' cannot be compacted because another operation is in progress. Please try again later." Followed by "The folder 'Sent' cannot be compacted because another operation is in progress. Please try again later." then "The folder 'Trash' cannot be compacted because another operation is in progress. Please try again later." then "The folder 'Junk' cannot be compacted because another operation is in progress. Please try again later."

I can close the alerts, and everything works, but having to close these almost every time I check emails is very annoying. I have archived both inbox and sent folders, and deleted the trash files, so the folders are not large (between 200 to 2500 emails for each folder). I have tried turning off the auto compact config, but no change.

Any suggestions are greatly appreciated.

Using thunderbird 60.5.1, I have two accounts, a gmail and microsoft exchange account (using exquilla). Often when I switch from the exchange inbox to the gmail inbox I receive the errors: "The folder 'Inbox' cannot be compacted because another operation is in progress. Please try again later." Followed by "The folder 'Sent' cannot be compacted because another operation is in progress. Please try again later." then "The folder 'Trash' cannot be compacted because another operation is in progress. Please try again later." then "The folder 'Junk' cannot be compacted because another operation is in progress. Please try again later." I can close the alerts, and everything works, but having to close these almost every time I check emails is very annoying. I have archived both inbox and sent folders, and deleted the trash files, so the folders are not large (between 200 to 2500 emails for each folder). I have tried turning off the auto compact config, but no change. Any suggestions are greatly appreciated.

Vsi odgovori (3)

sfhowes
sfhowes
  • Top 10 Contributor
more options

It appears the gmail folders have become corrupted, so the repair explained here might fix it. Try it first with the Inbox and then Trash, Sent and Junk, if successful.

To open the profile folder, select Help/Troubleshooting Information and click Open Folder; close TB before making any changes.

skyline57
skyline57
more options

I have the same problem. The thing is that I don't believe any compacting is actually happening. I can manually compact the folders without any problem. It's only when switching to a gmail account from the Exchange account that the problem happens.

sfhowes
sfhowes
  • Top 10 Contributor
more options

skyline57 said

I have the same problem. The thing is that I don't believe any compacting is actually happening. I can manually compact the folders without any problem. It's only when switching to a gmail account from the Exchange account that the problem happens.

You can see if compacting is actually occurring by checking the size of the mbox file for the folder in the profile folder, before and after. The mbox file has the same name as you see in TB, but no file extension. If the size doesn't change (decrease) when it should, it suggests the folder is corrupted (see above for fix).

There could also be a bug in the Exchange add-on.