Search code examples
sql-serverssmssql-server-data-tools

Error importing bacpac using Sql Server Management Studio 2016 - could not load file or assembly Microsoft.SqlServer.Dac

I made .bacpac file from Azure portal and save it to Desktop. Then in Management Studio 2016 Candidate right clicking on Databases and choosing Import data tier application i am targeting my file then next... and when it goes to process i am getting error:

Could not load file or assembly 'Microsoft.SqlServer.Dac, Version = 13.0.0.0, Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a' or one of its dependencies. You can not find the file specified. (Microsoft.SqlServer.Management.Dac.DacWizard)

I was searching over google but i couldn't find any working solution on it. Could you help?

Check also this picture about configuration:

SQL configuration

Solution

  • This is due to a bug in SSMS that should be fixed in a future release. The issue is that if you have Lightswitch for VS2015 installed, the binding paths used by SSMS to lookup DLLs will include a reference to an earlier 110 version of the DacFx DLLs before the 130 version. This results in the above error since by default Visual Studio returns the first matching DLL.

    Solution:

    1. Open "C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\ManagementStudio\ssms.pkgundef" in a text file viewer. You will need to run this viewer as Administrator in order to edit it

    2. Add the following line to ensure that in the future, the 110 binding path is ignored and save the file:

      [$RootKey$\BindingPaths\{272EA915-68EE-4AFD-99A4-1286126565EC}]

    3. Next we need to remove it from the registry as it's already been added once. Open Regedit.exe and navigate to "HKEY_CURRENT_USER\SOFTWARE\Microsoft\SQL Server Management Studio\13.0_Config\BindingPaths"

    4. Delete the folder {272EA915-68EE-4AFD-99A4-1286126565EC} from under this key.

    Note: This will only happen on machines with VS2015 installed and the Lightswitch package installed in this. The cause is that VS2015 binding paths are included in Isolated Shell applications like SSMS unless the pkgundef file excludes them. A fix will be included in an upcoming release.

    Disclosure: I work on the SQL Server tools team.