Why is my Entourage suddenly crashing?

[Richard H]

Can anyone throw any light on why my Entourage application has recently
begun crashing on the first run (OK on when immediately run again) ?

Here is the latest Crash Log:

Date/Time: 2006-09-30 15:00:43 +0100
OS Version: 10.2.8 (Build 6R73)
Host: My-Computer.local.

Command: Microsoft Entourage
PID: 519

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054

Thread 0:
#0 0x90073ba8 in mach_msg_trap
#1 0x90005ed0 in mach_msg
#2 0x9022a720 in SwitchContexts
#3 0x90224fc8 in YieldToThread
#4 0x0073eeec in 0x73eeec
#5 0x005099e8 in 0x5099e8
#6 0x0070535c in 0x70535c
#7 0x00705174 in 0x705174
#8 0x00700e90 in 0x700e90
#9 0x0026b20c in 0x26b20c
#10 0x00700c78 in 0x700c78
#11 0x002681cc in 0x2681cc

Thread 1:
#0 0x90073ba8 in mach_msg_trap
#1 0x90005ed0 in mach_msg
#2 0xc000a954 in __ape_internal
#3 0xc0001330 in __ape_agent
#4 0x90020c28 in _pthread_body

Thread 2:
#0 0x90073ba8 in mach_msg_trap
#1 0x90005ed0 in mach_msg
#2 0x9022a720 in SwitchContexts
#3 0x90224fc8 in YieldToThread
#4 0x90243128 in SetThreadState
#5 0x9026d948 in SetThreadStateEndCritical
#6 0x0073fcd8 in 0x73fcd8
#7 0x0073e8d4 in 0x73e8d4
#8 0x0073e7f8 in 0x73e7f8
#9 0x0073eb6c in 0x73eb6c
#10 0x007400d4 in 0x7400d4
#11 0x9023bba8 in CooperativeThread
#12 0x90020c28 in _pthread_body

Thread 3:
#0 0x9003e9a8 in semaphore_wait_signal_trap
#1 0x9003e7c4 in _pthread_cond_wait
#2 0x9023317c in TSWaitOnSemaphoreCommon
#3 0x9024890c in AsyncFileThread(void*)
#4 0x90020c28 in _pthread_body

Thread 4:
#0 0x9003130c in accept
#1 0x03652cd4 in FWaitForConnection
#2 0x008561e4 in 0x8561e4
#3 0x0087fa30 in 0x87fa30
#4 0x0087fbb8 in 0x87fbb8
#5 0x902b81e8 in _MP_CFMTaskProc
#6 0x9025e364 in PrivateMPEntryPoint
#7 0x90020c28 in _pthread_body

Thread 5:
#0 0x9002560c in recvfrom
#1 0x03652e90 in FReceiveMessage
#2 0x0085635c in 0x85635c
#3 0x0087fd9c in 0x87fd9c
#4 0x0087fefc in 0x87fefc
#5 0x902b81e8 in _MP_CFMTaskProc
#6 0x9025e364 in PrivateMPEntryPoint
#7 0x90020c28 in _pthread_body

Thread 6:
#0 0x90042588 in semaphore_timedwait_signal_trap
#1 0x9003e7b4 in _pthread_cond_wait
#2 0x902a0d4c in MPWaitOnSemaphore
#3 0x00880068 in 0x880068
#4 0x902b81e8 in _MP_CFMTaskProc
#5 0x9025e364 in PrivateMPEntryPoint
#6 0x90020c28 in _pthread_body

Thread 7:
#0 0x90073ba8 in mach_msg_trap
#1 0x90005ed0 in mach_msg
#2 0x90148938 in __CFRunLoopRun
#3 0x90180f04 in CFRunLoopRunSpecific
#4 0x94652f80 in HALRunLoop::OwnThread(void*)
#5 0x946591e0 in CAPThread::Entry(CAPThread*)
#6 0x90020c28 in _pthread_body

