Application Entourage has unexpectedly quit

D

ds

Entourage X (with SR1) on Tiger has started giving this message along
with an Apple "report this error" dialog whenever I quit the program or
try to switch identities. Entourage seems to work fine otherwise, and
has 50,000 messages in the database.

I did an advanced rebuild and it still is happening. Also I copied the
identity to another machine and it did the same. Also junked all
preferences and renamed the Temp folder.

Ideas?
 
B

Barry Wainwright

Entourage X (with SR1) on Tiger has started giving this message along
with an Apple "report this error" dialog whenever I quit the program or
try to switch identities. Entourage seems to work fine otherwise, and
has 50,000 messages in the database.

I did an advanced rebuild and it still is happening. Also I copied the
identity to another machine and it did the same. Also junked all
preferences and renamed the Temp folder.

Ideas?
Click to expand...

Take a look and see if you have any schedules 9unde rth eTools menu) set to
fire 'on quit' - it may be something in there has been corrupted.

Please report your findings.
 
D

ds

no there aren't. I did add one just to read mail on quit based on a
suggestion a list somewhere, and it works fine, then gives the error
message anyway. I have the entire crashlog report if it is helpful.

I also get the same crash when trying to switch identities.
 
B

Barry Wainwright

no there aren't. I did add one just to read mail on quit based on a
suggestion a list somewhere, and it works fine, then gives the error
message anyway. I have the entire crashlog report if it is helpful.

I also get the same crash when trying to switch identities.
Click to expand...

I'm not surprised at you getting the same crash on a=n identity switch -
that sguts down the database daemon in a similar way to quitting the app.

Try repairing permissions - it is possible a prefs file has become
inaccessible for some reason and the app is crashing when trying ot write to
it on quit.

To repair perms, fire up the 'disk utility' in the /Applications/Utilities
folder.
 
D

ds

I'd already done that but your message prompted me also to run Disk
Warrior to rebuild the directories. Still crashes.

Running the Activity monitor shows it isn't the daemon crashing but the
Entourage process, thread 0

PID: 282
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x048fb784
Thread 0 Crashed:
0 Microsoft Framework UI 0x01478798 0x133e000 + 1288088
1 Microsoft Entourage 0x0055ae0c 0x405000 + 1400332
2 Microsoft Entourage 0x004a0ee4 0x405000 + 638692
3 Microsoft Entourage 0x004893c8 0x405000 + 541640
4 Microsoft Entourage 0x00488a84 0x405000 + 539268
 
M

matt neuburg

ds said:
Entourage X (with SR1) on Tiger has started giving this message along
with an Apple "report this error" dialog whenever I quit the program or
try to switch identities. Entourage seems to work fine otherwise, and
has 50,000 messages in the database.

I did an advanced rebuild and it still is happening. Also I copied the
identity to another machine and it did the same.
Click to expand...

What happens if you make a new user with a completely clean identity;
does it happen there? If not, there's something wrong with your database
(or your user, though this seems less likely since you claim the same
thing happens on a different machine). m.
 
D

ds

With a new identity and a different OS user it all works fine - quit as
well as change identity, so perhaps it is the database or a user
specific setting

If the database is corrupted, how to repair it? I ran the rebuild
(option on open) three times, both typical and advanced. There might be
a bad message or attachment, but if so how to find it?
 
M

matt neuburg

ds said:
With a new identity and a different OS user it all works fine - quit as
well as change identity, so perhaps it is the database or a user
specific setting

If the database is corrupted, how to repair it?
Click to expand...

One approach would be: don't bother. Consider the problem solved. You
now have a new identity / user that works. So first decide whether what
fixed it is the identity alone or the identity + user. Then migrate into
the new identity (and possibly into the new user). Go carefully as you
drag folders from the old database into the Finder and from there (after
the appropriate user switch) into the new database: stop after each one
and make sure it's working, that you have not imported whatever is
causing the problem. It may be that you'll be able to bring everything
across and the new database / identity / user will just work. m.
 
D

ds

interesting. I didn't know you could do that. I might just move out the
98,000 emails and let Spotlight index them.

david
 
N

Nathan Herring [MSFT]

I'd already done that but your message prompted me also to run Disk
Warrior to rebuild the directories. Still crashes.

Running the Activity monitor shows it isn't the daemon crashing but the
Entourage process, thread 0

PID: 282
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x048fb784
Thread 0 Crashed:
0 Microsoft Framework UI 0x01478798 0x133e000 + 1288088
1 Microsoft Entourage 0x0055ae0c 0x405000 + 1400332
2 Microsoft Entourage 0x004a0ee4 0x405000 + 638692
3 Microsoft Entourage 0x004893c8 0x405000 + 541640
4 Microsoft Entourage 0x00488a84 0x405000 + 539268
Click to expand...

This is close, but not everything we would need to tackle looking at the
problem. We would need the version #s of Entourage and the Framework (in the
"Office") folder. Unfortunately, while Panther made the crash reports
possible to use for Carbon applications, it still doesn't list the version
numbers correctly for them. (Previous to Panther, we wouldn't even get the
offset into the shared library either -- just an absolute position in memory
which was useless to us, since it did not list where the libraries were
loaded into memory.) These are two reasons why we wrote the Microsoft Error
Reporting application for Office 2004, so we could make sure we have all the
information necessary to identify where it crashed.

That said, we are focused largely on future work with some SP-like support
for current version products. It is significantly more likely that we'd look
at problems reported for 2004 (and for the latest version, currently 11.1)
than for Office v. X.
 
Top