Troubleshoot user errors with Office Add-ins

At times your users might encounter issues with Office Add together-ins that y'all develop. For example, an add-in fails to load or is inaccessible. Use the information in this commodity to help resolve mutual bug that your users encounter with your Function Add-in.

You can also employ Fiddler to identify and debug problems 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 have to resolve the errors.

Error message Resolution
App fault: Itemize 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 exist started. Close this dialog to ignore the problem or click "Restart" to endeavor again. Verify that the latest Office updates are installed, or download the update for Part 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, nosotros couldn't load the app because your browser version is non 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 together-ins.

When installing an add-in, you lot see "Fault loading add together-in" in the status bar

  1. Close Office.
  2. Verify that the manifest is valid
  3. Restart the add together-in
  4. Install the add-in over again.

You can as well give us feedback: if using Excel on Windows or Mac, yous can written report feedback to the Office extensibility team straight from Excel. To do this, select File | Feedback | Transport a Frown. Sending a frown provides the necessary logs to understand the effect.

Outlook add-in doesn't work correctly

If an Outlook add-in running on Windows and using Cyberspace Explorer is not working correctly, endeavor turning on script debugging in Cyberspace 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, yous volition get prompts when you browse. Afterward the event is resolved, check Disable script debugging (Internet Explorer) and Disable script debugging (Other) once more.

Add-in doesn't activate in Office 2013

If the add-in doesn't activate when the user performs the following steps.

  1. Signs in with their Microsoft account in Office 2013.

  2. Enables two-pace verification for their Microsoft account.

  3. 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 dialog box cannot be displayed

When using an Office Add-in, the user is asked to allow a dialog box to exist displayed. The user chooses Permit, and the following error message occurs.

"The security settings in your browser foreclose us from creating a dialog box. Attempt a different browser, or configure your browser so that [URL] and the domain shown in your address bar are in the aforementioned security zone."

Screenshot of the dialog box error message.

Affected browsers Affected platforms
Microsoft Border Office on the web

To resolve the issue, end users or administrators can add the domain of the add-in to the listing of trusted sites in the Microsoft Edge browser.

Important

Practise not add the URL for an add-in to your list of trusted sites if you don't trust the add-in.

To add a URL to your list of trusted sites:

  1. In Command Panel, go to Internet options > Security.
  2. Select the Trusted sites zone, and cull Sites.
  3. Enter the URL that appears in the error bulletin, and choose Add.
  4. Effort to employ the add together-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 awarding.

This event occurs when the Dialog API is used in pop-up mode. To foreclose 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.

              Office.context.ui.displayDialogAsync(startAddress, {displayInIFrame:truthful}, callback);                          

Run into as well

  • Troubleshoot evolution errors with Office Add-ins