C
christopher.fox
We have a fairly large-scale deployment of Entourage, and have recently
started upgrading users from 11.1.1 to SP2 followed by 11.2.1.
We've started seeing an issue where user's database is becoming
corrupted (requiring a rebuild) when they attempt to move multiple
messages from a folder in their Exchange account to a local folder, or
attempt to delete multiple messages from the Exchange "Deleted Items"
folder. Entourage appears to delete the mails, but as soon as Entourage
attempts to connect to the Exchange server to receive mail, a dialogue
box appears that says "Mail could not be received at this time...". At
this point, the only way to resolve the issue is to rebuild the
database. Also, the messages never get moved or deleted from the
Exchange account.
This is a particularly nefarious as the default "Empty Deleted Items
Folder" schedule *always* points to the *local* deleted items folder,
and never to the Exchange account deleted items folder. If it isn't
edited to point to the deleted items folder in the Exchange account by
hand, deleted messages build up in the Exchange mailbox; users then
attempt to delete them by hand, causing the issue noted above. Also, it
appears that a database rebuild resets the Empty Deleted Items Folder
schedule to point *back* to the local Deleted Items folder, instead of
the one in the Exchange account.
Our Exchange environment was patched with the required update for SP2.
Thanks for any insight.
started upgrading users from 11.1.1 to SP2 followed by 11.2.1.
We've started seeing an issue where user's database is becoming
corrupted (requiring a rebuild) when they attempt to move multiple
messages from a folder in their Exchange account to a local folder, or
attempt to delete multiple messages from the Exchange "Deleted Items"
folder. Entourage appears to delete the mails, but as soon as Entourage
attempts to connect to the Exchange server to receive mail, a dialogue
box appears that says "Mail could not be received at this time...". At
this point, the only way to resolve the issue is to rebuild the
database. Also, the messages never get moved or deleted from the
Exchange account.
This is a particularly nefarious as the default "Empty Deleted Items
Folder" schedule *always* points to the *local* deleted items folder,
and never to the Exchange account deleted items folder. If it isn't
edited to point to the deleted items folder in the Exchange account by
hand, deleted messages build up in the Exchange mailbox; users then
attempt to delete them by hand, causing the issue noted above. Also, it
appears that a database rebuild resets the Empty Deleted Items Folder
schedule to point *back* to the local Deleted Items folder, instead of
the one in the Exchange account.
Our Exchange environment was patched with the required update for SP2.
Thanks for any insight.