Thread 8:
#0 0x9000508c in syscall
#1 0x90515d0c in BSD_waitevent
#2 0x905156dc in CarbonSelectThreadFunc
#3 0x90020c28 in _pthread_body

Thread 9:
#0 0x9003e9a8 in semaphore_wait_signal_trap
#1 0x9003e7c4 in _pthread_cond_wait
#2 0x9051dbf0 in CarbonOperationThreadFunc
#3 0x90020c28 in _pthread_body

Thread 10:
#0 0x9003e9a8 in semaphore_wait_signal_trap
#1 0x9003e7c4 in _pthread_cond_wait
#2 0x905259e0 in CarbonInetOperThreadFunc
#3 0x90020c28 in _pthread_body

Thread 11 Crashed:
#0 0x00430ce4 in 0x430ce4
#1 0x00441668 in 0x441668
#2 0x00440364 in 0x440364
#3 0x0043fcdc in 0x43fcdc
#4 0x0046c000 in 0x46c000
#5 0x00381f4c in 0x381f4c
#6 0x00380080 in 0x380080
#7 0x0038a3dc in 0x38a3dc
#8 0x0038a38c in 0x38a38c
#9 0x0038ced8 in 0x38ced8
#10 0x0038a830 in 0x38a830
#11 0x0038a7d0 in 0x38a7d0
#12 0x003892c4 in 0x3892c4
#13 0x003819d0 in 0x3819d0
#14 0x003814a8 in 0x3814a8
#15 0x0037e58c in 0x37e58c
#16 0x0037fa7c in 0x37fa7c
#17 0x0046ae3c in 0x46ae3c
#18 0x0046eefc in 0x46eefc
#19 0x0028070c in 0x28070c
#20 0x007400d4 in 0x7400d4
#21 0x9023bba8 in CooperativeThread
#22 0x90020c28 in _pthread_body

Thread 12:
#0 0x90073ba8 in mach_msg_trap
#1 0x90005ed0 in mach_msg
#2 0x9022a720 in SwitchContexts
#3 0x90224fc8 in YieldToThread
#4 0x0073eeec in 0x73eeec
#5 0x004efff0 in 0x4efff0
#6 0x00631430 in 0x631430
#7 0x006317b0 in 0x6317b0
#8 0x90514588 in CarbonCallBackNow
#9 0x9051595c in WaitForSyncDone
#10 0x90511814 in RecvData
#11 0x9051305c in OTRcv
#12 0x0062f480 in 0x62f480
#13 0x0062f5c0 in 0x62f5c0
#14 0x0062d1e0 in 0x62d1e0
#15 0x0061a588 in 0x61a588
#16 0x004f0d48 in 0x4f0d48
#17 0x004f0c38 in 0x4f0c38
#18 0x004f12ec in 0x4f12ec
#19 0x004a030c in 0x4a030c
#20 0x00499248 in 0x499248
#21 0x00499100 in 0x499100
#22 0x0046ae3c in 0x46ae3c
#23 0x0046b09c in 0x46b09c
#24 0x0046f0a0 in 0x46f0a0
#25 0x0028070c in 0x28070c
#26 0x007400d4 in 0x7400d4
#27 0x9023bba8 in CooperativeThread
#28 0x90020c28 in _pthread_body

Thread 13:
#0 0x90073ba8 in mach_msg_trap
#1 0x90005ed0 in mach_msg
#2 0x9022a720 in SwitchContexts
#3 0x90224fc8 in YieldToThread
#4 0x0073eeec in 0x73eeec
#5 0x004efff0 in 0x4efff0
#6 0x00631430 in 0x631430
#7 0x006317b0 in 0x6317b0
#8 0x90514588 in CarbonCallBackNow
#9 0x9051595c in WaitForSyncDone
#10 0x90511814 in RecvData
#11 0x9051305c in OTRcv
#12 0x0062f480 in 0x62f480
#13 0x0062f5c0 in 0x62f5c0
#14 0x0062d1e0 in 0x62d1e0
#15 0x0061a588 in 0x61a588
#16 0x004f0d48 in 0x4f0d48
#17 0x004f0c38 in 0x4f0c38
#18 0x004f15e8 in 0x4f15e8
#19 0x0049ff60 in 0x49ff60
#20 0x00498f6c in 0x498f6c
#21 0x0046ae3c in 0x46ae3c
#22 0x0046b09c in 0x46b09c
#23 0x0046f0a0 in 0x46f0a0
#24 0x0028070c in 0x28070c
#25 0x007400d4 in 0x7400d4
#26 0x9023bba8 in CooperativeThread
#27 0x90020c28 in _pthread_body

