XLCubed Excel Edition Troubleshooting

Revision as of 10:26, 10 January 2022 by Antonio.remedios (talk | contribs) (You receive a Cannot insert object error when inserting a Dimension Slicer)

Installation Troubleshooting

  • Details of prerequisites can be found here.

Could not access network location \Hewlett-Packard\\.

When installing XLCubed, you get the above error message. This is because of a faulty InstallLocation registry entry, found in these two places:


You can either back up, then remove it manually, or follow the instructions listed in this article.

XLCubed Ribbon or menu doesn't appear

Could not load file or assembly

When you perform certain actions, you get this error message:

Could not load file or assembly 'office, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c'
or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040)

Download and install the following packages:

Alternatively, this error may be a sign that a cloud version of Office 365 with restricted add-in support is installed. XLCubed requires the desktop version of Office.

Error while processing XLCubed.dna

When you open XLCubed, you get the following error message:

There was an error during processing of C:\Program Files (x86)\XLCubed Ltd\XLCubed\XLCubed.dna:
There is an error in XML document (0, 0).
The type initializer for 'System.Xml.Serialization.XmlSerializationReader' threw an exception.

This error can be caused by problems with one of several configuration files:

  • XLCubed.dna, XLCubed64.dna, XLCubed.xll.config or XLCubed64.xll.config, all found in the XLCubed installation folder (usually C:\Program Files (x86)\XLCubed Ltd\XLCubed)
  • Excel.exe.config, found in the Excel installation folder (usually C:\Program Files (x86)\Microsoft Office\Office15 or similar)
  • machine.config, found in the Microsoft.NET configuration folder (usually C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config and C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config)

The problems can be caused by several underlying issues:

  • The files do not exist (except for XLCubed.xll.config and Excel.exe.config, which are not necessary)
  • The files exist, but are protected and not accessible by Excel while it is loading
  • The files exist, but are corrupted

In particular, installation of some IBM Client Access providers can cause problems with the machine.config file. See this IBM support article for details.

The .Net runtime interface could not be retrieved

When you open XLCubed, you get the following error message:

This Excel add-in requires the Microsoft .NET Framework 4.
A problem occurred while attempting to load the .NET runtime:
 The .Net runtime interface could not be retrieved.
This is an unexpected error. Please report this error to the add-in developer.
Additional error information: HRESULT 0x12980620

This error is caused by using an on-demand version of Microsoft Office rather than being conventionally installed on your computer. XLCubed is not currently compatible with this version of Office.

Grid Troubleshooting

When I try to create a Grid Chart, no chart types are listed, and I cannot press OK to insert it.

Your formats file may be missing or corrupted. Please back it up, then copy a new version from the XLCubed installation folder. Typical locations are:

Installation version 
C:\Program Files\XLCubed Ltd\XLCubed\FormatSheet.xls and FormatSheet.xlsx
User's customised version 
C:\Users\username\AppData\Roaming\XLCubed Ltd\XLCubed Excel Edition

Slicer Troubleshooting

You receive a Cannot insert object error when inserting a Dimension Slicer

This error can be caused by a workbook being in protected mode. It may have the alternative error message "Unable to create specified ActiveX control". Please try to unprotect the workbook and insert the slicer.

If this doesn't help, this error is often caused by some of the XLCubed assemblies not being correctly registered. To re-register them, you must run the following command as an elevated administrator, using the path where XLCubed is installed:

 "C:\Program Files\XLCubed Ltd\XLCubed\XLCubed.Excel.Installer.Utility.exe" /regctls

In version 6.1 and prior versions, the /regctls switch wasn't available. In this case, use this instead, again using an administrator account:

 C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /tlb /codebase "C:\Program Files\XLCubed Ltd\XLCubed\XLCubed.Excel.UserInterface.dll"
 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe /tlb /codebase "C:\Program Files\XLCubed Ltd\XLCubed\XLCubed.Excel.UserInterface.dll"

If these commands don't work, you may need to check the Excel Trust Center Settings to ensure that ActiveX controls are allowed with only minimal restrictions, and check that the prerequisites are all installed.

You receive a Can't exit design mode because Control 'ExcelDimensionSlicer1' can not be created error during normal operation

This error is caused by some corruption in your saved workbook when saving as Excel 97-2003 format (.xls). It is caused by a limitation of the .xls file format and can occur from time to time when using slicers. To fix the corruption, save the workbook as the more modern .xlsx file format instead. If this is not available to you, the workbook can be temporarily fixed by:

  1. Save the file as .xlsx
  2. Close Excel
  3. Open the .xlsx workbook and resave as .xls

If you are using Microsoft Excel 2003, and are unable to save as .xlsx, you may need to install the Microsoft Office Compatibility Pack, which should allow you to save as the newer .xlsx format. Alternatively, for some workbooks you may be able to save as the XML Spreadsheet (.xml) type instead.

Slicers do not open when clicked

Slicers don't respond when being clicked, instead causing some of the Excel ribbons to become greyed out. This problem is experienced in some configurations, and can be fixed by turning on Optimize for compatibility in Excel:


Publishing Troubleshooting

  • Detailed information can be found here.

Miscellaneous Issues

Error when editing calculated members based on calculated sets

You may receive this error:

The selected calculation could not be executed:
The 'NamedSetName' named set cannot be created because a set with the same name already exists.
Please check the details and try again.

You may receive this error when using a named set in a calculated member created on a non-Measures hierarchy.

For example (based on Adventure Works):

Named Set 'MySet' 
Calculated Member 'MyMember' 

Editing the above results in an error. This is because of a problem executing the necessary MDX with Analysis Services. You should instead use the following, making sure you set the solve order of the calculated member to 1:

Named Set 'MySet' 
Calculated Member 'MyMember' 

In order to successfully create this once the error has been triggered, you will also have to rename the named set.

Searching in the Hierarchy Editor doesn't work

Clicking the Find Member button on the toolbar doesn't appear to do anything, even when matches are present: Troubleshooting search.png

This can happen if the cube doesn't support some of the functions required for case insensitive searching. In this case, set the default Case Sensitivity to Use Database default on the XLCubed Options form.

Connection error when using PivotViews

The following error may be encountered when using PivotView connections (Grid connections based on Excel ranges and table-like data sources):

A connection cannot be made. Ensure that the server is running.
Microsoft.AnalysisServices.AdomdClient.AdomdConnectionException: A connection cannot be made. Ensure that the server is running. ---> 
Microsoft.AnalysisServices.AdomdClient.XmlaStreamException: The 'C:\Users\USERNAME\AppData\Roaming\XLCubed Ltd\XLCubed Excel Edition\PivotViewCache\ID\ID.cub' local cube file cannot be opened. ---> System.ComponentModel.Win32Exception: The operation completed successfully

This indicates that the provider Microsoft SQL Server 2012 Analysis Services 11.0 OLEDB Provider is not installed or has been corrupted. To fix this:

  • Install / reinstall the providers: (x86) and (x64)
  • Remove all Microsoft OLEDB providers and reinstall them

Further Help