Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


Assume that you apply Microsoft SQL Server 2012 Service Pack 1 (SP1) on a computer that has Microsoft SQL Server Management tools (including Microsoft SQL Server 2012 Analysis Services tools) installed. When you try to edit the connection string for a data source by opening the Specify Configuration Properties dialog box in the Analysis Services Deployment Wizard tool, you receive the following error message:

Could not load file or assembly 'Microsoft.Data.ConnectionUI, Version=,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
The located assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040)


This issue occurs because of incorrect references to the Microsoft.Data.ConnectionUI.dll and Microsoft.Data.ConnectionUI.Dialog.dll files in the manifest for the Microsoft.DataWarehouse.dll file.


Cumulative update information

Cumulative Update 3 for SQL Server 2012 Service Pack 1 (SP1)

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012 SP 1, click the following article number to view the article in the Microsoft Knowledge Base:

2812412 Cumulative update package 3 for SQL Server 2012 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 SP 1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


To work around this issue, follow these steps:

  1. Open the following configuration file in a text editor, such as Notepad, as an administrator:

    <system drive>:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Microsoft.AnalysisServices.Deployment.exe.config

  2. Insert the runtime XML tags after the </startup> tag in the configuration section:

    <requiredRuntime version="v4.0.30319" safemode="true" />
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <assemblyIdentity name="Microsoft.Data.ConnectionUI" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
    <bindingRedirect oldVersion="" newVersion=""/>
    <assemblyIdentity name="Microsoft.Data.ConnectionUI.Dialog" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
    <bindingRedirect oldVersion="" newVersion=""/>
  3. Save the configuration file.

  4. Run Microsoft.AnalysisServices.Deployment.exe, and try the database deployment again.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!