Entourage 2008 crashes without VPN connection

[jodell]

I just upgraded from Office 2004 to 2008.

With Entourage 2004, I could connect to my Corporate exchange server without needing a VPN connection. I pointed the exchange server and public folder servers to the server name of the webmail server. I pointed the LDAP server to an AD server. This worked fine for 1 year -- I could download, read and write email with no problems.

After upgrading to office 2008, I found a nasty problem - each time Entourage would launch and attempt to download new mail, it would crash. After 12 hours of troubleshooting, I found that if I connected to VPN, Entourage would work as expected.

Has anyone else found this behavior?

I can post the crash report if necessary. During troubleshooting, I submitted the bug report 15-20 times at least so if anyone is looking at the crash report queue, they already know about it. :')

Thanks,
Jeff

 

[jodell]

Full text of crash report:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-01-21 21:48:02 -0800
Application Name: Microsoft Entourage
Application Bundle ID: com.microsoft.Entourage
Application Signature: OPIM
Application Version: 12.0.0.071130
Crashed Module Name: CoreFoundation
Crashed Module Version: unknown
Crashed Module Offset: 0x000c419a
Blame Module Name: CoreFoundation
Blame Module Version: unknown
Blame Module Offset: 0x000c419a
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0:

# 1 0x94af88e6 in _signgam + 0x9495F0E6 (libSystem.B.dylib + 0x000008e6)
# 2 0x934ae439 in __gTECMasterGlobals + 0x931C9E79 (CarbonCore + 0x00071439)
# 3 0x021b64e5 in LThread::Yield(LThread const*) + 0x00000027 (PowerPlantCore + 0x0000f4e5)
# 4 0x003f0c26 in __mh_execute_header + 0x003EFC26 (Microsoft Entourage + 0x003efc26)
# 5 0x021ab69b in LAttachment::Execute(long, void*) + 0x00000033 (PowerPlantCore + 0x0000469b)
# 6 0x021ab92c in LAttachable::ExecuteAttachments(long, void*) + 0x00000056 (PowerPlantCore + 0x0000492c)
# 7 0x012a3061 in LApplication:ostProcessEventsRAEL(OpaqueEventRef*, OpaqueEventTargetRef*, unsigned char) + 0x000000BB (PowerPlant + 0x00070061)
# 8 0x012a3292 in LApplication::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 0x0000018E (PowerPlant + 0x00070292)
# 9 0x9617a863 in .objc_class_name_IPMDFontRange + 0x95E51C43 (HIToolbox + 0x00007863)
# 10 0x96179c9d in .objc_class_name_IPMDFontRange + 0x95E5107D (HIToolbox + 0x00006c9d)
# 11 0x96179b02 in .objc_class_name_IPMDFontRange + 0x95E50EE2 (HIToolbox + 0x00006b02)
# 12 0x961a881c in .objc_class_name_IPMDFontRange + 0x95E7FBFC (HIToolbox + 0x0003581c)
# 13 0x9617ac1c in .objc_class_name_IPMDFontRange + 0x95E51FFC (HIToolbox + 0x00007c1c)
# 14 0x96179c9d in .objc_class_name_IPMDFontRange + 0x95E5107D (HIToolbox + 0x00006c9d)
# 15 0x9619608e in .objc_class_name_IPMDFontRange + 0x95E6D46E (HIToolbox + 0x0002308e)
# 16 0x96203444 in .objc_class_name_IPMDFontRange + 0x95EDA824 (HIToolbox + 0x00090444)
# 17 0x961ffc9e in .objc_class_name_IPMDFontRange + 0x95ED707E (HIToolbox + 0x0008cc9e)
# 18 0x012a2741 in LApplication:rocessEvents() + 0x000000FF (PowerPlant + 0x0006f741)
# 19 0x012a27cf in LApplication::Run() + 0x0000006D (PowerPlant + 0x0006f7cf)
# 20 0x00019c5c in __mh_execute_header + 0x00018C5C (Microsoft Entourage + 0x00018c5c)
# 21 0x000028ce in __mh_execute_header + 0x000018CE (Microsoft Entourage + 0x000018ce)
# 22 0x000027f5 in __mh_execute_header + 0x000017F5 (Microsoft Entourage + 0x000017f5)

X86 Thread State:
 eax: 0xffffffe1 ebx: 0x934ae266 ecx: 0xbfffecac edx:0x94af88e6
 edi: 0x00000000 esi: 0x00000000 ebp: 0xbfffece8 esp:0xbfffecac
  ss: 0x0000001f eip: 0x94af88e6 cs: 0x00000007 ds:0x0000001f
  es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00000206

Thread 1:

# 1 0x94af8a06 in _signgam + 0x9495F206 (libSystem.B.dylib + 0x00000a06)
# 2 0x94b80b7b in _signgam + 0x949E737B (libSystem.B.dylib + 0x00088b7b)
# 3 0x0219a265 in _MerpCreateSession + 0x00000B05 (merp + 0x00002265)
# 4 0x021998cd in _MerpCreateSession + 0x0000016D (merp + 0x000018cd)
# 5 0x02199954 in _MerpCreateSession + 0x000001F4 (merp + 0x00001954)
# 6 0x0219a40d in _MerpCreateSession + 0x00000CAD (merp + 0x0000240d)
# 7 0x94b29075 in _signgam + 0x9498F875 (libSystem.B.dylib + 0x00031075)
# 8 0x94b28f32 in _signgam + 0x9498F732 (libSystem.B.dylib + 0x00030f32)

X86 Thread State:
 eax: 0xffffffa6 ebx: 0x94b6f999 ecx: 0xb00a0a5c edx:0x94af8a06
 edi: 0x00006e6b esi: 0xc2efe8cf ebp: 0xb00a0ac8 esp:0xb00a0a5c
  ss: 0x0000001f eip: 0x94af8a06 cs: 0x00000007 ds:0x0000001f
  es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000202

Thread 2:

# 1 0x94afface in _signgam + 0x949662CE (libSystem.B.dylib + 0x00007ace)
# 2 0x94b29ced in _signg

 

[tsai.julia]

I just upgraded from Office 2004 to 2008.
With Entourage 2004, I could connect to my Corporate exchange server without needing a VPN connection. I pointed the exchange server and public folderservers to the server name of the webmail server. I pointed the LDAP serverto an AD server. This worked fine for 1 year -- I could download, read and write email with no problems.
After upgrading to office 2008, I found a nasty problem - each time Entourage would launch and attempt to download new mail, it would crash. After 12 hours of troubleshooting, I found that if I connected to VPN, Entourage would work as expected.
Has anyone else found this behavior?
I can post the crash report if necessary. During troubleshooting, I submitted the bug report 15-20 times at least so if anyone is looking at the crashreport queue, they already know about it. :')
Thanks,
Jeff

Funny, I have the same problem but with Entourage 2004. I recently
had to restore my hard drive after a hard drive replacement and I am
having the same problem crashing when I am directly connected to the
exchange server. It does not crash while I am connected through VPN.
I had no problems with Entourage 2004 prior to the hard drive failure
but I have the problem now. Spoke to the people from Entourage Help
and they said that any problem like this for 2004 will carry over to
2008 as well. I thought I would get rid of this problem by installing
2008 but it looks like you're having the same problem.