PPC Thread State:
srr0: 0x00430ce4 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x20000000 lr: 0x00441668 ctr: 0x90003a40 mq: 0x00000000
r0: 0x00441668 r1: 0xf068bbc0 r2: 0x00d2a000 r3: 0x00000000
r4: 0x00000002 r5: 0x00000000 r6: 0x00000449 r7: 0x00000000
r8: 0x00046010 r9: 0xa0223308 r10: 0x04a3e010 r11: 0x04a3e000
r12: 0x90003a40 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xf068ca20 r22: 0x03cead6c r23: 0x03ce8ed8
r24: 0x03ce8ed8 r25: 0x04a36ec0 r26: 0xf068c3c0 r27: 0x04a77fa9
r28: 0x00000002 r29: 0x00bc9478 r30: 0xf068c3c0 r31: 0x00000000


TIA

 

[gapoirrier]

I would say you probably have some corruption in your database, backup
your data for safety sake and then do a rebuild! go to this web page
for instructions www.entourage.mvps.org

 

[Mickey Stevens]

If you have Entourage 2004, try starting up with the Shift key held down;
that will disable schedules. Otherwise, try unplugging your computer from
the internet before launching Entourage.

If that helps, it could be a corrupt mail message causing the problem.
Recently, malformed junk mail has exploited a bug in the Junk Mail Filter
included with Entourage X and 2001 that causes the entire program to crash
when Entourage attempts to download and process the message. Microsoft has
posted a workaround at their web site:
<http://support.microsoft.com/?kbid=837065>

Entourage 2004 includes improvements that allows it to download most of the
commonly-received junk messages that crashed earlier versions. The latest
updates for Office X provide comparable fixes. Make sure your version of
Office is fully up-to-date.
<http://home.earthlink.net/~mickey.stevens/tutorials/update.html>

Be aware that there are some types of messages that will crash any version
of Entourage regardless of whether the Junk Filter is turned on or off. If
you are crashing on receiving mail, it is likely happening because of a
corrupt message on the server. Work through the steps on the
"Crashes" page on The Entourage Help Page to resolve the problem.
Basically, you need to use an alternate interface like web mail to delete
the message before you can restore access through Entourage.
<http://www.entourage.mvps.org/troubleshoot/send_receive/crashes_hangs.html>

 

[neon_bikini]

I'm experiencing a font warning from Suitcase whenever I view Entoruage
emails using specific fonts (advertisement emails, groups emails from
yahoo, etc.). The strange thing, these fonts are already activated by
Suitcase and in my system folder!

I'm using 10.2.8 on my TiG4 667 with Suitcase 10.2.2 and Entorugae
10.1.1. I've used this set up since I bought the laptop and its worked
fine. I recently reinstalled the system (one month ago), but did not
reinstall the applications since its such a drama to get everything
back the way it was. Suitcase and Entoruage are the worst to restore.

I posted to the Extensis forum with this problem. A reader suggested:

To also fix the Microsoft Font issues you can also delete the Microsoft
Font Cache files. First quite out of all the MS Applications.
Quit Entourage & try deleting com.microsoft.browserfont.cache & Tasman
Broser.cache files from <Harddisk>/Users/Home folder (Folder with a Home
icon) /Library/Caches.

My system does not have these cache files. Is this a possible cause of
Entourage not recognizing the fonts that are currently running through
the system and Suitcase? If they're not there, then why is Entourage
not making them?