Hi, I have some trouble connecting the Outlook to our Exchange Server. On that same Mac I configure the Mac Mail to connect to Exchange and went OK. I configure the Outlook using the exchange connection and cannot connect, user account (username password) is correct but still cant connect history: few days back it was connected but recently for unknown reason its just stop synchronizing. I tried comparing the outlook configuration on the working MAC it was the same but still can't connect. We tried reinstalling the Office, do some Office Update but still same. Any idea shared is highly appreciated.

Regards, mobdoc. Ahh,.local rears its ugly head again.local is not a valid TLD, and Mac OS X handles it differently than Windows. Here are Microsoft's articles recommending against the use of.local 'Using single label names or unregistered suffixes, such as.local, is not recommended' The dsachetuil command should be as shown below, so I apologize for that typo on my part (I've fixed it above in my prior replies). Dsacheutil -q host -a name fqdn.ofyourserver.com or in your case dsacheutil -q host -a name server.domain.local. Hi Oliver - What version of Exchange are you using and what OS X version?

Microsoft has some useful recommendations for troubleshooting which might apply to you: Outlook 2011 also had issues with corrupted identities and databases which would require using the DB Utility to clean up or a completely new install and setup removing all previous preferences files. Some of the issues you reported were fixed in an update for Mavericks and Yosemite a while back. You can use this free utility as an Administrator to test Exchange connections. As an FYI - If you're an Office 365 user, you can get access to Outlook 2016 for Mac which my team reports is performing well. The standalone version of this will be available to the public in September.

Hope this information helps you out! Please let me know if I can be of further assistance.. Hi Megan, Thanks for your reply, yes its Yosemite 10.10.2 and were using Exchange 2007 SP3, we have a couple of Mac users using Outlook 2011 and they are working fine connecting to our exchange server except this one. We tried reinstalling a couple of times, update the Office, uninstall the office and install back again, and once we tried adding account in outlook using exchange connection we got yellow icon and account is not successfully added to outlook. Note: it is same configuration we did to other Mac Users who is using Outlook, users credentials are correct because we can login using that account through OWA.

Regards, Oliver. There is a lot of information being tossed about but much of it is simply not on point, sorry. For an Exchange account with Outlook for Mac never ever ever do a database rebuild. I'm speaking from many years of experience with this. A rebuilt Outlook for Mac database will fail again within days to a couple weeks, it will.

Outlook 2011 For Mac Update

Because Exchange email is all housed on the server, one should completely replace the existing Identity & newly configure Outlook for Mac & let the email sync from the server. Outlook 2016 requires Exchange 2010 or later so it's not an option for Oliver.

Alphnix: Your suggestion is only valid for a mail client that uses ActiveSync. As I have already noted above Outlook for Mac does.not. use ActiveSync, it uses Microsoft's EWS.

Oliver, please revisit & respond to my reply above. Ahh,.local rears its ugly head again.local is not a valid TLD, and Mac OS X handles it differently than Windows. Here are Microsoft's articles recommending against the use of.local 'Using single label names or unregistered suffixes, such as.local, is not recommended' The dsachetuil command should be as shown below, so I apologize for that typo on my part (I've fixed it above in my prior replies). Dsacheutil -q host -a name fqdn.ofyourserver.com or in your case dsacheutil -q host -a name server.domain.local. Thank you for the additional information on the versions of Outlook and OS, mobdoc.

Some more information for you from my team. Have you tried to see if Apple Mail will connect via the “Exchange” active sync setup? Also you can add a test user account on this particular Mac and attempt an Outlook setup to see if there are any changes. I believe, that despite uninstalling the software on previous attempts some remnants of the Microsoft DB or preferences were left behind.

By setting up a test user OS X account and trying the Outlook setup again we can eliminate some possibilities. The Apple Mail setup could also shed some light..

Error – “This application failed to start because OLM.DLL not found. Re-installing the application may fix this problem”. If this error hits your system, means Outlook 2011 for Mac is inaccessible and the application needs to be re-installed, but the problem is if you try to re-install the application, you might end-up losing previous data. Secondly, Outlook for Mac doesn’t allow OLM file to open on other email clients or operating systems, apart from Mac, thus ruling out the option of backup on other systems. To avoid losing email data, opt to rebuild Outlook 2011 for Mac which will not only help in resolving the current error “application failed to start” but also help in retrieving valuable database. Before acquainting with the methodology, let’s have a look at the probable symptoms when Outlook for Mac stops responding as per expectations:. Slow and unresponsive Mac.

