How do I – Install PowerPivot into an EXISTING SharePoint 2010 farm

Written by Cornelius J. van Dyk on . Posted in How Do I...

This one was a BEAR to work through.  There’s not much out there for it and everywhere I turned it seems everyone else was either having the same problem OR suggestion we “start with a clean install”.  Nice suggestion that last one.  Almost like… try rebooting the computer… but I digress.  So hopefully this guide will help some other poor soul save some time when they run into the same issue.

  1. Due to a farm admin error during PowerPivot install that incorrectly claims that the current user is NOT a Farm Administrator, you’ll need to logon to your SharePoint server, using the SharePoint Admin Service account credentials.

  2. Install the Microsoft Access Database Engine 2010 Redistributable.

  3. Startup the SQL Server 2008 R2 installer in Admin mode:

  4. Browse to the CD folder of the install media.

  5. Right click “Setup.exe”.

  6. On the popup menu, click “Run as administrator”.

  7. image_60_05C9C7A4

  8. On the SQL Server Installation Center menu, click “Installation”.

  9. image

  10. Click “New installation or add features to an existing installation”.

  11. image

  12. On the Setup Support Rules page, correct any issues that are identified and then click “OK”.

  13. image

  14. Now click “Install” to install the Setup file required.

  15. image

  16. On the Setup Support Rules page, Setup will run it’s support rules to check for valid install.  Correct any issues that are identified and then click “Next”.

  17. image

  18. On the Installation Type page, Setup will list already installed instances of SQL Server.  Here you want to select “New installation or add shared features”.  DO NOT select the “Add features…” option.

  19. Click “Next”.

  20. image

  21. On the Product Key page, select the “Enter the product key” radio button.

  22. Enter your SQL Server 2008 R2 product key that you received from Microsoft in the edit box.

  23. Click “Next”.

  24. image

  25. On the License Terms page, check the “I accept the license terms” checkbox.

  26. Click “Next”.

  27. image

  28. On the Setup Role, select the “SQL Server PowerPivot for SharePoint” radio button.  DO NOT select the SQL Server Feature Installation option.

  29. From the dropdown list box, select “Existing Farm”.

  30. Click “Next”.

  31. image

  32. On the Feature Selection page, Setup will show you the installation options to be added.  These cannot be changed.  Click “Next”.

  33. image

  34. On the Installation Rules page, Setup will run rules to check for blocks.  Correct any issues that are identified and then click “Next”.

  35. image

  36. On the Instance Configuration page, you cannot change the Named Instance name, but you can change the Instance ID, if you wish.

  37. Click “Next”.

  38. image

  39. On the Disk Space Requirements page, click “Next”.

  40. image

  41. On the Server Configuration page, Setup requires that you configure an account for SQL Server Analysis Services.  Best Practices dictates that this should NOT be a network service or system account, but rather it should be a dedicated domain account.

  42. Enter the domain account ID e.g. “DOMAIN\ServiceAccountName” in the Account Name edit box.

  43. Enter the domain password in the Password edit box.

  44. Leave the Startup Type as “Automatic”.

  45. Click “Next”.

  46. image

  47. On the Analysis Services Configuration page, Setup is asking you to identify the administrators of Analysis Services.

  48. Click “Add Current User”.

  49. The SharePoint Admin Service account should now be listed as an admin.

  50. Click “Add…” to add each account that needs to have Admin rights to Analysis Services and PowerPivot.

  51. Click “Next”.

  52. image

  53. On the Error Reporting page, click “Next”.

  54. image

  55. On the Installation Configuration Rules page, Setup will run some more rules.

  56. Resolve any identified issues and click “Next”.

  57. image

  58. On the Ready to Install page, STOP RIGHT HERE!!!

  59. If you click “Install” here, your installation WILL fail… but you already knew that. 😉  That’s why you’re reading this post. 😀

  60. HACK #1

  61. At the bottom of the window, Setup is displaying the path to the “ConfigurationFile.ini” file.  Copy the path to the file.  We have to pause the install here because the location of this .ini file changes on every install as Setup will take the current date/time stamp and use it for the …Log\<YYYYMMDD_HHMMDD>\… part of the folder location.

  62. image

  63. Open the “ConfigurationFile.ini” file with Notepad.

  64. Using Ctrl+F, locate the reference to “FARMADMINPORT”.

  65. image

  66. Your port number will show something random.  This is because PowerPivot assumes that its installing at the same time as a default SharePoint install.  Since we already have SharePoint installed, we need to edit this value and change it to match the port of our Central Admin location.

  67. Change the value between the quotes to match the port number of your current Central Admin.

  68. image

  69. Exit and save the .ini file.

  70. HACK #2

  71. The other problem with the current PowerPivot install is that it looks for the Microsoft.AnalaysisServices.SharePoint.Integration.dll file in the bootstrap folder, but it doesn’t exist there.  In past failed installs of PowerPivot, you may have encountered references to this DLL being “missing”.

  72. Copy Microsoft.AnalysisServices.SharePoint.Integration.dll to the PowerPivot bootstrap location of C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x64

  73. You may, or may not have a copy of this DLL file handy.  If you don’t, you can download the copy I placed on my SkyDrive here:


  75. HACK #3

  76. Now we have to ensure that there are no remnants of this dll left over within the GAC.  Open Windows Explorer.

  77. Browse to “C:\Windows\assembly”.

  78. Scroll down and look for Microsoft.AnalysisServices.SharePoint.Integration.

  79. You should not find it because it’s not installed yet.  This was the case in my install as can be seen below.

  80. image

  81. That’s not necessarily true though as can be seen from my environment screen shot below:

  82. image

  83. Open a command shell via Start/Run/cmd

  84. Execute “cd\windows\assembly\gac_msil” from the command line.

  85. Execute “dir microsoft.analysisservices.s*” from the command line.

  86. Your output SHOULD show 0 files and 0 dirs.  If it doesn’t, like in my example above, the odds are you’ve had a failed install of AnalysisServices before and remnants were left behind when the installer didn’t cleanup behind itself.

  87. If there is a folder named “Microsoft.AnalysisServices.SharePoint.Integration”, you need to delete it by executing “rd  Microsoft.AnalysisServices.SharePoint.Integration” from the command line.

  88. Now that we’ve cleared the path for the installer by deleting remnants from the GAC, hacking the configuration file and manually providing a copy of the integration DLL, we can switch back to Setup and click “Install”.

  89. Setup should complete successfully this time around as in my example below:

  I hope this saves somebody some time and frustration out there.



