Microsoft Office 2013 For Mac 3 Users
Applies to: Azure Information Protection, Office 365
Mar 24, 2013 3. Select Microsoft Office 2013 from the Programs & Features list. Select Office 2013 - Click on Change. Click on the symbol next to Office- Select Run All from My Computer and configure the setup. Restart the computer and check if you can access Office applications from other user accounts.
- Microsoft Office Professional 2013 32/64 Bit License - Download. Mfg Part Number 269-16093.
- Office 365, Office 2019, Office 2016, Office 2013, Office 2010, Office 2007, Office for Mac 2011, and Office for Mac 2008 applications can open your documents without any additional action. Customers using earlier versions of Office may need to download and install a compatibility pack.
Use this information to determine what you need to do so that Office apps work with the Azure Rights Management service from Azure Information Protection.
Office 365 apps, Office 2019, Office 2016, and Office 2013
Because these later versions of Office natively support the Azure Rights Management service, no client computer configuration is required to support the information rights management (IRM) features for applications such as Word, Excel, PowerPoint, Outlook, and Outlook on the web. All users have to do for these apps on Windows, is sign in to their Office applications with their Office 365 credentials. They can then can protect files and emails, and use files and emails that have been protected by others.
User instructions for Office for Mac
Users who have Office for Mac must first verify their credentials before they can protect content. For example:
Open Outlook and create a profile by using your Office 365 work or school account.
Create a new message and on the Options tab, select Permissions, and then select Verify Credentials. When prompted, specify your Office 365 work or school account details again, and select Sign in.
This action downloads the Azure Rights Management templates and Verify Credentials is now replaced with options that include No Restrictions, Do Not Forward, and any Azure Rights Management templates that are published for your tenant.
You can now cancel this new message.
To protect an email message or a document: On the Options tab, select Permissions and choose an option or template that protects your email or document.
Office 2010
For client computers to use the Azure Rights Management service with Office 2010, they must have the Azure Information Protection client (classic). No further configuration is required other than users must sign in with their Office 365 credentials and they can then protect files and use files that have been protected by others.
For more information about the Azure Information Protection client (classic), see Azure Information Protection client: Installation and configuration for clients.
-->At times your users might encounter issues with Office Add-ins that you develop. For example, an add-in fails to load or is inaccessible. Use the information in this article to help resolve common issues that your users encounter with your Office Add-in.
You can also use Fiddler to identify and debug issues with your add-ins.
Common errors and troubleshooting steps
The following table lists common error messages that users might encounter and steps that your users can take to resolve the errors.
| Error message | Resolution |
|---|---|
| App error: Catalog could not be reached | Verify firewall settings.'Catalog' refers to AppSource. This message indicates that the user cannot access AppSource. |
| APP ERROR: This app could not be started. Close this dialog to ignore the problem or click 'Restart' to try again. | Verify that the latest Office updates are installed, or download the update for Office 2013. |
| Error: Object doesn't support property or method 'defineProperty' | Confirm that Internet Explorer is not running in Compatibility Mode. Go to Tools > Compatibility View Settings. |
| Sorry, we couldn't load the app because your browser version is not supported. Click here for a list of supported browser versions. | Make sure that the browser supports HTML5 local storage, or reset your Internet Explorer settings. For information about supported browsers, see Requirements for running Office Add-ins. |
When installing an add-in, you see 'Error loading add-in' in the status bar
- Close Office.
- Verify that the manifest is valid
- Restart the add-in
- Install the add-in again.
You can also give us feedback: if using Excel on Windows or Mac, you can report feedback to the Office extensibility team directly from Excel. To do this, select FileFeedbackSend a Frown. Sending a frown provides the necessary logs to understand the issue.
Outlook add-in doesn't work correctly
If an Outlook add-in running on Windows and using Internet Explorer is not working correctly, try turning on script debugging in Internet Explorer.
Go to Tools > Internet Options > Advanced.
Under Browsing, uncheck Disable script debugging (Internet Explorer) and Disable script debugging (Other).
We recommend that you uncheck these settings only to troubleshoot the issue. If you leave them unchecked, you will get prompts when you browse. After the issue is resolved, check Disable script debugging (Internet Explorer) and Disable script debugging (Other) again.
Add-in doesn't activate in Office 2013
If the add-in doesn't activate when the user performs the following steps:
Signs in with their Microsoft account in Office 2013.
Enables two-step verification for their Microsoft account.
Verifies their identity when prompted when they try to insert an add-in.
Verify that the latest Office updates are installed, or download the update for Office 2013.
Add-in doesn't load in task pane or other issues with the add-in manifest
See Validate an Office Add-in's manifest and Debug your add-in with runtime logging to debug add-in manifest issues.
Microsoft Office 2013 For Mac 3 Users Manual
Add-in dialog box cannot be displayed
When using an Office Add-in, the user is asked to allow a dialog box to be displayed. The user chooses Allow, and the following error message occurs:
'The security settings in your browser prevent us from creating a dialog box. Try a different browser, or configure your browser so that [URL] and the domain shown in your address bar are in the same security zone.'
| Affected browsers | Affected platforms |
|---|---|
| Internet Explorer, Microsoft Edge | Office on the web |
To resolve the issue, end users or administrators can add the domain of the add-in to the list of trusted sites in Internet Explorer. Use the same procedure whether you're using the Internet Explorer or Microsoft Edge browser.
Important
Do not add the URL for an add-in to your list of trusted sites if you don't trust the add-in.
Office 365 For Mac
To add a URL to your list of trusted sites:
- In Control Panel, go to Internet options > Security.
- Select the Trusted sites zone, and choose Sites.
- Enter the URL that appears in the error message, and choose Add.
- Try to use the add-in again. If the problem persists, verify the settings for the other security zones and ensure that the add-in domain is in the same zone as the URL that is displayed in the address bar of the Office application.
This issue occurs when the Dialog API is used in pop-up mode. To prevent this issue from occurring, use the displayInFrame flag. This requires that your page support display within an iframe. The following example shows how to use the flag.
Changes to add-in commands including ribbon buttons and menu items do not take effect
If changes you've made in the manifest, such as file names of ribbon button icons or text of menu items, do not seem to take effect, try clearing the Office cache on your computer.
For Windows:
Delete the contents of the folder %LOCALAPPDATA%MicrosoftOffice16.0Wef.
University of iowa microsoft office for mac 2020. College of Nursing. College of Pharmacy. College of Engineering.
For Mac:
Add-ins are often cached in Office for Mac, for performance reasons. Normally, the cache is cleared by reloading the add-in. If more than one add-in exists in the same document, the process of automatically clearing the cache on reload might not be reliable.
You can clear the cache by using the personality menu of any task pane add-in.
Choose the personality menu. Then choose Clear Web Cache.
Note
You must run macOS version 10.13.6 or later to see the personality menu.
You can also clear the cache manually by deleting the contents of the ~/Library/Containers/com.Microsoft.OsfWebHost/Data/ folder.
Note
If that folder doesn't exist, check for the following folders and if found, delete the contents of the folder:
~/Library/Containers/com.microsoft.{host}/Data/Library/Caches/where{host}is the Office host (e.g.,Excel)~/Library/Containers/com.microsoft.{host}/Data/Library/Application Support/Microsoft/Office/16.0/Wef/where{host}is the Office host (e.g.,Excel)com.microsoft.Office365ServiceV2/Data/Caches/com.microsoft.Office365ServiceV2/
For iOS:
Call window.location.reload(true) from JavaScript in the add-in to force a reload. Alternatively, you can reinstall Office.
Changes to static files, such as JavaScript, HTML, and CSS do not take effect
The browser may be caching these files. To prevent this, turn off client-side caching when developing. The details will depend on what kind of server you are using. In most cases, it involves adding certain headers to the HTTP Responses. We suggest the following set:
- Cache-Control: 'private, no-cache, no-store'
- Pragma: 'no-cache'
- Expires: '-1'
For an example of doing this in an Node.JS Express server, see this app.js file. For an example in an ASP.NET project, see this cshtml file.
Microsoft Office For Mac
If your add-in is hosted in Internet Information Server (IIS), you could also add the following to the web.config.
If these steps don't seem to work at first, you may need to clear the browser's cache. Do this through the UI of the browser. Sometimes the Edge cache isn't successfully cleared when you try to clear it in the Edge UI. If that happens, run the following command in a Windows Command Prompt.