You may get “Error loading add-in” while trying to install SmartCite in Microsoft Word 2016+ from the Store. This is due to an authentication issue, but not to worry - it's an easy fix! To get this solved, you need to log-out of Microsoft and log back in again. We've outlined the steps below. When we upgraded to Word 2016, I saved the 2007.doc document as a 2016.docx document. Since that point, it has not allowed me to add images. However, there appears to be a placeholder for the image as the area I am trying to place an image displays a width and length as if the image is there but not displayed. Word 2016 version 15.xx: Copy the file 'EndNote CWYW Word 2016.bundle' by highlighting the file and going to 'Edit Copy.' (see below for download) (see below for download) NOTE: If you do not see the 'EndNote CWYW Word 2016.bundle' file in the 'Applications: EndNote X8(X9): Cite While You Write' folder (or if this file is not the most up to. To check if it is installed, open Word, and then click About Word from the Word menu. If the version number is 14.2.0 or above, you have Service Pack 2 and you should follow the Service Pack 2 steps when provided in this article. Install Adobe Sign add-in or any other add-in. Log in Word 2016 with Adobe account. You are able to use the add-in without any problems. If an error still persists, try the following instead.

You can use runtime logging to debug your add-in's manifest as well as several installation errors. This feature can help you identify and fix issues with your manifest that are not detected by XSD schema validation, such as a mismatch between resource IDs. Runtime logging is particularly useful for debugging add-ins that implement add-in commands and Excel custom functions.

Note

The runtime logging feature is currently available for Office 2016 or later on desktop.

Important

Runtime Logging affects performance. Turn it on only when you need to debug issues with your add-in manifest.

Use runtime logging from the command line

Enabling runtime logging from the command line is the fastest way to use this logging tool. These use npx, which is provided by default as part of npm@5.2.0+. If you have an earlier version of npm, try Runtime logging on Windows or Runtime logging on Mac instructions, or install npx.

• To enable runtime logging:

• To enable runtime logging only for a specific file, use the same command with a filename:

• To disable runtime logging:

• To display whether runtime logging is enabled:

• To display help within the command line for runtime logging:

Runtime logging on Windows

1. Make sure that you are running Office 2016 desktop build 16.0.7019 or later.

2. Add the RuntimeLogging registry key under HKEY_CURRENT_USERSOFTWAREMicrosoftOffice16.0WEFDeveloper.

   Note

   If the Developer key (folder) does not already exist under HKEY_CURRENT_USERSOFTWAREMicrosoftOffice16.0WEF, complete the following steps to create it.

   1. Right-click the WEF key (folder) and select New > Key.
   2. Name the new key Developer.

3. Set the default value of the RuntimeLogging key to the full path of the file where you want the log to be written. For an example, see EnableRuntimeLogging.zip.

   Note

   The directory in which the log file will be written must already exist, and you must have write permissions to it.

The following image shows what the registry should look like. To turn the feature off, remove the RuntimeLogging key from the registry.

Runtime logging on Mac

1. Make sure that you are running Office 2016 desktop build 16.27 (19071500) or later.

2. Open Terminal and set a runtime logging preference by using the defaults command:

   <bundle id> identifies which the host for which to enable runtime logging. <file_name> is the name of the text file to which the log will be written.

   Set <bundle id> to one of the following values to enable runtime logging for the corresponding application:

   • com.microsoft.Word
   • com.microsoft.Excel
   • com.microsoft.Powerpoint
   • com.microsoft.Outlook

The following example enables runtime logging for Word and then opens the log file:

Note

You'll need to restart Office after running the defaults command to enable runtime logging.

To turn off runtime logging, use the defaults delete command:

The following example will turn off runtime logging for Word:

Use runtime logging to troubleshoot issues with your manifest

To use runtime logging to troubleshoot issues loading an add-in:

1. Sideload your add-in for testing.

   Note

   We recommend that you sideload only the add-in that you are testing to minimize the number of messages in the log file.

2. If nothing happens and you don't see your add-in (and it's not appearing in the add-ins dialog box), open the log file.

3. Search the log file for your add-in ID, which you define in your manifest. In the log file, this ID is labeled SolutionId.

