If I just launch it and quit, it's fine, but if I've been running it for a few hours or a few days (I leave it running for days on end usually, not rebooting or quitting very often), when I quit Outlook, it almost always crashes (though it looks like it's quit just fine) and I get the Microsoft Error Reporting (I always send in the crash information).  I've rebuilt my database and Outlook otherwise works just fine, it's just that it bugs me that it keeps crashing when I choose quit (or rather press Cmd-Q).

Any ideas on how to fix this, or at least troubleshoot it more?  I'm running 10.8.2 (but this has been going on since 10.7.x) and I don't see anything in Console's DiagnosticsReports directory (no crashes for Outlook, though a few crash dumps from other applications that have crashed in the past).

Thanks!
The only thing I can think of that has changes recently is that I updated the Microsoft Error Reporting a couple days ago, but now on 2 different Macbook Pro's (both running Mountain Lion), Outlook freezes with the beach ball.   If I wait several minutes it eventually unfreezes, but since email is critical, its very frustrating.  I've noticed this behaviour on 2 different machines today.   Both are connected to an Exchange server and multiple IMAP server as well.   Any ideas?

I wish to block unsolicited messages from messenger, people who are not on my contact list or ever been on my contact list. I understand that people not on contact list are supposedly unable to send messages since I am using 2011 Live version, but this has clearly failed miserably as everyone I know gets unsolicited messages from various people using various other IM systems. Reporting abuse has no effect. These people need to have their ISP address blocked, not just their account, otherwise they simply create another account name. It is your responsibility to keep spammers and abusers out of your messenger system and you seem little inclined to do so, indeed, several people have asked this question on different forums including your own, and yet no adequate response has been given by your company. This is appalling lack of service.

 

This error report: Microsoft Error Reporting log version: 2.0  
Error Signature: Exception: EXC_BAD_ACCESS Date/Time: 2012-10-02 13:48:43 +0000 Application Name: Microsoft Outlook Application Bundle ID: com.microsoft.Outlook Application Signature: OPIM Application Version: 14.2.2.120421, etc.