Entourage 2008 - crashes multiple times per day

[Rick_Wrightson]

where do i find the crash logs? i checked all my log folders and there are none from entourage.

Shape: when it crashes, a dialog box/window pops up asking if it ok to send the report to Microsoft. In the lower left of the box/window you will see a button for 'more info' (or something to that effect). When you click the button, the error log displays. You can copy and paste it to a post here. However, the error log info history is apparently erased each time Entourage is restarted so there is no cumulative error history residing anyplace. You have to grab it when it crashes.

 

[Diane Ross]

another day, another crash...(I guess it's time to go back in and set the
'work around'...here is the error report

Once was enough reporting the same crash over and over. There is nothing we
can do. As I mentioned both Apple and Microsoft is looking into this bug.
There is no fix other than some have found that turning off viewing HTML in
Entourage preferences helped.

 

[shape]

ok, here's my log. is this also the webcore bug?

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-09-11 17:05:49 -0400
Application Name: Microsoft Entourage
Application Bundle ID: com.microsoft.Entourage
Application Signature: OPIM
Application Version: 13.0.0.090609
Crashed Module Name: JavaScriptCore
Crashed Module Version: unknown
Crashed Module Offset: 0x0000382c
Blame Module Name: JavaScriptCore
Blame Module Version: unknown
Blame Module Offset: 0x0000382c
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0:

# 1 0x015a173d in CPooledSharedMemoryMgr::UpdatePoolList() + 0x00000023 (EntourageCore + 0x000d173d)
# 2 0x015a1c08 in CPooledSharedMemoryMgr::AllocateMemory(unsigned long, unsigned long*) + 0x00000076 (EntourageCore + 0x000d1c08)
# 3 0x015a1f85 in CSharedMemoryMgr::AllocateMemoryClear(unsigned long, unsigned long*) + 0x00000021 (EntourageCore + 0x000d1f85)
# 4 0x0156c6d3 in CDatabaseClientMgr:oFind(unsigned long, CSearchDescriptor*, CDBSelection*, long, unsigned short, unsigned long) + 0x0000003F (EntourageCore + 0x0009c6d3)
# 5 0x014f2dfd in CDatabaseClient::FindAllMatchesSearch(CSearchDescriptor*, CDBSelection*, short, unsigned char) const + 0x0000005D (EntourageCore + 0x00022dfd)
# 6 0x014e94d0 in UContactUtils::FindAllByEmailAddress(CStr const&, unsigned long) + 0x00000118 (EntourageCore + 0x000194d0)
# 7 0x014e9817 in UContactUtils::FindByEmail(CStr const&, CDBTransaction*, unsigned long) + 0x0000004B (EntourageCore + 0x00019817)
# 8 0x001d40cb in __mh_execute_header + 0x001D30CB (Microsoft Entourage + 0x001d30cb)
# 9 0x001dbb71 in __mh_execute_header + 0x001DAB71 (Microsoft Entourage + 0x001dab71)
# 10 0x001dab73 in __mh_execute_header + 0x001D9B73 (Microsoft Entourage + 0x001d9b73)
# 11 0x001e4f4e in __mh_execute_header + 0x001E3F4E (Microsoft Entourage + 0x001e3f4e)
# 12 0x001e43cf in __mh_execute_header + 0x001E33CF (Microsoft Entourage + 0x001e33cf)
# 13 0x0020535f in __mh_execute_header + 0x0020435F (Microsoft Entourage + 0x0020435f)
# 14 0x01e9c37c in CTableMgr::SetPreviewItem(Store::CRecordBase*) + 0x00000114 (EntourageLegacy + 0x0016337c)
# 15 0x01e9c9c9 in CTableMgr::SyncPreviewPane() + 0x0000006F (EntourageLegacy + 0x001639c9)
# 16 0x01e9adac in CTableMgr:oDeferred(long) + 0x00000070 (EntourageLegacy + 0x00161dac)
# 17 0x01d5da38 in CCategorizableTableMgr:oDeferred(long) + 0x00000026 (EntourageLegacy + 0x00024a38)
# 18 0x0279ed5b in CDeferrable:ispatchIfReady(long, long) + 0x000000D3 (PowerPlantCore + 0x00001d5b)
# 19 0x0279eee3 in CDeferrable:evoteTimeToDeferrables() + 0x00000103 (PowerPlantCore + 0x00001ee3)
# 20 0x01331050 in LApplication:ostProcessEventsRAEL(OpaqueEventRef*, OpaqueEventTargetRef*, unsigned char) + 0x0000010A (PowerPlant + 0x00070050)
# 21 0x01331232 in LApplication::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 0x0000018E (PowerPlant + 0x00070232)
# 22 0x934a813d in .objc_class_name_IPMDFontRange + 0x9317D4FD (HIToolbox + 0x0000813d)
# 23 0x934a757b in .objc_class_name_IPMDFontRange + 0x9317C93B (HIToolbox + 0x0000757b)
# 24 0x934a73e0 in .objc_class_name_IPMDFontRange + 0x9317C7A0 (HIToolbox + 0x000073e0)
# 25 0x934d5d54 in .objc_class_name_IPMDFontRange + 0x931AB114 (HIToolbox + 0x00035d54)
# 26 0x934a84f6 in .objc_class_name_IPMDFontRange + 0x9317D8B6 (HIToolbox + 0x000084f6)
# 27 0x934a757b in .objc_class_name_IPMDFontRange + 0x9317C93B (HIToolbox + 0x0000757b)
# 28 0x934c3ecc in .objc_class_name_IPMDFontRange + 0x9319928C (HIToolbox + 0x00023ecc)
# 29 0x93530a6c in .objc_class_name_IPMDFontRange + 0x93205E2C (HIToolbox + 0x00090a6c)
# 30 0x9352d2c2 in .objc_class_name_IPMDFontRange + 0x93202682 (HIToolbox + 0x0008d2c2)
# 31 0x013306e1 in LApplication:rocessEvents() + 0x000000FF (PowerPlant + 0x0006f6e1)
# 32 0x0133076f in LApplication::Run() + 0x0000006D (PowerPlant + 0x00

 

[Diane Ross]

Yes! There is no known fix at this time. Sorry!

 

[shape]

ok, well can you tell me the best way to downgrade to entourage 12.2.1? will my database work or cant i downgrade? i cant deal with crashes every 2 hrs.

thanks

 

[Diane Ross]

ok, well can you tell me the best way to downgrade to entourage 12.2.1? will
my database work or cant i downgrade? i cant deal with crashes every 2 hrs.

The problem is at the system level. You would need to re-install Leopard
then update to 10.5.7. Do not update to Safari 4. Install Office and quit at
12.1.5. (do I hear a huge groan?)

If you had an external where you could do this, it would be the best option.
This way you can test to be sure this is working without having to do a
complete redo of everything until you are sure it's not crashing.

 

[shape]

10.5.7? but entourage 12.21 worked fine. it's v13 that crashes. i definitely dont have a spare week to spend reinstalling the OS. that's like choosing to replace all the inner pipes in your home just b/c you have a minor leaky faucet def not an option.

 

[Diane Ross]

10.5.7? but entourage 12.21 worked fine. it's v13 that crashes. i definitely
dont have a spare week to spend reinstalling the OS. that's like choosing to
replace all the inner pipes in your home just b/c you have a minor leaky
faucet def not an option.

When you upgraded to v13 of Entourage it upgraded your Identity. It cannot
be used by 12.2.1. You could try exporting the data then import it into
Entourage after you remove Office v13 then reinstalling 12.2.1.

If you had backups, you could drag those back and it would save time.

 

[shape]

hmm, ok thanks, that's what i figured. so if i went back to v12 i could do it by importing the new data? i do have backups but i would still lose all my new data since the upgrade.

 

[Diane Ross]

hmm, ok thanks, that's what i figured. so if i went back to v12 i could do it
by importing the new data? i do have backups but i would still lose all my new
data since the upgrade.

You could not import the Identity, but you could export the data as .rge and
import that data. This way you don't loose anything.

You can't go backwards using import from a program. Hope this is clear.

 

[Michel Bintener]

You could not import the Identity, but you could export the data as .rge and
import that data. This way you don't loose anything.

And to do so, you need to go to File>Export and choose to export your data
as an Entourage archive. The resulting archive file (in .rge format) can
then be imported into Entourage again using the File>Import dialogue.

 

[shape]

ok, thanks

 

[Amanda Turner]

I have Entourage for Mac 2008 v12.2.1 ( 090605)
I have noticed people taking about v13.

I am also having numerous crashing during the day with the following error
log

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-10-01 18:09:15 +1000
Application Name: Microsoft Entourage
Application Bundle ID: com.microsoft.Entourage
Application Signature: OPIM
Application Version: 12.2.0.090605
Crashed Module Name: JavaScriptCore
Crashed Module Version: unknown
Crashed Module Offset: 0x00004b29
Blame Module Name: JavaScriptCore
Blame Module Version: unknown
Blame Module Offset: 0x00004b29
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

How do I get the v13 and will it fix the constant crashing I am having

Regards

Amanda

 

[Diane Ross]

I have Entourage for Mac 2008 v12.2.1 ( 090605)
I have noticed people taking about v13.

V13 is the EWS version of Entourage for Exchange users. If you don't have
Exchange you don't need this version.

I am also having numerous crashing during the day with the following error
log

Crashed Module Name: JavaScriptCore
Crashed Module Version: unknown
Crashed Module Offset: 0x00004b29
Blame Module Name: JavaScriptCore
Blame Module Version: unknown

This is a known bug for some users. WebCore is part of WebKit which is the
Safari engine available for use in Mac OS X applications. Entourage uses it
to render HTML messages. Microsoft & Apple are investigating the
WebKit-related crashing. (JavaScriptCore is a part of WebKit)

We have a few options that works for some users, but for many these do not
work. A "Erase & Install" might fix it. If you had a second drive you could
try it there. Install the OS then update. Then install Office and update.

WebCore involved in crashes

<http://tinyurl.com/nchetu>

Possible workaround for crashes involving Webcore

<http://tinyurl.com/nrt45r>