Known issues with runtime logging

You might see messages in the log file that are confusing or that are classified incorrectly. For example:

• The message Medium Current host not in add-in's host list followed by Unexpected Parsed manifest targeting different host is incorrectly classified as an error.

• If you see the message Unexpected Add-in is missing required manifest fields DisplayName and it doesn't contain a SolutionId, the error is most likely not related to the add-in you are debugging.

• Any Monitorable messages are expected errors from a system point of view. Sometimes they indicate an issue with your manifest, such as a misspelled element that was skipped but didn't cause the manifest to fail.

See also

On this page, we have collected three practical solutions that can help fix the 'Word Not Opening' error on Mac. And if you mistakenly removed a Word file on Mac, let reliable Mac file recovery software as recommended here for help. Check out how to fix the not opening Word file to accessible again:

'Word 2016 on my Mac won't open. It flashes immediately by double-clicking and then closes unexpectedly. I didn't do anything or any change. How to fix it if Microsoft Word won't open at all?'

In addition to this situation, most users are also faced with these errors:

• The application Microsoft Word quit unexpectedly
• Microsoft Word cannot be opened because of a problem. Check with the developer to make sure Microsoft Word works with this version of Mac OS X

Error Loading Add-ins Word For Mac 2016 Free

As Microsoft Word is widely used among people, owning some basic Word troubleshooting is recognized as an essential skill. Today you're going to learn three tricks in solving Word not opening on Mac. The given workarounds are applicable to all Word editions such as 2003, 2007, 2010, 2013 2016.

1. Run Repair Disk Permissions

Step 1: On the 'Go' menu, click 'Utilities'. Start the Disk Utility program.

Step 2: Choose the primary hard disk drive for your computer. Then, click the 'First Aid' tab.

Step 3: Click 'Run' to repair the disk volume errors and permissions. When it finishes, click 'Done'.

2. Remove Word Preferences

Step 1: Open 'Library'. Usually, click 'GO' > 'Go to the folder', then type ~/Library

Step 2: Locate a file named as 'Preferences'.

Step 3: Find a file named com.microsoft.Word.plist. Move the file to the desktop.

Start Word, and check whether the problem still occurs.

If the problem still occurs, exit Microsoft Word, and then restore the 'com.microsoft.word.prefs.plist' file to its original location. Then, go to Step 4.

If the problem seems to be resolved, you can move the file to the trash.

Note: If you do not locate the file, the program is using the default preferences.

Step 4: Exit all Microsoft Office for Mac programs. Then, Click the Word icon. On the left, click 'Preferences'.

Step 5: Click 'File Locations'.

Step 6: Select 'User templates'.

Error Loading Add-ins Word For Mac 2016

Step 7: Locate the file that is named Normal, and move the file to the desktop.

You can also find the file named as Normal through this way: 'Library' > 'Application Support' > 'Microsoft' > 'Office' > 'User Templates' > 'Normal'

Start Word, and check whether the problem still occurs. If the problem seems to be resolved, you can move the 'Normal' file to the trash.

3. Try to Open and Repair Word

Step 1: Start Word. On the File menu, click 'Open'.

Step 2: In the Open dialog box, select the file that you want to open. Click the down arrow on the Open button, click 'Open' > 'Repair'.

Recover Deleted and Missing Word on Mac

Do not worry if the 'Word not opening' issue causes data loss disaster, you can recover unsaved Word document on Mac from its Temporary folder and AutoRecovery save. While for a deleted Word document on Mac, the easiest way of recovery is using a third-party Mac data recovery software.

EaseUS Data Recovery Wizard for Mac also recovers Word document that is missing, deleted or lost due to formatting, virus infection and other misoperation, and the best part of using the software to recover Word is being able to preview the file entirety.

Step 1. Select the disk location (it can be an internal HDD/SSD or a removable storage device) where you lost data and files. Click the 'Scan' button.

Step 2. EaseUS Data Recovery Wizard for Mac will immediately scan your selected disk volume and display the scanning results on the left pane.

Step 3. In the scan results, select the file(s) and click the 'Recover Now' button to have them back.