Repair (PowerPivot for SharePoint)
Use the information in this topic to repair a multi-server topology that includes two or more PowerPivot for SharePoint servers.
This topic contains the following sections:
You can use SQL Server 2008 R2 installation media to repair a failed or corrupted installation of PowerPivot for SharePoint. Repair will replace missing or corrupted program files, registry keys, and configuration files for the SQL Server instance you select. Repair will not modify SharePoint application and configuration settings, nor will it redeploy the PowerPivot solutions. This is important to understand if you used the New Server option that automatically configured both SharePoint 2010 and PowerPivot for SharePoint. If your goal is to repair all aspects of a New Server deployment, you will now need to manually reconfigure features and settings that were automatically configured during the original installation.
Repair will use the latest version of the program files that are current for your installation. For example, if you installed a service pack, Repair will use the files from the service pack. You do not need to re-apply service packs or patches after you repair your installation.
If you are repairing multiple servers, server availability will fluctuate. Server instances that are lower than the version that is current for the farm will be taken offline automatically. The PowerPivot health rules enforce this behavior to ensure that all server instances are at the same version. Server capacity within the farm is restored to its previous after all servers are running identical versions of PowerPivot for SharePoint.
Repairing a multi-server topology can be time consuming because changes to your deployment must be synchronized across the farm. If you are using SharePoint timer jobs to propagate changes to the farm, it can take up to an hour for PowerPivot server instances to transition to either an offline or online state. During that time, users will encounter errors and low availability for PowerPivot data and query processing, data refresh, and reporting.
To work around this issue, you can run a health rule that detects and then fixes solution version problems.
In Control Panel, in Programs, click Uninstall a program.
Select Microsoft SQL Server 2008 R2 (64-bit)
Specify the location of the installation media. If you have a DVD, insert it and double-click Setup.exe on the disk. Otherwise, if you installed from a network share, enter the UNC path to the installation folder, and then double-click Setup.exe.
In Setup Support Rules, click OK.
In Setup Support Files, click Install, and then click Next.
In Select Instance, choose POWERPIVOT.
Click Next until you get to Ready to Repair, and then click Repair.
Optionally, run a health rule to immediately synchronize the solutions to the expected version. This approach requires that you reset IIS.
In Central Administration, in Monitoring, click Review rule definitions.
In the Configuration category, find and then click the following rule:
PowerPivot: The deployed farm solution is not up-to-date.
In the Health Analyzer Rule Definitions box for this rule, click Run Now.
Reset IIS to ensure the older version is no longer available. To do this, open an Administrator command prompt and type IISRESET.
All versions of PowerPivot System Service and Analysis Services service instances in the farm must be the same version. To verify that all server components are at the same version, check version information for the following:
Microsoft.AnalysisServices.SharePoint.Integration.dll file. This is the file that has the object model for the PowerPivot System Service.
Analysis Services service on each application server that has an installation of PowerPivot for SharePoint.
How to check the version of PowerPivot solutions and PowerPivot System Service
In \Windows\Assembly, find the Microsoft.AnalysisServices.SharePoint.Integration.dll file.
Right-click Microsoft.AnalysisServices.SharePoint.Integration.dll, and select Properties.
File version should be 10.50.<major build>.<minor build>.
There are multiple copies of Microsoft.AnalysisServices.SharePoint.Integration.dll on a PowerPivot for SharePoint server. Copies of the file will be found in the global assembly, \inetpub\wwwroot\wss\VirtualDirectories\80\bin\, and in \Program Files\Microsoft SQL Server\100\SDK\Assemblies.
When checking for file versions in an installation, always use the version that is in the Assembly folder. This is the copy that Setup updates. Other copies of the file are added by the powerpivotwebapp.wsp solution package or by Setup if you install connectivity components.
How to check the version of Analysis Services
In \Program Files\Microsoft SQL Server\MSAS10_50.PowerPivot\OLAP\bin, find msmdsrv.exe.
Right-click msmdsrv.exe, and select Properties.
File version should be 10.50.<major build>.<minor build>.
Verify that this number is identical to the Microsoft.AnalysisServices.SharePoint.Integration.dll file.
After you repair your PowerPivot server, be sure to confirm the server is operational.
Verify the service is running on all computers that run PowerPivot for SharePoint.
Verify feature activation at the site collection level
Verify individual PowerPivot workbooks are loading properly by opening a workbook and clicking on filters and slicers to initiate a query.
Check for the presence of cached files on the hard drive. A cached file confirms that the data file was loaded on that physical server.
Look for cached files in the \Program Files\Microsoft SQL Server\MSAS10_50.POWERPIVOT\OLAP\Backup folder.
Check data refresh reports in PowerPivot Management Dashboard to confirm there are no data refresh errors.
For more information about how to configure PowerPivot settings and features, see Configuration (PowerPivot for SharePoint).
For step-by-step instructions that guide you through all of the post-installation configuration tasks, see Install PowerPivot for SharePoint on an Existing SharePoint Server.