Outlook for Mac Does Not Work on OS X 10.10 (Yosemite Public Beta)

Anonymous
2014-07-26T04:33:23+00:00

Outlook launches without a Home Screen.

Menu Items are accessible and function properly (i.e. compose and send email, access Accounts etc.).

However, Home Screen does not render and you cannot see (or access) Mailboxes, Calendar, Contacts etc.

Appreciate that this is an issue with Public Beta Version but Apple has now issued this to One Million Mac Users and plenty of Microsoft Users rely on Outlook for Mac so, will need to be resolved.

Outlook | MacOS | Legacy Outlook for Mac | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

68 answers

Sort by: Newest
  1. Anonymous
    2014-10-24T03:23:42+00:00

    I have downloaded the update and applied it to my machine. The symptoms remain the same. I have now gone back to the in-house networking team and reviewed the network settings for connecting to our exchange server. The network team has given me a completely different set of network settings for the Exchange endpoint.

    And now Outlook for Mac is working for me. Hooray!

    I suspect that the problem has been a combination of new software and old network settings. It's hard to pinpoint precisely.

    I'm very grateful to all who have provided assistance and encouragement with sorting out this problem.

    Thanks, and cheers,  S t u a r t .

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-10-23T21:06:43+00:00

    I too unhappily had 14A389 installed. The solution was to run the brand new Office update (version 14...).  I'm thinking that Office and Yosemite couldn't get along, MS received complaints, and created an update to handle the problem. I can now search for emails again using Outlook with an Exchange server.  BTW, MS should not create an update file for Office that requires one to jump through multiple hoops! I had to kill the Microsoft Database Daemon and rename the SyncServicesAgent before the update would run. Shouldn't the update kill processes that get in the way?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-10-23T09:37:39+00:00

    Hi, Bruce

    Thanks for your insight. I checked my version of Yosemite, and was (sort of) disappointed to find that it is the Final GM Worldwide Release (14A389). I was hoping you'd found it, but alas I'm still stuck with a broken Outlook under Yosemite.

    Cheers,  S t u a r t .

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-10-23T05:32:55+00:00

    Hi All, I just discovered something fascinating and am posting here in case this helps anyone else. It turns out that when I visited the OS X App Store and clicked the link to download and install Yosemite a few days after the general release, I assumed I was getting Apple's public release, but it actually downloaded an early Beta version of Yosemite. Why it did this I have no idea. I only discovered this now because I kept checking the Update page on the App Store, and each time I  was prompted to download a newer Beta version. So I've now downloaded and installed Beta versions 1, 2, 3, 4, 5 and finally Beta 6. Google tells me that Beta 6 was the last Developer release prior to the final GM release. It's official version number was: OS X 10.10 (14A388b). Whereas the final FINAL GM worldwide release is OS X 10.10 (14A389). The point being in my car that my issues with Outlook occurred when I was still running one of the earliest Beta version (1 or 2, not sure which). As this thread shows, others were having issues with Outlook up thru version 3, and by version 4 issues seem to have abated almost entirely.

    So - if you're experiencing issues, one thing to be sure to do before trying other workarounds is to use System Information to check your OS X version of Yosemite. If you, like me, somehow ended up with an early Beta installed on your system, it might explain why you're having issues. And these issues might be resolved by upgrading to at least Beta 6, and even better, the final release - "14A389."

    -Bruce

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-10-23T00:53:20+00:00

    Hi, Bruce

    Thank you very much for your reply.

    I must be having a different problem. I haven't experienced the missing window problem.

    I tried your method as outlined in you recent post: I deleted the .plist file; started Outlook with the Option key; create a new identity; made the new identity the default; close the Database Rebuild app; open Outlook; created a new account through the preferences>account dialog. Nothing.

    The account always has an orange "ball" next to the account indicating that it cannot connect. And then I start getting repeated visits from the "autodiscover" dialog box I mentioned in my previous post.

    Again, thanks for your reply. But no luck yet.

    We do have a flaky network here at work with really convoluted connections and proxies. I'll do a little more investigation around the network configuration.

    Cheers,  S t u a r t .

    Was this answer helpful?

    0 comments No comments