Entourage 2008 - STILL crashes multiple times per day

[Rick_Wrightson]

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel Email Client: Exchange I want to point out that the question above: "What type of email client are you using?" doesn't offer a complete choice. I use Entourage to pick up my mail for three different email accounts - from an Exchange server; an IMAP server and; a POP2 server.

I first posted this problem a couple of months ago and was told that it was a WebCore issue and there was nothing to do, except for a work around, until a fix came out.

I think MS has since released two updates (last being Version: 12.2.3.091001) and Apple has released three updates (10.6; 10.6.1 and 10.6.2). We still have the crashes. Is the only solution to go to Apple Mail?

Here is my last error log (as you can see at the bottom of the log, this was the 131st crash reported)

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-11-20 10:03:26 -0500
Application Name: Microsoft Entourage
Application Bundle ID: com.microsoft.Entourage
Application Signature: OPIM
Application Version: 12.2.3.091001
Crashed Module Name: WebCore
Crashed Module Version: unknown
Crashed Module Offset: 0x0002c08b
Blame Module Name: WebCore
Blame Module Version: unknown
Blame Module Offset: 0x0002c08b
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x92c1808b in .objc_class_name_AccessibilityObjectWrapper + 0x9235DA1F (WebCore + 0x0002c08b)
# 2 0x92c92a26 in .objc_class_name_AccessibilityObjectWrapper + 0x923D83BA (WebCore + 0x000a6a26)
# 3 0x92c92993 in .objc_class_name_AccessibilityObjectWrapper + 0x923D8327 (WebCore + 0x000a6993)
# 4 0x92c9255a in .objc_class_name_AccessibilityObjectWrapper + 0x923D7EEE (WebCore + 0x000a655a)
# 5 0x92df088e in .objc_class_name_AccessibilityObjectWrapper + 0x92536222 (WebCore + 0x0020488e)
# 6 0x92df04a8 in .objc_class_name_AccessibilityObjectWrapper + 0x92535E3C (WebCore + 0x002044a8)
# 7 0x92c9094f in .objc_class_name_AccessibilityObjectWrapper + 0x923D62E3 (WebCore + 0x000a494f)
# 8 0x92c90820 in .objc_class_name_AccessibilityObjectWrapper + 0x923D61B4 (WebCore + 0x000a4820)
# 9 0x92c8bd67 in .objc_class_name_AccessibilityObjectWrapper + 0x923D16FB (WebCore + 0x0009fd67)
# 10 0x92c35672 in .objc_class_name_AccessibilityObjectWrapper + 0x9237B006 (WebCore + 0x00049672)
# 11 0x92c863ac in .objc_class_name_AccessibilityObjectWrapper + 0x923CBD40 (WebCore + 0x0009a3ac)
# 12 0x92c84995 in .objc_class_name_AccessibilityObjectWrapper + 0x923CA329 (WebCore + 0x00098995)
# 13 0x92c32b59 in .objc_class_name_AccessibilityObjectWrapper + 0x923784ED (WebCore + 0x00046b59)
# 14 0x92c83127 in .objc_class_name_AccessibilityObjectWrapper + 0x923C8ABB (WebCore + 0x00097127)
# 15 0x926c61dc in .objc_class_name_WKAppKitDrawDecoyWindow + 0x925D8154 (WebKit + 0x0001a1dc)
# 16 0x926c6103 in .objc_class_name_WKAppKitDrawDecoyWindow + 0x925D807B (WebKit + 0x0001a103)
# 17 0x926c5e7b in .objc_class_name_WKAppKitDrawDecoyWindow + 0x925D7DF3 (WebKit + 0x00019e7b)
# 18 0x926c5df9 in .objc_class_name_WKAppKitDrawDecoyWindow + 0x925D7D71 (WebKit + 0x00019df9)
# 19 0x92c75617 in .objc_class_name_AccessibilityObjectWrapper + 0x923BAFAB (WebCore + 0x00089617)
# 20 0x92c75289 in .objc_class_name_AccessibilityObjectWrapper + 0x923BAC1D (WebCore + 0x00089289)
# 21 0x92c749e5 in .objc_class_name_AccessibilityObjectWrapper + 0x923BA379 (WebCore + 0x000889e5)
# 22 0x92c7384d in .objc_class_name_AccessibilityObjectWrapper + 0x923B91E1 (WebCore + 0x0008784d)
# 23 0x92c732d3 in .objc_class_name_AccessibilityObjectWrapper + 0x923B8C67 (WebCore + 0x000872d3)
# 24 0x92c7254f in .objc_class_name_AccessibilityObjectWrapper + 0x923B7EE3 (WebCore + 0x0008654f)
# 25 0x92e1a0c4 in .objc_class_name_AccessibilityObjectWrapper + 0x9255FA58 (WebCore + 0x0022e0c4)
# 26 0x92e19f5b in .objc_class_name_AccessibilityObjectWrapper + 0x9255F8EF (WebCore + 0x0022df5b)
# 27 0x9733eedb in .objc_class_name___CFx606449CPF + 0x971AF2AF (CoreFoundation + 0x0

 