Applications freeze or crash repeatedly without intimation. “Access denied” message pops-up and emails are not accessible. File not found as users are unable to locate data file. Error messages on the screen with error description and probable resolution.

Mac system terminates after a time-period What factors trigger the above-mentioned error symptoms? The common reasons which may result in corruption of Outlook 2011 Data file are:. Sudden Network failure or unexpected server problem. Malware attack on network. Exchange server crash.

Mac Outlook is not installed properly or there is interruption in installation. Corruption in storage media where Outlook application is installed. Outlook for Mac crashes due to unexpected problem. Corruption during Outlook for Mac update process There might be more reasons which result in Outlook for Mac data corruption. Whatever be the cause of the error, it is mandatory to repair and rebuild Outlook for Mac for efficient data recovery: Steps to rebuild your Identity Database Step 1: Switching off all the applications.

Click on application name menu from the toolbar available on top and select the Quit – option. Long press the Command and Option keys and press on Escape button from the keyboard. Select the application you need to quit from the Force Quit application window and click on Force Quit button. You can’t quit the Finder window. Close the windows with the red circular icon available on the top left corner of the screen. Step 2: Identify the amount of space available on Hard disk Maintenance process always needs double space and in this case of database maintenance, you need to have three times as much space as the current Outlook size is. If your Outlook database is 1 GB, you need to have 3GB space for efficiency.

Step 3: Get the backup of current identity As the name suggests, backup is essential to avoid the risk of losing data. In the Finder option, click on GoHome. Open folder “Documents”. Open the Microsoft User data folder.

Right click on the Office 2011 identities folder and select duplicate to create a new folder. Quit application By this method, You have created backup of your current identity Step 4: Rebuild Database using Inbuilt Utility. Quit all applications.

Hold to long press the Option key and start Outlook 2011 application or open the Application Folder after that click on Microsoft Office 2011 Folder then Double click on Microsoft Database Utility app. Select the Database and click on Rebuild 4. Rebuilding Main Identify window will open and show the progress. When the operation is completed, you will receive the message “Your database was rebuilt successfully.” Start Outlook 2011 application and verify if the problem is resolved. If the problem is resolved, proceed to access Outlook 2011 for Mac but if the problem still persists, proceed to create a new Identity to further resolve the issue. This step is applicable when you have created two different identities on the same system. Here Outlook may be configured to have more than one identity with each identity-constituting a separate set of e-mail, address books, tasks, calendars, account settings, and more.

Multiple identities may face corruption due to a single file-damage. Create a new identity to resolve the error. Step 5: Create new identity in Outlook 2011. Quit applications.

Long press Option key and click on Outlook to open Microsoft database utility. Click on (+) sign to add a new identity and type the name of new identity.

Set the New identity you created to mark it as default. Now that a new identity is created, quit and restart Check if the problem is resolved. Chances are that the database is still in the corrupt state even after the rebuilding database identity. Now that you have tried to rebuild database and the problem is not resolved, choose the most performing OLM repair software. One such tool is Stellar Repair for OLM software which not only repairs corrupt database but also retrieves the archived and deleted data, if required.

You can choose a single folder from the database or select the complete database, this is solely at your discretion. To summarize Outlook 2011 for Mac is an important application from the user perspective. In case the database gets corrupt, Mac efficiency is diminished to nil.

Using software helps you to resolve the error in no time. With unmatched Graphical User Interface and widespread compatibility, this tool enables even the non-technicians to execute their task with utmost perfection. What are you waiting for? Download the demo now.

I am using Outlook for Mac 2011 ( version 14.7.1). This morning when I started my MacBook Air ( i had shut it down last night) and clicked on the outlook, a message from Microsoft Database Utility advising that I must ”rebuild the main identity” popped up. Its been 5 hours and I am on step 3 of 5 where it is ”copying records to new database”. And it looks like it may take more than a day to complete this step! I have been taking regular backups via time machine and I took a back up now and copied the main identity to my external hard drive. But, this tool is better than Microsoft Database Utility for an error-free result.