Entourage 2004 Database Corruption, etc.

A

Auri Rahimzadeh

(I've renamed the message subject because the last one wasn't focused
enough)

To whom it may concern:

A client has recently upgraded to Entourage 2004 so he can talk
"successfully" to Exchange 2003 Server. However, the following problems
are occuring:

1. It takes FOREVER to syncronize, even over the 100 megabit connection.
2. Every day or two Entourage says his database is corrupt (22 times
now) and has to rebuild. This takes about 15 hours (4 hours scanning, 11
hours rebuilding).
3. While the database is rebuilding he cannot use any other Microsoft
Office applications!!! (so, can't write reports, look at spreadsheets,
etc.! Who at MS thought of that one???)

Note he probably has over 100,000 messages in his email account, across
many folders. I run Outlook 2003 on my PC at home with over 4000
messages in my inbox, and probably close to how many messages he has
total and all works fine. I haven't tried synching my Entourage X to my
Exchange 2000 server, but I'm afraid if it's going to mess up my Mac,
too. Note he has also run Disk Utility and fixed all permissions. I do
not believe he has run Disk First Aid yet, but all other applications on
his system work fine -- only Entourage causes trouble (regardless of
version).

Maybe this is a database file size limit in Entourage?

Is anyone else having these problems? Is there someone at Microsoft who
can help? This is costing my client a lot of time and money since his
business relies on sending emails out!!!

I have attached some of the info returned by Entourage to this message.

Thanks,

-Auri Rahimzadeh

Microsoft Error Reporting log version: 1.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2004-08-11 19:46:00 -0400
Application Name: Microsoft Entourage
Application Version: 11.0.0.040405
Module Name: Microsoft Framework DB
Module Version: 11.0.0.040326
Module Offset: 0x00023a80
Extra app info: Reg=English Loc=0x0409


Thread 0 crashed:

# 1 0x01497f10 in (Microsoft Framework DB + 0x00023a80)
# 2 0x01497aa4 in (Microsoft Framework DB + 0x00023614)
# 3 0x01497370 in (Microsoft Framework DB + 0x00022ee0)
# 4 0x014f3fc4 in (Microsoft Framework DB + 0x0007fb34)
# 5 0x014f0200 in (Microsoft Framework DB + 0x0007bd70)
# 6 0x014c8a18 in (Microsoft Framework DB + 0x00054588)
# 7 0x014e1264 in (Microsoft Framework DB + 0x0006cdd4)
# 8 0x014e1584 in (Microsoft Framework DB + 0x0006d0f4)
# 9 0x020e5240 in (Microsoft Entourage + 0x00047e00)
# 10 0x020e52c0 in (Microsoft Entourage + 0x00047e80)
# 11 0x020dfd60 in (Microsoft Entourage + 0x00042920)
# 12 0x020e0798 in (Microsoft Entourage + 0x00043358)
# 13 0x0130ea68 in (Microsoft Framework UI + 0x00142c18)
# 14 0x020df394 in (Microsoft Entourage + 0x00041f54)
# 15 0x0130f30c in (Microsoft Framework UI + 0x001434bc)
# 16 0x020df5b8 in (Microsoft Entourage + 0x00042178)
# 17 0x012f25e0 in (Microsoft Framework UI + 0x00126790)
# 18 0x01304720 in (Microsoft Framework UI + 0x001388d0)
# 19 0x01305278 in (Microsoft Framework UI + 0x00139428)
# 20 0x004d7124 in (PowerPlantZ + 0x00032564)
# 21 0x004e7de8 in (PowerPlantZ + 0x00043228)
# 22 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 23 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 24 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 25 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 26 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 27 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 28 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 29 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 30 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 31 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 32 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 33 0x004e7dd4 in (PowerPlantZ + 0x00043214)
# 34 0x004ea01c in (PowerPlantZ + 0x0004545c)
# 35 0x012e05d4 in (Microsoft Framework UI + 0x00114784)
# 36 0x004e9e20 in (PowerPlantZ + 0x00045260)
# 37 0x012ddfc4 in (Microsoft Framework UI + 0x00112174)
# 38 0x012e059c in (Microsoft Framework UI + 0x0011474c)
# 39 0x004c59a8 in (PowerPlantZ + 0x00020de8)
# 40 0x004c55f8 in (PowerPlantZ + 0x00020a38)
# 41 0x020c1690 in (Microsoft Entourage + 0x00024250)
# 42 0x004beff0 in (PowerPlantZ + 0x0001a430)
# 43 0x020b38a8 in (Microsoft Entourage + 0x00016468)
# 44 0x004bed9c in (PowerPlantZ + 0x0001a1dc)
# 45 0x020b0918 in (Microsoft Entourage + 0x000134d8)
# 46 0x0247dac0 in (Microsoft Entourage + 0x003e0680)
 
D

Diane Ross

A client has recently upgraded to Entourage 2004 so he can talk
"successfully" to Exchange 2003 Server. However, the following problems
are occuring:

1. It takes FOREVER to syncronize, even over the 100 megabit connection.
2. Every day or two Entourage says his database is corrupt (22 times
now) and has to rebuild. This takes about 15 hours (4 hours scanning, 11
hours rebuilding).
3. While the database is rebuilding he cannot use any other Microsoft
Office applications!!! (so, can't write reports, look at spreadsheets,
etc.! Who at MS thought of that one???)
Click to expand...

Generally it does not take this long to rebuild. However, I can't imagine
any database taking that long. I suspect the rebuild is not successful.

My database is only 866 MB and it only takes a couple of minutes to rebuild.

Is the client able to use the Export option under the File menu to export
all? If he can export, then I suggest he export and import into a new
Identity.

I'm assuming some of this mail is not recent. He might consider using a
separate Identity for older mail. This might be more manageable.
Note he probably has over 100,000 messages in his email account, across
many folders. I run Outlook 2003 on my PC at home with over 4000
messages in my inbox, and probably close to how many messages he has
total and all works fine. I haven't tried synching my Entourage X to my
Exchange 2000 server, but I'm afraid if it's going to mess up my Mac,
too. Note he has also run Disk Utility and fixed all permissions. I do
not believe he has run Disk First Aid yet, but all other applications on
his system work fine -- only Entourage causes trouble (regardless of
version).

Maybe this is a database file size limit in Entourage?
Click to expand...

Entourage 2004 has no size limit, just a limit to the number of items in the
Entourage database: 2 million database items.

Note: Database items, not Entourage objects (such as messages, contacts,
events, etc.). Dave Cortright, Entourage developer, explains it this way: An
email or news message is actually TWO database items, and for anyone with
near a million Entourage objects (messages, contacts, events, etc.), they
will almost all be messages - the other stuff will be "loose change". So
the limit is effectively just under 1 million messages. Entourage will
notify you if you ever approach the limit.

Entourage X has a 4 GB limit on the Database file
 
Top