Support for Office for Mac 2011 ended on October 10, 2017. All of your Office for Mac 2011 apps will continue to function. However, you could expose yourself to serious and potentially harmful security risks. Upgrade to a newer version of Office so you can stay up to date with all the latest features, patches, and security updates. If the Microsoft Office folder is not in Applications, Microsoft AutoUpdate does not detect Microsoft Office on the Mac, and it cannot install updates. To verify that the Microsoft Office folder is in the correct location, follow these steps: On the Go menu, click Applications. Look for the Microsoft Office 2008 or Microsoft Office 2011 folder. Microsoft originally had plans to release Office for Mac in the spring of 2014, but it appears the company will miss that timeline, instead planning for a release later in the year. According to a.
Topics Map > Campus Services > Office 365
2016-4-10 For my Office 2016 applications on the latest version of Mac OS X (10.11.4) via my Office 365 subscription. I then moved all of the fonts in the /Library/Fonts/ folder to a new folder. Being on the same drive, a move did nothing more than change all of the file table entries to note the new location of the fonts. Office 2016 on El.
Below is a list of known issues with Outlook for Windows and Mac desktop clients. Feature requests and known issues for other clients can be viewed at: Outlook on the Web | Outlook for mobile devices.
Important: You can contact Microsoft directly to make a case for supporting a specific feature in Office 365, by submitting your idea to Microsoft's Office 365 feedback and suggestions site at https://office365.uservoice.com/.
For a list of issues that have been resolved, click here.
You may also want to review support documentation from other services that may be related to the issue you are experiencing.
- OneDrive for Business: known issues | support
- Wisc Account Administration site: known issues | support
- Google Apps: known issues | support
- WiscList: known issues | support *
Note: If you are experiencing message delivery delays and are interacting with a WiscList, review the documentation related to WiscList above.
If you are experiencing issues with an earlier version of Outlook, the UW-Madison Office 365 team recommends upgrading to a newer version of Outlook. Learn more about client support.
Outlook for Mac clients
- Fixes or workarounds for recent issues in Outlook for Mac
- Details and Workaround
- With the latest release/update to Apple OS and Office for Mac, multiple issues have risen and are being worked on. Please review this article for common issue and automated troubleshooting tools.
- In addition, is it highly recommended that you always make sure you are running the latest version of Office for the Mac. In some cases, the issue you are experiencing may have been fixed in a newer version.
- Details and Workaround
- Microsoft acknowledges Office 2016-El Capitan crashes but lacks ETA for fix
- Details and Workaround
- Error: 'Microsoft Outlook has encountered a problem and needs to close. We are sorry for the inconvenience' when using Outlook 2016/2011 for Mac.
- For additional details on this issue, review following information.
- Workaround: Install the latest release of Office/Outlook.
- Details and Workaround
- Performance issues such as slowness when interacting with mail and/or calendar
- Details and Workaround
- In Outlook 2011 and Outlook 2016 for Mac, accounts that you have full mailbox permissions to -- including any linked accounts -- will not be added to your account list automatically. You will need to subscribe or configure these accounts.
- Details and Workaround
- In Office 2011 for Mac, installation produces 'activation' or 'sign-on' error
- Details and Workaround
- The version of Office 2011 for Mac downloaded from within Outlook on the web is not compatible with UW-Madison's Office 365 implementation. If you attempt to install/run this version, it will return an error within the 'Activate Office' screen: Sign in failed because the password is incorrect or the sign-in name does not exist or Sorry, there was a problem while trying to connect to your account.
- Current Work Around (because the Office 2011 installer available on the Campus Software Library is licensed under UW-Madison's Microsoft EES, it can only be used on UW-owned computers and is not visible or available to students)
- Delete any Office 2011 software from your 'Applications' folder.
- Delete any Office 2011 application icons from within your dock.
- Log into UW-Madison Campus Software Library using your NetID credentials.
- Within the 'Productivity' section, click Microsoft Site License.
- Within the 'Downloads | Microsoft Office Site License' section, click Macintosh - Office 2011 Standard.
- Save/Run the file.
- Details and Workaround
Outlook for Windows clients
- When you view items in the secondary mailbox, new items may not appear or items seem to be missing or items that you had deleted still appear in the secondary mailbox.
- Details and Workaround
- For additional details on this issue, review following information.
- Workaround/solution:
- Start Outlook for Windows.
- On the 'File' tab, click Account Settings in the Account Settings list.
- In the Account Settings dialog box, click the 'E-mail' tab and then double-click your Microsoft Exchange Server account.
- In the 'Change Account' dialog box, click More Settings.
- In the 'Microsoft Exchange' dialog box, click the 'Advanced' tab.
- Click to clear the Download shared folders check box.
- Click OK two times.
- Click Next, click Finish, and then click Close.
- Restart Outlook.
- Details and Workaround
- Performance issues such as slowness when interacting with mail and/or calendar
- Details and Workaround
- The most common performance issue for Outlook is slowness when completing the following tasks: downloading/syncing mail, loading calendar, interacting with messages, editing calendars, or editing permissions.
- Workaround: Performance issues can have a variety of causes. For more information on how to improve Outlook performance, please review the following document: Office 365 - Get better performance when using Outlook desktop clients.
- Details and Workaround
- When using Outlook for Windows, you may experience any of the following symptoms: Outlook does not load or takes a long time to load, receive an error during startup, unable to access another account(s) (permission issue), etc
- Details and Workaround
- A common troubleshooting step for these types of symptoms is to recreate the Outlook local data file for your profile. To perform this action, follow the steps outlined within the Re-create an offline Outlook Data File (.ost) section. After completing this, start Outlook and see if the problem persists.
- Details and Workaround
- Moving, copying, or deleting large quantities of mail may result in an error
- Details and Workaround
- Error messages can include: 'Outlook is not responding' or 'Outlook is not working'.
- If this occurs, do not attempt to shutdown or quit out of Outlook. Be patient and let Outlook complete your last action. This may take several minutes.
- Review following Microsoft resources:
- Details and Workaround
- Downloading a large mailbox can result in an error
- Details and Workaround
- Error messages can include: 'Outlook is not responding' or 'Outlook is not working'.
- If this occurs, do not attempt to shutdown or quit out of Outlook. Be patient and let Outlook complete your last action. This may take several minutes.
- Review following Microsoft resources:
- Details and Workaround
- Sending as an address which is not visible in the Global Access List (GAL) can result in an error
- Details and Workaround
- When attempting to send as an address which you have send as permissions for, the following error will be sent to your inbox if the send as account is not visible in the GAL:
- Information on how to make an account visible in the GAL can be found here: Show or Hide Service Account within Global Address List
- Details and Workaround
- Performance issues such as slowness when interacting with mail and/or calendar
- Details and Workaround
- In Outlook for Windows, accounts that you have full mailbox permission to -- including any linked accounts -- will be added to your account list automatically. Review the following document for further details on AutoMapping: Office 365 - Automapping.
- Details and Workaround
- Emails with HTML formatting do not always display as expected
- Details and Workaround
- To work around this issue, Outlook gives you the option to open the message in a web browser.
- More information on this issue is available here and here.
- Details and Workaround
- Some users are unable to use the 'Report Spam' function in certain Outlook desktop clients. In some rare cases, the 'Report Spam' action will not work and the message will remain in your Inbox. We are aware of this issue and are working on a solution.
- Details and Workaround
- Use Outlook on the web to submit the message as spam.
- Manually forward the message to the spam repository account.
- Details and Workaround
- Some users are unable to use the 'Report Spam' function in certain Outlook desktop clients. In some rare cases, the 'Report Spam' action will not work and the message will remain in your Inbox. We are aware of this issue and are working on a solution.
- Details and Workaround
- On machines with smaller monitors, clicking the 'Report Spam' link displays a disclaimer, but the 'Report Spam' button is obscured from view. It is not possible scroll down to see the button.
- To work around this issue, double-click on the message to open it in a separate window, then maximize the window. This should allow for enough space for the 'Report Spam' button to be displayed below the disclaimer.
- Details and Workaround
- In Outlook for Windows, emails 'sent as' or 'sent on behalf of' another account will appear in the default configured account's Sent Items folder
- Details and Workaround
- If you send an email on behalf of Bucky Badger, the email will appear in your Sent Items folder instead of Bucky's. Note: Even though you may have 'send as' or 'send on behalf of' permissions to another account, this does not mean the account will automatically show up in Outlook 2016/13.
- This does not occur in Outlook 2016/2011 for Mac.
- Workaround: Follow these instructions/options to have a message sent stored in the mailbox of the intended account.
- Details and Workaround
- After the password for your NetID account is changed, Microsoft Outlook may repeatedly prompt you for your password or is unable to send/receive mail. After you enter the new password and then click to enable the Remember my credentials option, you are again prompted for your credentials. Microsoft access os x mac.
- Details and Workaround
- Windows uses a password manager to store your account credentials for certain applications. You may need to reset these credentials.
- Workaround - Review NetID password change issue for Outlook document.
- Details and Workaround
- In Office 2013 for Windows, activation produces 'The user id or password is incorrect. Please try again.' when attempting to sign-in to your Office 365 account
- Details and Workaround
- The version of Office 2013 for Windows downloaded from within the campus software library is not compatible with UW-Madison's Office 365 implementation. If you attempt to install/run this version, it will return an error within the activation screen: 'The user id or password is incorrect. Please try again.'.
- Workaround - Uninstall Office 2013 then install the version Office for Windows available to you via Outlook on the web. If you do not want to uninstall your current version of Office, follow these instructions to install the correct version of Office. Make sure to follow the steps to update your registry.
- Details and Workaround
- If you are having trouble starting Outlook for Windows, or have received the error 'Cannot start Microsoft Outlook. Cannot open the Outlook window', the user interface may be failing to completely launch.
- Details and Workaround
- Review this Microsoft document for possible solutions.
- Details and Workaround
- Importing contacts from Thunderbird to Outlook for Windows will require extra steps.
- Details and Workaround
- By default, contacts imported from Thunderbird to Outlook will display the email address in the 'Comments' field. Other information may also display incorrectly.
- For information on how to avoid this issue, see step #12 of this document: [Link for document 35410 is unavailable at this time.].
- Details and Workaround
- Unable to edit or assign permissions to or create/edit/delete events on a resource when granted editor/owner rights in Outlook for Windows.
- Details and Workaround
- Some users may experience the inability to edit (create, edit, delete events) or assign permissions to a resource even though the user has been granted the appropriate access to the resource.
- Open Outlook.
- Go to File > Account Settings > Account Settings.
- Select your Exchange profile > Click 'Change' > Click 'More Settings' > Select the 'Advanced' tab.
- Check 'Use Cached Exchange Mode' (if not already checked).
- Uncheck 'Download shared folders'.
- Click OK > Click 'Next' > Click 'Finish'.
- Restart Outlook.
- Some users may experience the inability to edit (create, edit, delete events) or assign permissions to a resource even though the user has been granted the appropriate access to the resource.
- Details and Workaround
- Unable to share calendar - Policy does not allow.
- Details and Workaround
- When attempting to share one of your secondary calendars you may receive the following message: 'Policy does not allow granting permissions at this level to one or more of the recipients. Please select another permission level and send the sharing invite again'. Follow the steps below to correct this.
- Open Outlook.
- Select the calendar you want to share. Make certain the the text of the name in the calendar tab is bold
- From the ribbon in the Home tab in the Share group, click Share Calendar.
- Click Add.
- In the Address book list, click Global Address List.
- In the Search box type the last name of the person with whom you want to share your calendar.
- Click Go.
- Click to highlight the person's name.
- Click To, then click OK.
- Repeat steps 5 - 9 for each additional person you want to share your calendar with.
- Click Send.
- When attempting to share one of your secondary calendars you may receive the following message: 'Policy does not allow granting permissions at this level to one or more of the recipients. Please select another permission level and send the sharing invite again'. Follow the steps below to correct this.
- Details and Workaround
Go Errors
See Also:
![Golang 1.3 error Golang 1.3 error](/uploads/1/2/5/6/125656977/150595513.png)
The Problem
In OS X 10.4.x (Tiger), when you launch Word 2004, you get multiple errors saying something like “(name of font) is corrupt and should be removed.” This happens for many, if not all, your fonts and without any apparent cause (although more likely when installing Office 2004 in Tiger or just after upgrading to Tiger). You click out of the error dialogs, check your fonts only to find out that they are not corrupt, and then everything is fine until you quit and relaunch Word, whereupon the entire mess repeats.
The Cause
When Word launches, it checks each font before loading it. The splash screen shows 'Optimizing font menu performance..' during this process. However, something about certain installations of Tiger causes Word to report fonts as corrupt while this is going on, even when the fonts appear to be perfectly fine.
Simply put, no one knows the cause .. yet. The “corrupt font error” issue is annoying (to say the least) and unpredictable. It only hits a small percentage of Office users and it doesn't reproduce consistently. That makes it very hard to pin down and fix; as does the fact that it’s hard to determine whether there’s genuine font corruption as opposed to an illegitimate warning related to Office font validation.
What To Do About It
There are seven or eight things to try listed below. None of the following procedures work in every case and none will reliably prevent a repeat visit of the bug, even when they work initially. However, many users have found at least temporary relief—usually these will work at least until you have to reboot the computer. If one of these works for you or if you have another solution or information that could lead to a permanent fix, please let Apple, Microsoft and/or us know about it. You can reach us on the Microsoft Answers site.
The Procedures
Update
Be sure you have both Office/Word and your OS fully updated. Click here for more information on updating.
Check for Font Corruption
New Mac Os Errors With Microsoft Office Free
It’s always possible that you actually have corrupt fonts in your system. You can use Tiger’s Font Book application to check. Select all your fonts in Font Book and use “File:Validate Font”. Alternatively, you can use more powerful, third-party applications like Font Doctor [Lene Fredborg, 1-Oct-2018: Removed outdated link to http://www.morrisonsoftdesign.com/with_fl/index-7.html]. If you don’t own this software already, you can use it in demo mode to scan for corrupted fonts.
A new (July 2006) workaround related to this procedure has been posted by Jeff Boultinghouse on one of the Microsoft newsgroups. This is the only report of success with this method that we have seen so far but it looks promising.
I stumbled across another solution that worked in my case and may help other users. A program called Linotype FontExplorer X is available for free download. This program contains a utility under the 'Tools' menu called 'Clean System Fonts folders..' When selected, this utility puts up a dialog box to confirm that the user wishes to run it and also states, 'All fonts not installed by the Mac OS X Installation will be moved to a folder on your Desktop. You can backup this folder afterwards for the case that an application needs some of these fonts or you can delete them all.' The utility takes very little time to run. When it finished, I was able to launch and run Office applications with no errors. Many of the fonts that were moved to the Desktop had names that clearly identified them as application-specific (such as OCR-A installed by TurboTax) and had been installed as part of the application installation. I then started FontBook and reinstalled several fonts that had previously been declared as 'corrupt' by Office. Again, Office applications launched with no difficulty and the reinstalled fonts were available for use by the Office application. I proceeded to reinstall all of the fonts using FontBook. A number of them were rejected by FontBook (which had not been previously rejected by the FontBook 'Validate Fonts' function) and were not reinstalled. Following this, all Office applications work just fine, as do all other applications I have tested. My hunch is that Linotype FontExplorer X recognizes a flag in each font file that identifies whether it was installed by OS X or not and does a better job of clearing the caches and font folders. FontBook is able to recognize truly corrupt font files when attempting to reinstall them and thus prevents the user from putting bad fonts back in the system. It's not clear why Office was reporting perfectly good fonts as corrupt, but the sequence of events shows that there were, in fact, bad font files present. Many of the fonts that would not reinstall had very old file creation dates, some as far back as 1993. By following this procedure, I had confirmed the status of each font file and had used OS X to reinstall all of the fonts that had been installed by other applications. I hope this information is useful and presents an effective solution for other users. I know from experience that this can be an extraordinarily frustrating problem to solve. |
Remove Duplicate Fonts
Make absolutely sure there are no duplicate fonts. Use OS X’s Font Book or a third-party application to resolve duplicates.
Remove (or cut back) the OS 9 fonts
If you need to use OS 9 fonts on occasion, keep only the necessary ones. If you don’t need them, rename or just delete the OS 9 fonts folder.
Delete the Office Font Cache
Quit all Office applications, trash the Office Font Cache – Home/Library/Preferences/Microsoft/Office Font Cache (11) – empty the trash, and then relaunch Word.
Delete the System and User Font Caches
Quit all Office applications and drag the following files to the trash. Reboot, and then empty the trash.
- Com.apple.ATS.plist (Home/Library/Preferencess)
- Com.apple.ATS/ (/Library/Caches)
- FontTablesAnnex (/System/Library/Caches)
- All other files whose names include .ATS or Font found in /System/Library/Caches, especially com.apple.ATS.System.fcache and com.apple.ATSServer.FODB_System
You can delete these files/folders yourself or use a third-party utility to do it for you: TinkerTool System, or Font Finagler(shareware). Even if the application doesn’t ask you to, you should reboot immediately after deleting the system font caches.
Safe Boot
A participant on the microsoft.public.mac.office newsgroup (Jeffrey Hicken) recommends this procedure: First, do a safe boot (start up your machine and when you hear the chime, hold down the Shift key until you see the spinning progress clock (maybe 2-3 minutes). Next, launch Word. Finally, restart your machine normally. This worked for months for Jeffrey until he installed a new font, at which time problems arose again; but repeating the Safe Boot procedure got things back to normal.
To be honest, we’re not sure why doing a Safe Boot is any more efficacious than deleting particular font caches (since that’s part of what Safe Boot does), but we can’t say for sure either that one of its other actions doesn’t help. (Apple isn’t exactly verbose on what Safe Boot does but here’s what they have to say [Lene Fredborg, 4-Feb-2019: Removed outdated link to http://docs.info.apple.com/article.html?artnum=107392]. At any rate, it’s worth a try.
'Remove' the Font Cache Tool
Some users have reported that trashing the Font Cache Tool fixes this problem for them. While it doesn’t actually fix anything, the procedure does prevent the problem from coming to view by eliminating the 'font optimization” process from occurring at all. This action, however, has repercussions that you may not like:
- Not only will you stop getting these false corrupt font error messages, but you won’t get real ones either.
- If you prefer to view fonts as WYSIWYG and you ever (again) have to trash your Office Font Cache, you will lose WYSIWYG display.
- The only way to restore the Font Cache Tool after trashing it is by reinstalling Office.
There is a workaround however: Another newsgroup contributor (J. Bingham) reported that instead of trashing the Font Cache Tool, you can archive it, rename it or drag it into a subfolder so Office doesn’t recognize it. That way, if you need it again, you can restore it. NOTE: You should restore the Font Cache Tool before updating Office.
We don’t really recommend the above hack, but if you’re really desperate . . .
Go back to OS X 10.3.9
This is a last ditch workaround but the fact is that the “corrupt font error” occurs almost exclusively in Tiger (OS 10.4.x). We do have one report of what appears to be this same error in an installation of OS X 10.3.9.
In Closing
Thanks to all the newsgroup posters who contributed to this article. We will continue to update it as new information comes in. Hopefully Apple or Microsoft will figure out how to reproduce this bug so they can fix it!