15 49.0138 8.38624 1 0 4000 1 https://vladtalkstech.com 300 1
theme-sticky-logo-alt

Configuration Failed – Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin

10 Comments

I was at a client recently and was trying to add a new SharePoint Server to the farm, and everything went well until I tried to run the SharePoint Products Configuration Wizard. The error was:

Task configdb has failed with an unknown exception Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91. Could not load file or assembly ‘Microsoft.AnalysisServices.SPClient, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The system cannot find the file specified.

 123014_0212_Configurati1

The problem is that the rest of the farm had the PowerPivot enabled, and therefore the PowerPivot Addin is required. Unfortunately, This Add-in is not verified at the begging of the SharePoint Products Configuration Wizard standard check, so that is why you get to this error. A recommended best practice is to install spPowerPivot.msi on all servers in the SharePoint farm for configuration consistency, including application servers and web-front end servers. The installer package includes the Analysis Services data providers as well as the PowerPivot for SharePoint 2013 configuration tool. To fix the problem, simply download the installer file from Microsoft Download Center: Microsoft® SQL Server® 2014 PowerPivot for Microsoft SharePoint®, run it on your server and then re-run the SharePoint Products Configuration Wizard. Everything should work perfectly!

Drop a comment if this helped!

Leave a comment and don’t forget to like the Absolute SharePoint Blog Page  on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

Previous Post
SharePoint 2013 SSRS – The remote server returned an error: (500) Internal Server Error
Next Post
Easily Compare Office 365 Plans

10 Comments

  • April 8, 2015 at 2:32 am
    Samar

    Thank you, real world scenario this is common to see, thanks for posting detail, it also saves time not installing powerpivot using sql server installation disk.

    Reply
  • April 13, 2015 at 8:30 am
    Chris

    Thanks a life saver

    Reply
  • October 16, 2015 at 10:20 am
    Matt

    I’m still getting the error after running the sppowerpivot.msi on the server that I am adding to my far. Do I run the configuration tool?

    Reply
    • October 17, 2015 at 12:27 am

      Yes, you need to run the config wizard!

      Reply
      • October 18, 2015 at 6:26 am
        Matt

        It is still failing…how do I run the PowerPivot configuration tool on the new server if I haven’t successfully run PSConfig to configuration SP on it for the first time? The server that is currently in the farm has PowerPivot and SP already configured and everything is running fine.

  • December 1, 2015 at 11:09 am

    Same issue here – I believe this is directly causing the OWSTIMER.EXE to fail. I’ll feedback on progress as I’m currently installing Microsoft® SQL Server® 2014 PowerPivot for Microsoft SharePoint®, I can;t run the config wizard because the solutions won’t install due to the Timer Service not running

    Reply
  • December 28, 2015 at 12:47 pm
    Matt

    I fixed it by installing PowerPivot 2012 not 2014.

    Reply
  • February 3, 2016 at 7:49 am
    pradeep

    Yes this helped, but we have just selected sharepoint powerpivot while installing this msi

    Cheers!!

    Reply
  • March 24, 2017 at 1:17 am
    Aron

    You my friend are a Legend.

    Cheers

    Reply
  • April 19, 2017 at 10:52 am
    Phil

    When you read the answer you cant help but hit your head on the wall a few times! Thank you for this…

    Reply

Leave a Reply