Applications crash on launch in Snow Leopard

[theseek3r]

Hello,

I have a Macbook Pro i7 with Snow Leopard (10.6.6). I have installed many different applications but several of them, such as Word/Office 2011 and Epson Scan along with other minor apps keep crashing when I launch them with my admin user logged in. I tried repairing the disk permissions and verified/resolved duplicate fonts just in case, but the problem persisted.

So, I created a test user with no admin privileges and I managed to run them, but it's no serious workaround to switch users every time I need to work on Word or scan something...

Any help is much appreciated.

The error I get from Word 2011 is the following:

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2011-03-09 16:57:38 +0200
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 14.0.2.101115
Crashed Module Name: OutlookLegacy
Crashed Module Version: unknown
Crashed Module Offset: 0x00002068
Blame Module Name: OutlookLegacy
Blame Module Version: unknown
Blame Module Offset: 0x00002068
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409 
Crashed thread: 0


Thread 0 crashed:

#  1  0x0bf73068 in CTimeInfo::CTimeInfo() + 0x00000134 (OutlookLegacy + 0x00002068)
#  2  0x0c21ff27 in _SetLegacyWindowAsFloating + 0x00000908 (OutlookLegacy + 0x002aef27)
#  3  0x8fe0ed6d in  ( + 0x00000000)
#  4  0x8fe0d31e in  ( + 0x00000000)
#  5  0x8fe0d3d1 in  ( + 0x00000000)
#  6  0x8fe0200b in  ( + 0x00000000)
#  7  0x8fe0b299 in  ( + 0x00000000)
#  8  0x993a68a8 in _dlopen + 0x00000042 (libSystem.B.dylib + 0x000078a8)
#  9  0x9835713a in __CFBundleDlfcnLoadFramework + 0x000000DA (CoreFoundation + 0x0009c13a)
# 10  0x9831cb13 in __CFBundleLoadExecutableAndReturnError + 0x000005F3 (CoreFoundation + 0x00061b13)
# 11  0x9831c511 in _CFBundleLoadExecutable + 0x00000021 (CoreFoundation + 0x00061511)
# 12  0x9831d189 in _CFBundleGetFunctionPointerForName + 0x00000039 (CoreFoundation + 0x00062189)
# 13  0x0003e468 in _SetupUI_IsActivityAllowed + 0x0000DEC5 (MicrosoftSetupUI + 0x00011468)
# 14  0x0003e91a in _SetupUI_IsActivityAllowed + 0x0000E377 (MicrosoftSetupUI + 0x0001191a)
# 15  0x00033645 in _SetupUI_IsActivityAllowed + 0x000030A2 (MicrosoftSetupUI + 0x00006645)
# 16  0x00031cea in _SetupUI_IsActivityAllowed + 0x00001747 (MicrosoftSetupUI + 0x00004cea)
# 17  0x0003064e in _SetupUI_IsActivityAllowed + 0x000000AB (MicrosoftSetupUI + 0x0000364e)
# 18  0x000302ad in  (MicrosoftSetupUI + 0x000032ad)
# 19  0x000305cb in _SetupUI_IsActivityAllowed + 0x00000028 (MicrosoftSetupUI + 0x000035cb)
# 20  0x0eecc8e7 in __mh_execute_header + 0x000028E7 (Microsoft Word + 0x000028e7)
# 21  0x0eecc817 in __mh_execute_header + 0x00002817 (Microsoft Word + 0x00002817)
# 22  0x0eecc7f6 in __mh_execute_header + 0x000027F6 (Microsoft Word + 0x000027f6)

X86 Thread State:
 eax: 0x00000006  ebx: 0x0bf72f45  ecx: 0xbfffed2c  edx:0x06008a60
 edi: 0x00000006  esi: 0x00000000  ebp: 0xbfffeec8  esp:0xbfffed40
  ss: 0x0000001f  eip: 0x0bf73068   cs: 0x00000017   ds:0x0000001f
  es: 0x0000001f   fs: 0x00000000   gs: 0x00000037  eflags:0x00010282


Thread 1:

#  1  0x993c6982 in ___kevent + 0x0000000A (libSystem.B.dylib + 0x00027982)
#  2  0x993c6559 in __dispatch_queue_invoke + 0x000000A3 (libSystem.B.dylib + 0x00027559)
#  3  0x993c62fe in __dispatch_worker_thread2 + 0x000000F0 (libSystem.B.dylib + 0x000272fe)
#  4  0x993c5d81 in __pthread_wqthread + 0x00000186 (libSystem.B.dylib + 0x00026d81)
#  5  0x993c5bc6 in _start_wqthread + 0x0000001E (libSystem.B.dylib + 0x00026bc6)

