Given how much effort is was to get PowerPivot installed and working in the first place, you may never need this post, but just in case something goes wrong and you have to uninstall it to start over, here’s how to do that:
Launch Programs and Features via Start/Control Panel/Uninstall a Program.
Locate the “Microsoft SQL Server 2008 R2 (64-bit)” entry and select it with a left click.
The Uninstall/Change button becomes active. Click it.
Windows may warn you that there are other users that’ll be affected.
Click “Continue” to ignore the warning and proceed.The SQL Server configuration tool opens.Click “Remove”.Setup will load all the support rules.Once all rules were loaded, click “OK”.Change the “Instance to remove feature from” dropdown value to “POWERPIVOT”.Click “Next”.Ensure that “Analysis Services” and it’s sub categories under POWERPIVOT is checked.Click “Next”.Setup runs all the removal rules.Once the rules have run successfully, click “Next”.On the Ready to Remove screen, click “Remove”.Once setup has removed PowerPivot, you’ll be taken to the Complete screen.The status should indicate that the removal was successful.Click “Close”.
TROUBLE SHOOTING TIP
If you have previously removed PowerPivot and am trying to reinstall it again, the installation may fail because the removal didn’t cleanup everything properly.
If you install PowerPivot and go to the Solution administration page, there’s a .wsp for PowerPivot called “powerpivotfarm.wsp”. If this solution shows an error with a message of “Some of the files failed to copy during deployment of the solution”, then the uninstaller didn’t cleanup everything successfully.
Looking at the error above, the Microsoft.AnalysisServices.SharePoint.Integration.dll assembly didn’t get deployed to the GAC.
If you browse to the GAC via Windows Explorer, you’ll see this:
OK, so it is NOT there. That’s what we expected because that’s what the error indicated.
Ah… but wait… there’s more…
Open a command prompt on the server.
Now manually change directory to the GAC_MSIL folder and do it dir for that DLL.
And what do we get?…
It seems that the folder was not cleaned up successfully during a past uninstall. The installer isn’t smart enough to figure out that’s the right folder to put the DLL and simply throws an error. It wants to create the folder from scratch.
Us the RD command to remove the offending folder and then retry your installation. Odds are it’ll work this time.
Trackback from your site.