[camealy]

We manage hundreds of Entourage users and probably 70-80% of them have this HTML email related crash. The only thing we have been able to tell them is turn off pictures and complex HTML which is a little crazy in today's email world.
If there is no fix now, is there one in the works? Or are we just going to have to wait for a new version of Office?

Thanks,

Kurt

 

[mridella]

It's truly terrible. 10.5.8 hasn't fixed it, neither has the latest Safari 4.0.4 or any of the numerous Apple software updates OR Office 12.2.3. We too have around 100 Mac users running Entourage, it's completely ridiculous that there isn't a fix yet. I can tell you that Entourage 13.0.3 (Web Services Edition) didn't help either. Wasted a lot of time rebuilding Entourage DBs, running OSX combo updaters, repairing permissions, testing on other machines and with new test user accounts...

 

[Diane Ross]

I'm working with Microsoft now to see if we can find a solution. I just
received a database from a user for testing and even though I don't have the
problem, I was able to see the crashes for some of the messages. So, does
this indicate something is happening to the messages they receive that is
causing the crashes? I found two comments users have made concerning this
issue.

1. I have discovered something that I suggest all entourage 2008 users check
if using entourage 2008 behind a proxy. If you find you are using a pac file
proxy configuration (Automatic proxy configuration) and you are finding
entourage crashing please switch over to a manual proxy configuration. I
found since switching over entourage has not crashed once.
2. I found something interesting, I was using my laptop at home today, vpn'd
into work and opened up entourage, not a single crash occurred. I'm
wondering if this issue could be caused by some sort of firewall rule at the
office.


--
Diane Ross, Microsoft Mac MVP
Entourage Help Page <http://www.entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://tinyurl.com/bzcrjy> <-- Entourage mailing list
Twitter: follow <http://twitter.com/entouragehelp>

 

[sjd]

Hi All,

I have noticed that disabling image download via the security tab in
Entourage does seem to stop the crash (fingers crossed)

Do we know if this will ever be fixed

TA

S

 

[Diane Ross]

I have noticed that disabling image download via the security tab in
Entourage does seem to stop the crash (fingers crossed)

Do we know if this will ever be fixed

I do know that both Apple and Microsoft are looking into this matter.

If you have the room, I would partition your drive and install Snow Leopard
and Office for testing. If the problem goes away then you should consider a
clean install of everything.

Snow Leopard plus Office takes approx 8GB of space. I would make the
partition around 20 GB to give you space for additional testing and for free
space needed by the OS.

--
Diane Ross, Microsoft Mac MVP
Entourage Help Page <http://www.entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://tinyurl.com/bzcrjy> <-- Entourage mailing list
Twitter: follow <http://twitter.com/entouragehelp>