*Microsoft Excel Runtime Error 9
*Excel Runtime Error 91
*Mac Excel Runtime Error 1004
*Excel Runtime 2016-->
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.
Different macbooks. Note
The runtime logging feature is currently available for Office 2016 or later on desktop.
*Problems may occur when you automate Microsoft Word or Microsoft Excel if either the Normal.dot template in Word or the Excel.xlb resource file in Excel is corrupted. To test these files, search the local hard disks for all instances of Normal.dot or of Excel.xlb. Note You may find multiple copies of these files. There is one copy of each of.
*This excel file repair tool can be used on both Windows and Mac platforms to repair corrupt excel file. All kinds of MS office corruption errors (for XLS and XLSX files only) can be handled with this tool.
*Excel 2016 is a Microsoft’s venerable Excel series of spreadsheet software. This latest Excel version is smooth and modernized, with all its previously existing features and few more advanced features that provide greater ease of use.Microsoft Excel Runtime Error 9
Important
It only seems to happen on Excel for Mac 2016 and 2019. I know that starting with Excel for Mac 2016, Excel is “sandboxed”, meaning you cannot save files wherever you want via VBA code. But my code is written to save the file in a particular folder that should always be accessible by Excel, regardless of the sandbox limitation: /Users. The runtime error 1004 usually appears in Excel when the user tries to run MS Visual Basic for Applications Macro, which is MS VBA to change Legend entries. It is a security action performed by Excel to lock out access to MS VBA, and if the user chooses to permit the programmatic access, then runtime error 1004 cannot appear most of the time.
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 WindowsExcel Runtime Error 91
*
Make sure that you are running Office 2016 desktop build 16.0.7019 or later.
*
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.
*Right-click the WEF key (folder) and select New > Key.
*Name the new key Developer.
*
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
*
Make sure that you are running Office 2016 desktop build 16.27 (19071500) or later.
*
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:Mac Excel Runtime Error 1004
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:
*
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.
*
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.
*
Search the log file for your add-in ID, which you define in your manifest. In the log file, this ID is labeled SolutionId.
In the following example, the log file identifies a control that points to a resource file that doesn't exist. For this example, the fix would be to correct the typo in the manifest or to add the missing resource.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.Excel Runtime 2016See also
