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

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. Startup the SQL Server 2008 R2 installer in Admin mode:
  3. Browse to the CD folder of the install media.
  4. Right click “Setup.exe”.
  5. On the popup menu, click “Run as administrator”.

  6. image_60_05C9C7A4
  7. On the SQL Server Installation Center menu, click “Installation”.

  8. image
  9. Click “New installation or add features to an existing installation”.

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

  12. image
  13. Now click “Install” to install the Setup file required.

  14. image
  15. 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”.

  16. image
  17. 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.
  18. Click “Next”.

  19. image
  20. On the Product Key page, select the “Enter the product key” radio button.
  21. Enter your SQL Server 2008 R2 product key that you received from Microsoft in the edit box.
  22. Click “Next”.

  23. image
  24. On the License Terms page, check the “I accept the license terms” checkbox.
  25. Click “Next”.

  26. image
  27. On the Setup Role, select the “SQL Server PowerPivot for SharePoint” radio button.  DO NOT select the SQL Server Feature Installation option.
  28. From the dropdown list box, select “Existing Farm”.
  29. Click “Next”.

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

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

  34. image
  35. On the Instance Configuration page, you cannot change the Named Instance name, but you can change the Instance ID, if you wish.
  36. Click “Next”.

  37. image
  38. On the Disk Space Requirements page, click “Next”.

  39. image
  40. 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.
  41. Enter the domain account ID e.g. “DOMAIN\ServiceAccountName” in the Account Name edit box.
  42. Enter the domain password in the Password edit box.
  43. Leave the Startup Type as “Automatic”.
  44. Click “Next”.

  45. image
  46. On the Analysis Services Configuration page, Setup is asking you to identify the administrators of Analysis Services.
  47. Click “Add Current User”.
  48. The SharePoint Admin Service account should now be listed as an admin.
  49. Click “Add…” to add each account that needs to have Admin rights to Analysis Services and PowerPivot.
  50. Click “Next”.

  51. image
  52. On the Error Reporting page, click “Next”.

  53. image
  54. On the Installation Configuration Rules page, Setup will run some more rules.
  55. Resolve any identified issues and click “Next”.

  56. image
  57. On the Ready to Install page, STOP RIGHT HERE!!!
  58. If you click “Install” here, your installation WILL fail… but you already knew that. 😉  That’s why you’re reading this post. 😀
  59. HACK #1
  60. 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.

  61. image
  62. Open the “ConfigurationFile.ini” file with Notepad.
  63. Using Ctrl+F, locate the reference to “FARMADMINPORT”.

  64. image
  65. 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.
  66. Change the value between the quotes to match the port number of your current Central Admin.

  67. image
  68. Exit and save the .ini file.
  69. HACK #2
  70. 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”.
  71. Copy Microsoft.AnalysisServices.SharePoint.Integration.dll to the PowerPivot bootstrap location of C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x64
  72. 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:
  73. HACK #3
  74. Now we have to ensure that there are no remnants of this dll left over within the GAC.  Open Windows Explorer.
  75. Browse to “C:\Windows\assembly”.
  76. Scroll down and look for Microsoft.AnalysisServices.SharePoint.Integration.
  77. You should not find it because it’s not installed yet.  This was the case in my install as can be seen below.

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

  80. image
  81. Open a command shell via Start/Run/cmd
  82. Execute “cd\windows\assembly\gac_msil” from the command line.
  83. Execute “dir microsoft.analysisservices.s*” from the command line.
  84. 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.
  85. 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.
  86. 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”.
  87. Setup should complete successfully this time around as in my example below:

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


Post a Comment

Comments are moderated only for the purpose of keeping pesky spammers at bay.