The Microsoft OLE DB Provider for Analysis Services (MSOLAP) is an interface that client applications use to interact with Analysis Services data. In a SharePoint environment that includes PowerPivot for SharePoint, the provider handles connection requests for PowerPivot data.
The data provider is included in the PowerPivot for SharePoint installation package (spPowerPivot.msi), but might require manual installation. There are two reasons why you might need to manually install a client library or data provider on a SharePoint server.
Enable backwards compatibility. SQL Server 2008 R2 workbooks specify the SQL Server 2008 R2 version of the Analysis Services OLE DB provider in their connection string. As such, this provider version must be present on the computer in order for the request to succeed.
Enable data access on a dedicated Excel Services instance. If your SharePoint farm includes Excel Services on a server that does not also have PowerPivot for SharePoint, install the SQL Server 2012 SP1 version of the provider and other client connectivity components by using the PowerPivot for SharePoint installation package.
These scenarios are not mutually exclusive. Hosting multiple workbook versions on a farm that includes application servers running Excel Services without a PowerPivot for SharePoint instance will require that you install both older and newer versions of the data provider on each Excel Services computer.
In this topic:
Versions of the OLE DB Provider Supporting PowerPivot Data Access
Why you need to install the OLE DB Provider
Install the SQL Server 2012 OLE DB Provider and client connectivity components on standalone Excel Services servers
Use the PowerPivot for SharePoint Installation package (spPowerPivot.msi) to Install the SQL Server 2012 OLE DB
Install the SQL Server 2008 R2 OLE DB Provider to host earlier version workbooks
A SharePoint farm might include multiple versions of the Analysis Services OLE DB provider, including older versions that do not support PowerPivot data access.
By default, SharePoint 2010 installs the SQL Server 2008 version of the provider. Although it is identified as MSOLAP.4 (the same version number used for SQL Server 2008 R2), this version does not work for PowerPivot data access. In order for connections to succeed, you must have the SQL Server 2008 R2 or SQL Server 2014 version of the provider.
A post SQL Server 2008 version of the OLE DB provider includes transports and connection support for PowerPivot data structures. PowerPivot workbooks use newer versions of this provider to request query processing from PowerPivot servers in the farm. To get an updated version, you can download and install it through a SQL Server Feature Pack page.
The following table describes the valid versions:
SQL Server 2008 R2
MSOLAP100.dll in the file system
MSOLAP.4 in an Excel connection string
10.50.1600 or later in file version details
Use for data models created using the SQL Server 2008 R2 version of PowerPivot for Excel.
SQL Server 2012
MSOLAP110.dll in the file system
MSOLAP.5 in an Excel connection string
11.0.0000 or later in file version details
Use for data models created using the SQL Server 2012 or SQL Server 2014 version of PowerPivot for Excel.
SQL Server 2014
MSOLAP120.dll in the file system
12.0.20000 or later in file version details
Use for data models other than PowerPivot models.
There are two scenarios that call for manually installing the OLE DB provider on servers in the farm.
The most common scenario is when you have older and newer versions of PowerPivot workbooks that are saved in document libraries in the farm. If analysts in your organization are using the SQL Server 2008 R2 version of PowerPivot for Excel, and they save those workbooks to a SQL Server 2012 PowerPivot for SharePoint installation, the older workbook will not work. Its connection string will reference an older version of the provider, which won’t be on the server unless you install it. Installing both versions will enable data access for PowerPivot workbooks created in older and newer versions of PowerPivot for Excel. SQL Server 2012 Setup does not install the SQL Server 2008 R2 version of the provider, so you must install it manually if you are using workbooks from a previous version.
The second scenario is when you have a server in a SharePoint farm that runs Excel Services, but not PowerPivot for SharePoint. In this case, the application server that runs Excel Services must be manually updated to use a newer version of the provider. This is necessary for connecting to a PowerPivot for SharePoint instance. If Excel Services is using an older version of the provider, the connection request will fail. Note that the provider must be installed by using SQL Server setup or the PowerPivot for SharePoint installation package (spPowerPivot.msi) in order to ensure that all components required support PowerPivot are installed.
Use the following instructions to add the OLE DB provider and other client connectivity components to SharePoint servers that do not already have them installed, such as application servers that run Excel Services without PowerPivot for SharePoint on the same hardware.
Use these instructions to install the current Analysis Services OLE DB provider and to add the Microsoft.AnalysisServices.Xmla.dll to the global assembly.
Run SQL Server Setup and Install the Client Connectivity Tools
On the application server that hosts Excel Services, run SQL Server Setup.
On the Installation page, choose New SQL Server stand-alone installation or add features to an existing installation.
On the Installation Type page, choose Perform a new installation of SQL Server 2012.
On the Setup Role page, choose SQL Server Feature Installation.
On the Feature Selection page, click Client Tools Connectivity. This option installs Microsoft.AnalysisServices.Xmla.dll
Do not select any other features.
Click Next to finish the wizard, and then click Install to run Setup.
Repeat the previous steps if you have other servers running Excel Services, without a PowerPivot for SharePoint installation on the same server.
Verify MSOLAP.5 is a trusted provider
In Central Administration, click Manage service applications, and then click the Excel Services service application.
Click Trusted Data Providers.
Verify that MSOLAP.5 appears in the list. Depending on how you configured PowerPivot for SharePoint, MSOLAP.5 might already be trusted. If you used the PowerPivot Configuration tool, but then excluded this action from the task list, MSOLAP.5 will not be trusted by Excel Services and now needs to be added manually.
If MSOLAP is not listed, click Add Trusted Data Provider.
In Provider ID, type MSOLAP.5.
For Provider Type, ensure that OLE DB is selected.
In Provider Description, type Microsoft OLE DB Provider for OLAP Services 11.0.
Go to Program files\Microsoft Analysis Services\AS OLEDB\110.
Right-click msolap110.dll and select Properties.
View the file version information. The version should include 11.00.<buildnumber>.
In the Windows\assembly folder, verify that Microsoft.AnalysisServices.Xmla.dll, version 220.127.116.11, is listed.
Install the SQL Server 2012 SP1 OLE DB Provider on and Excel Services Server by using the PowerPivot for SharePoint installation package (spPowerPivot.msi).
Download the MSOLAP.5 provider from the SQL Server 2012 SP1 Feature Pack.
Click Install Instructions.
See the section “Microsoft Analysis Services OLE DB Provider for Microsoft SQL Server 2012 SP1”. Download the file and start the installation.
On the Feature Selection page, select Analysis Services OLE DB Provider for SQL Server. Unselect the other components and complete the installation. For more information on spPowerPivot.msi, see Install or Uninstall the PowerPivot for SharePoint Add-in (SharePoint 2013).
Register MSOLAP.5 as a trusted provider with SharePoint Excel Services. For more information, see Add MSOLAP.5 as a Trusted Data Provider in Excel Services.
Use the following instructions to install the SQL Server 2008 R2 version of the MSOLAP.4 provider, and register the Microsoft.AnalysisServices.ChannelTransport.dll file. The ChannelTransport is a subcomponent of the Analysis Services OLE DB provider. The SQL Server 2008 R2 version of the provider reads the registry when using ChannelTransport to make a connection. Registering this file is a post-installation step required only for connections handled by the SQL Server 2008 R2 provider on a SQL Server 2012 server.
Step 1: Download and install the client library
On the SQL Server 2008 R2 Feature Pack page, find Microsoft Analysis Services OLE DB Provider for Microsoft SQL Server 2008 R2.
Download the x64 Package of the SQLServer2008_ASOLEDB10.msi installation program. Although the file name contains SQLServer2008, it is the correct file for the SQL Server 2008 R2 version of the provider.
On the computer that has an installation of PowerPivot for SharePoint, run the .msi to install the library.
If you have other servers in the farm that run just Excel Services, without PowerPivot for SharePoint on the same server, repeat the previous steps to install the 2008 R2 version of the provider on the Excel Services computer.
Step 2: Register the Microsoft.AnalysisServices.ChannelTransport.dll file
Use the regasm.exe utility to register the file. If you have not run regasm.exe before, add its parent folder, C:\Windows\Microsoft.NET\Framework64\v4.0.30319\, to the system path variable.
Open a command prompt with administrator permissions.
Go to this folder C:\Windows\assembly\GAC_MSIL\Microsoft.AnalysisServices.ChannelTransport\10.0.0.0__89845dcd8080cc91
Enter the following command: regasm microsoft.analysisservices.channeltransport.dll
Repeat the previous steps for any computer on which you manually installed the 2008 R2 version of the provider.
You should now be able to slice or filter SQL Server 2008 R2 workbooks. If an error occurs, verify that you used the 64-bit version of regasm.exe to register the file.
Additionally, you can check the file version.
Go to C:\Program files\Microsoft Analysis Services\AS OLEDB\10. Right-click msolap100.dll and select Properties. Click Details.
View the file version information. The version should include 10.50.<buildnumber>.