Tags: , , ,

Trackback from your site.

Cornelius J. van Dyk

Born and raised in South Africa during the 70's I got my start in computers when a game on my Sinclair ZX Spectrum crashed, revealing it's BASIC source code. The ZX had a whopping 48K of memory which was considered to be a lot in the Commodore Vic20 era, but more importantly, it had BASIC built into the soft touch keyboard. Teaching myself to program, I coded my first commercial program at age 15.

After graduating high school at 17, I joined the South African Air Force, graduating the Academy and becoming a Pilot with the rank of First Lieutenant by age 20. After serving my country for six years, I made my way back into computer software.

Continuing my education, I graduated Suma Cum Laude from the Computer Training Institute before joining First National Bank where my work won the Smithsonian Award for Technological Innovation in the field of Banking and Insurance. Soon I met Will Coleman from Amdahl SA, who introduced me to a little known programming language named Huron/ObjectStar. As fate would have it, this unknown language and Y2K brought me to the USA in 1998.

I got involved with SharePoint after playing around with the Beta for SharePoint Portal Server 2003. Leaving my career at Rexnord to become a consultant in 2004, I was first awarded the Microsoft Most Valuable Professional Award for SharePoint in 2005, becoming only the 9th MVP for WSS at the time. I fulfilled a life long dream by pledging allegiance to the Flag as a US citizen in 2006. I met the love of my life and became a private consultant in 2008. I was honored to receive my ninth MVP award for SharePoint Server in 2013.

Leave a comment

You must be logged in to post a comment.