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

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

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.

5/5 (1)

Please rate this

 
Comments

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.

Thanks a life saver

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?

Yes, you need to run the config wizard!

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.

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

I fixed it by installing PowerPivot 2012 not 2014.

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

Cheers!!

You my friend are a Legend.

Cheers

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

Leave a Reply