Outlook 2011 does not work on OS X El Capitan

[jmecca09]

I'm posting this to alert users. Outlook 2011 does not work on OS X El Captian when you use exchange. It will work if you use other accounts; such as, imap, pop, etc. Microsoft is aware of the problem and the only work around is to use Yosemite.

https://support.microsoft.com/en-us/kb/3098396

 

[kch50428]

And ElCap has been in beta for how long, and Microsoft's only advice is "use Yosemite"?? C'mon Micorsoft... You should be better than that.

 

[jmecca09]

And ElCap has been in beta for how long, and Microsoft's only advice is "use Yosemite"?? C'mon Micorsoft... You should be better than that.

My thoughts exactly! Microsoft dropped the ball on this one.

Thankfully I run Parallels on my work machine, so I can still access Outlook 2013 for the functionality that I can't get in the Apple Mail and Calendar apps.

 

[route664]

yup.. i found that out the hard way. lucky for my company was testings office 365 and i was able to use outlook 2016.

 

[iN8ter]

My thoughts exactly! Microsoft dropped the ball on this one.

Thankfully I run Parallels on my work machine, so I can still access Outlook 2013 for the functionality that I can't get in the Apple Mail and Calendar apps.

They didn't drop the ball. They released Outlook 2016.

 

[jmecca09]

Yes the certainly did drop the ball. The majority of Mac users who use Outlook are still on 2011. They've had months to test bugs and have chosen not to fix the bugs. That is not a good example of putting customers first and therefore they dropped the ball. Also 2016 is very buggy as well on El Capitan, so your argument is invalid all around.

 

[Hendri Hendri]

And lync please ... I can't communicate with my office w/o lync ....

Posted via the iMore App for Android

 

[jmecca09]

And lync please ... I can't communicate with my office w/o lync ....

Posted via the iMore App for Android

I believe there was an update to Lync. I'm not sure if it fixed the issues because my office does not use it.

 

[Hendri Hendri]

I believe there was an update to Lync. I'm not sure if it fixed the issues because my office does not use it.

Nah .... i updated my lync, still can't sign in "no internet connection" ???

Posted via the iMore App for Android

 

[Sikosis]

We had a user on Office 2011 who upgraded to El Capitan and doing a rebuild of their Outlook database fixed it. This is connected to Exchange 2013 too.

I'm curious if anyone is having issues with Office 2016 and El Capitan ? Paul Thurrott said it's unusable, but I haven't noticed any issues yet.

"Office 2016 on El Capitan is unstable and virtually impossible to use on my machine; all of the apps crash multiple times a day. To top it off, I have had the error reporting mechanism crash (above image) while trying to send my crash log after Outlook bit the dust. The crashing is so bad that I cannot trust the apps to work long enough to accomplish anything meaningful which renders my Mac useless for daily tasks."

 

[GeorgePhx]

Sorry. Outlook does not work with anything. The issue I and many friends have is we will open outlook, use it and close it to the dock. When we click on it again, it will not open and we have to right-click and click on force close; Then reopen it again.

 

[Hendri Hendri]

I'm curious, anyone here using lync and cannot connect ? Or it just me who has this issue ?

Posted via the iMore App for Android

 

[Hendri Hendri]

Sorry. Outlook does not work with anything. The issue I and many friends have is we will open outlook, use it and close it to the dock. When we click on it again, it will not open and we have to right-click and click on force close; Then reopen it again.

Outlook 2016 and 365 is different ? My 365 has no issue for the outlook

Posted via the iMore App for Android

 

[kch50428]

Microsoft has released updates for Office 2011 to address the Outlook issue... Update your stuff..

 

[Muessig]

I'm so glad that MS released the update - I was trying to use my Mac at work and couldn't use any email services because everything would lock up! Bad form for MS to miss this bug, but at least it's fixed now!