This has been driving me crazy all day... any advice would be very gratefully received.
Background
My friend has got a reconditioned iMac with Mountain Lion fresh from Apple a few days ago. Her email is being hosted by Eapps. We can send and receive email with no problem using their web interface (Squirrel). She installed Office 2011 for Mac and everything was working fine, including all the Outlook functionality we tested (sending & receiving emails etc).
She then did some other setup (things like iCloud) and imported some contacts from an older version of Outlook. At some point during the day the following issue was noticed.
The Problem
Receiving email is working fine, but when we click "E-mail" (for a new message), "Reply", "Reply All" or "Forward" the button seems to do nothing. It is enabled and clicks, but nothing happens. If I run Outlook from the terminal like so:
> cd '/Applications/Microsoft Office 2011/Microsoft Outlook.app/Contents/MacOS'
> ./'Microsoft Outlook'
and click any one of those buttons I get the following error:
2013-11-16 16:32:42.551 Microsoft Outlook[245:707] [<MessageComposeViewController 0x7ac86a00> addObserver:<NSAutounbinderObservance 0x7acc6260> forKeyPath:@"infobars" options:0 context:0x7acbf850] was sent to an object that is not KVC-compliant for the "|Ô" property.
followed by a long stack trace (I can send the whole thing if anyone wants to see it). Outlook continues to work in every other way, but this error reappears whenever one of those buttons is clicked. I get the same behaviour if I invoke the same methods from the menu instead of the buttons.
In safe mode, everything works perfectly.
What we've tried:
- Deleted and recreated the email account, checking all details are correct.
- Created a new MacOS user and recreated the email account from that logon.
- Recorded all running processes in safe mode, booted back into full mode and systematically killed all processes that were not running in safe mode. We were able to validate that all the processes shown in Activity Viewer in full mode were also shown in safe mode; the issue was still present.
- Validated fonts and cleared out Library/Caches (we found a page on the Apple site that suggested this).
- Did a live chat with Apple support, who kicked the ball over to Microsoft's side.
Reinstalling Safari seems to be a common piece of advice for problems like this, but this seems to be non-trivial to do in Mountain Lion and I rather doubt it has anything to do with it (nothing in Safari has changed since Outlook was working AFAIK).
Does anyone have any ideas on this?
Recent Comments