X86 Thread State:
 eax: 0x0000016b  ebx: 0x993c6fd6  ecx: 0xb0080d5c  edx:0x993c6982
 edi: 0xa0bda1ec  esi: 0xb0080ed8  ebp: 0xb0080ef8  esp:0xb0080d5c
  ss: 0x0000001f  eip: 0x993c6982   cs: 0x00000007   ds:0x0000001f
  es: 0x0000001f   fs: 0x0000001f   gs: 0x00000037  eflags:0x00000246


Thread 2:

#  1  0x993c5a12 in ___workq_kernreturn + 0x0000000A (libSystem.B.dylib + 0x00026a12)
#  2  0x993c5bc6 in _start_wqthread + 0x0000001E (libSystem.B.dylib + 0x00026bc6)

X86 Thread State:
 eax: 0x00100170  ebx: 0x993c5c09  ecx: 0xb0102f6c  edx:0x993c5a12
 edi: 0x05800118  esi: 0xb0103000  ebp: 0xb0102fc8  esp:0xb0102f6c
  ss: 0x0000001f  eip: 0x993c5a12   cs: 0x00000007   ds:0x0000001f
  es: 0x0000001f   fs: 0x0000001f   gs: 0x00000037  eflags:0x00000286

... etc etc etc...

Operating System Information
Operating System: Mac OS X 10.6.6 (Build 10J567)
CPU: Intel Core Duo, Number: 4, Speed: 2147 MHz
gestaltPhysicalRAMSizeInMegabytes err = 0, result = 4096 MB
gestaltSystemVersion err = 0, result = 0x1066
Screen: 1680 x 1050, depth = 32, ltbr = 0, 0, 1050, 1680

Microsoft Application Information:
Error Reporting UUID: 53EE693C-7959-48B8-A737-AA16A1B213C9
Time from launch: 0 hours, 0 minutes, 0 seconds
Total errors on this client: 18

 

[wrldwzrd89]

Clearly, based on that error log you have a module called OutlookLegacy that is causing the problem. However, finding it and removing it probably won't be easy.

 

[theseek3r]

Clearly, based on that error log you have a module called OutlookLegacy that is causing the problem. However, finding it and removing it probably won't be easy.

Thanks for your reply. However, I don't see the relevance of this OutlookLegacy module with the other apps crashing on launch, so I guess there's something else lying behind that.

I'll be glad if there are any other suggestions.

Thank you

 

[wrldwzrd89]

Thanks for your reply. However, I don't see the relevance of this OutlookLegacy module with the other apps crashing on launch, so I guess there's something else lying behind that.

I'll be glad if there are any other suggestions.

Thank you

Looking at the stack trace more closely, whichever version of Word you're using is loading this buggy OutlookLegacy module, failing to do so, and thus crashing. It's also possible that OutlookLegacy may have registered a so-called "global hook" - meaning that EVERY application on your Mac causes it to get loaded, too. This behavior, combined with bugs in that particular module, would explain your crashing symptoms.

 

[theseek3r]

Looking at the stack trace more closely, whichever version of Word you're using is loading this buggy OutlookLegacy module, failing to do so, and thus crashing. It's also possible that OutlookLegacy may have registered a so-called "global hook" - meaning that EVERY application on your Mac causes it to get loaded, too. This behavior, combined with bugs in that particular module, would explain your crashing symptoms.

Thanks for your insight. But how does this relate to the fact that with a different user, everything runs fine? And, what would be your suggestions to resolve the problem?

 

[wrldwzrd89]

Thanks for your insight. But how does this relate to the fact that with a different user, everything runs fine? And, what would be your suggestions to resolve the problem?

If it runs fine in a test user, then the next place to look is your Library folder. Odds are the module in question is there - probably in Library -> Application Support.

 

[theseek3r]

If it runs fine in a test user, then the next place to look is your Library folder. Odds are the module in question is there - probably in Library -> Application Support.

I see... So I would have to remove it from its place?

 

[wrldwzrd89]

I see... So I would have to remove it from its place?

Yes, but removing the module itself may not be enough. You should also track down what application installed it (my guess is that it's an Outlook for Windows importer of some sort) and either update or remove it, too.