I. Install Microsoft.AnalysisServices.dll and Microsoft.AnalysisServices.AdomdClient.dll components on the web server and the database server where the data warehouse is located. You may be prompted for a restart after installing these components on the server. If so, restart the webserver after installation per instructions.

Both files can be found at http://www.microsoft.com/en-us/download/details.aspx?id=16978. Install ADOMD.NET to download the Microsoft.AnalysisServices.AdomdClient.dll file, and Analysis Management Objects to install the Microsoft.Analysis.Services.dll file.

If you use SQL Server 2012 or SQL Server 2014 you will need both the 2008 and either 2012\2014 versions of ADOMD.NET. See guide below for setting up a webserver for use with Blackbaud CRM:


Microsoft links to 2012 and 2014 versions of ADOMD.NET:

Microsoft SQL Server 2012 Feature Pack:

Microsoft SQL Server 2014 Feature Pack:
II. If this does not resolve the issue, replace the following section in the web.config file (ensure that a copy of the current web.config file is saved before editing):

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="bin\custom" />

With this:

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

<!-- This probing section below should be uncommented if the infinity application needs to allow custom components to be uploaded and deployed
through the application (using functionality in DevSpace.Catalog)

<!-- <probing privatePath="bin\custom" /> -->

<!-- pdg 9.2.2009 redirect the Dundas OLAP controls to use the new SQL 2008 AdomdClient assembly. -->
<assemblyIdentity name="Microsoft.AnalysisServices.AdomdClient" publicKeyToken="89845dcd8080cc91"/>
<bindingRedirect oldVersion="" newVersion=""/>


III. If receiving this error while deploying the data warehouse from the webserver, do the following:

a. As stated in Step I make sure the referenced components are installed on the webserver. A work around to this is to share out the \Blackbaud\bbappfx\MSBuild\Datamarts\bin folder and then from the Blackbaud Data Warehouse server navigate to that shared path and then run the Blackbaud.AppFx.ReportDB.Installer.exe there as most likely the database server will already have those components installed. If the error still persists even when running from the shared folder directly on the Blackbaud Data Warehouse server then make sure that those components are installed on the BBDW server as well.

b. Add the following lines to the runtime section of the Blackbaud.AppFx.ReportDB.Installer.exe.config file located here, \Blackbaud\bbappfx\MSBuild\Datamarts\bin. See file called Blackbaud.AppFx.ReportDB.Installer.exe.config:

   <loadFromRemoteSources enabled="true"/>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

      <assemblyIdentity name="Microsoft.AnalysisServices" publicKeyToken="89845dcd8080cc91" />
      <bindingRedirect oldVersion="" newVersion="" />



If this issue still persists, the following has worked has been needed in some self-hosted environments; make sure that the following directories exist, on the CRM web server, with the specified content:

C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\bin (zip up the Internet Server Application Programming Interface directory from the SQL SSAS on the BBDW SQL Server and extract to this location).


C:\Windows\assembly\GAC_MSIL\Microsoft.AnalysisServices\ (make sure that the Microsoft.AnalysisServices.DLL is copied from SSAS and placed in this directory).