none
SQL Server 2012 PowerPivot for Excel RC0 - VSTO 4.0 Exception with SOLUTION

    Question

  • Hi all,

    Background of Problem (see very bottom for solution)

    I've done a lot of research so far on why my PowerPivot tab will not appear in Excel 2010, but can't seem to find the same set of circumstances to mine, so here it goes:

    • OS is Windows 7 Ultimate - 64-bit with SP1 installed (all updates are current)
    • This is a physical machine, not in Hyper-V or VMWare virtual machine
    • Running Microsoft Office Professional Plus 2010 version 14.0.6029.1000 (64-bit)
    • Excel 2010 is running version 14.0.6.112.5000 (64-bit)
    • I've confirmed that .NET Programmability Support is installed
    • Confirmed that all Office Shared Features are installed
    • Installed .NET 4.0 version 4.0.30319 using dotNetFx40_Full_setup installer
    • Installed VSTO 2010 4.0 version 10.0.31119 using vstor40_x64 installer
    • Installed SQL Server 2012 PowerPivot for Excel 64-bit version 11.0.2100.60 using PowerPivot_for_Excel_amd64 installer
    • I have rebooted numerous times.  All installers report successful install.

    What I'm seeing is similar to other posts:

    • PowerPivot for Excel shows up under Inactive Application Add-ins
    • Going into COM Add-ins shows PowerPivot for Excel available but unchecked
    • Check this option and Excel seems to be applying the add-in, however
    • The PowerPivot tab does not appear, even after a OS reboot and/or exiting Excel and re-starting
    • Various posts talk about Excel\Options\Manage\Disabled items, where "Microsoft.AnalysisServices.Modeler.FieldList.Addin.Integration items sometimes appears, but this item is not listed under the disabled items list on my system.
    • The \Program Files\Microsoft Analysis Services\AS Excel Client\110\Microsoft.AnalysisServices.XLHost.Addin.dll shows file version 11.0.2100.60.  One discrepancy I see is that the location description in Excel\Options line item concatenates "...XLHost.Addin.vsto|vstolocal" to the location string.  This is not an existing file or location that I can find, so I'm assuming it is informational.  The ...XLHost.Addin.dll is the actual file name, right?
    • Going back into COM Add-ins, PowerPivot is still unchecked, now displaying the message: "Not loaded.  A runtime error occured during the loading of the COM Add-in.

    Further research into the Event Viewer (application) shows a thrown System.BadImageFormatException with the following key phrase:

    This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

    ** Call stack from Event View Starts **

    Customization URI: file:///C:/Program Files/Microsoft Analysis Services/AS Excel Client/110/
    Exception: Customization could not be loaded because the application domain could not be created.

    ************** Exception Text **************
    Microsoft.VisualStudio.Tools.Applications.Runtime.CannotCreateCustomizationDomainException: Customization could not be loaded because the application domain could not be created. ---> System.BadImageFormatException: Could not load file or assembly 'Microsoft.AnalysisServices.XLHost.Addin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
    File name: 'Microsoft.AnalysisServices.XLHost.Addin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
       at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
       at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
       at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
       at System.Reflection.Assembly.Load(String assemblyString)
       at Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.DomainInitializer.ActivatePipeline(String addInAssembly, String addInClass, String[] pipelineInfo)
       at Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.DomainInitializer.StartAddIn(IntPtr hostServiceProvider, String[] pipeline, String assemblyName, String[] entryPoints)
       at Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.DomainInitializer.StartAddIn(IntPtr hostServiceProvider, String[] pipeline, String assemblyName, String[] entryPoints)
       at Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.LoadMafPipeline(AppDomain newDomain, IntPtr hostServiceProvider, String fullAssemblyName, String[] entryPoints, OfficeApp officeApplication, OfficeVersion officeVersion, IntPtr& executor)
       at Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.CreateCustomizationDomainInternal(String solutionLocation, String manifestName, String documentName, Boolean showUIDuringDeployment, IntPtr hostServiceProvider, Boolean useFastPath, IntPtr& executor)

    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

       --- End of inner exception stack trace ---


    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.5448 (Win7SP1GDR.050727-5400)
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
    ----------------------------------------
    Microsoft.VisualStudio.Tools.Office.Runtime.v10.0
        Assembly Version: 10.0.0.0
        Win32 Version: 10.0.31119.0
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Office.Runtime.v10.0/10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Office.Runtime.v10.0.dll
    ----------------------------------------
    System
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.5453 (Win7SP1GDR.050727-5400)
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Core
        Assembly Version: 3.5.0.0
        Win32 Version: 3.5.30729.5420 built by: Win7SP1
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    Microsoft.VisualStudio.Tools.Applications.Hosting.v10.0
        Assembly Version: 10.0.0.0
        Win32 Version: 10.0.31119.0
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Hosting.v10.0/10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Hosting.v10.0.dll
    ----------------------------------------
    System.AddIn
        Assembly Version: 3.5.0.0
        Win32 Version: 3.5.30729.5420 built by: Win7SP1
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.AddIn/3.5.0.0__b77a5c561934e089/System.AddIn.dll
    ----------------------------------------
    Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0
        Assembly Version: 10.0.0.0
        Win32 Version: 10.0.31119.0
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0/10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0.dll
    ----------------------------------------
    Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0
        Assembly Version: 9.0.0.0
        Win32 Version: 9.0.30729.4130
        CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0/9.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0.dll
    ----------------------------------------

    ** Call stack from Event View ENDS **

    SOLUTION

    While working with one of my other computers, I noticed a discrepancy between the .NET installers.  On this other system, where the new PowerPivot 2012 version had installed correctly, My Control Panel\Add Remove Programs\ showed that I had the Microsoft .NET Framework 4 Extended version 4.0.30319 installed, but on the computer where the install was failing, it showed: Microsoft .NET Framework 4 Client Profile also with version 4.0.30319.

    Key point: I made a bad assumption that I would not need to run the dotNetFx40_Full_setup installer because I saw that I already had the Microsoft .NET Framework 4 Client Profile installed with the proper version.  There must be something different in the installers because it now works!

    Solution: I installed the dotNetFx40_Full_setup installer and went back into to Excel Options\COM Add-ins and checked-off the PowerPivot for Excel item and when it applied, the tab appeared!


    Regards, Scott

    Monday, March 19, 2012 9:47 PM

Answers

All replies

  • Hello Scott,

    the .NET Client Profile is a reduced set of .NET Framework, but as you can read in the installation instructions for PowerPivot the complete framework 4.0 is required as well as the VSTO runtime.


    Olaf Helper
    * cogito ergo sum * errare humanum est * quote erat demonstrandum *
    Wenn ich denke, ist das ein Fehler und das beweise ich täglich
    Blog Xing


    Monday, March 19, 2012 10:34 PM
  • I have the same problem - I uninstalled the .NET Extended and Client Profile and then reinstalled using the Full_setup.  It put the Client Profile and Extended back, but I still get the same error starting the PowerPivot COM add-in.

    Should I be seeing:

    Microsoft .NET Framework 4 Client Profile 4.0.30319

    Microsoft .NET Framework 4 Extended 4.0.30319

    I had to install the PowerPivot software using a cmd window running as Admin.  I have been trying to install this for over a month now.  There are dozens of sites with solutions - each one is different!

    Friday, April 20, 2012 1:25 PM