This article consists of troubleshooting tips and techniques for working through installation and configuration problems for SQL Server 2008 R2 version of PowerPivot for SharePoint.
Please update this page to include any new information or links that you think will be helpful to others.
Click Sign In at the top of the page and enter your Windows Live ID or Hotmail account.
When the page reloads, you will see an Edit tab. Click
Edit to add to this page. Thanks for your help in keeping this page useful and up to date!
Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$POWERPIVOT
SQL Server 2012
find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$POWERPIVOT (SQL Server Failover Cluster and PowerPivot for SharePoint)
The version number of the local SQL Server Analysis Services (PowerPivot) instance does not match the version associated with program files on the computer. This might occur if there is a failure during setup. The setup extension timer job is being started
which should correct the problem.
SQL Server 2012
This error can occur when you open or refresh a PowerPivot workbook on SharePoint, after upgrading to SQL Server 2012 version of PowerPivot for SharePoint. To resolve this error, run the PowerPivot Configuration Tool and select the upgrade option, then
retry opening the workbook.
An instance of SQL Server Analysis Services (PowerPivot) does not exist in the farm.
SQL Server 2008 R2
This error occurs when you try to install or reinstall PowerPivot for SharePoint, and bits from a previous installation block any subsequent installs.
Check the programs that are installed on your computer. If just one component from a prior installation of SQL Server 2008 R2 was not fully removed, Setup will attempt to a repair operation rather than the reinstall you expect, which will most likely fail
with the above error. To confirm, review the most recent log file to find out whether Setup detected attempted a repair action.
Resolve this problem by uninstalling any Analysis Services client library that appears in the Programs list and then retry Setup. Note that this problem is more likely to occur if you ran Setup multiple times, perhaps installing a native mode Analysis Services
instance first, or installing an Analysis Services redistributable program such as Analysis Services Management Objects (AMO), prior to installing PowerPivot for SharePoint.
Applies to: SQL Server 2008 R2
This error occurred when attempting to create a PowerPivot service application.
Resolved by repairing the installation, and then retried creating the service application. You must be a local admin to run SQL Server Setup. To repair the installation, go to Programs and Features, select Microsoft SQL Server 2008 R2 (64-bit), click Uninstall/Change,
and click Repair. You will be asked to pick the SQL Server instance to repair. Choose 'PowerPivot'. You will also be asked to specify the location of the Setup files.
In my case, I had previously installed SQL Server 2008 R2 SP1 on this machine. I did not have to reapply SP1 as a post-repair operation. SP1 features were available after the repair was finished.
SQL Server 2008 R2
In SQL Server 2008 R2, the msmdsrv.exe process (which is the SSAS engine) includes a reference to the PowerPivot SharePoint integration dll (as do other components). Since the normal SSAS installation does not include the SharePoint integration dll, the
registration marks the .NET assembly cache as failed. Later on, when you install PowerPivot, we copy the SharePoint integration dll to the right place, but the .NET assembly cache has already been marked failed from the previous SSAS installation and .NET
does not attempt to load it (and you get the error message above).
Recommended solution: If you are using "New Server" PowerPivot installation option, then delay installing any instances besides SQL Server RDMBS until
after you have PowerPivot installed and configured. That way you never hit this error condition.
Save the following code to to a file and name it as "setup100.exe.config" (no .txt extension)
encoding="utf-8" ?> <BR><configuration>
<BR> <runtime> <BR>
enabled="1" /> <BR> </runtime>