BACPAC: Could not load schema model from package

When trying to import a BACPAC file, you could run into the following error.


Count not load schema model from package. (Microsoft.SqlServer.Dac)

Additional Information:
Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service. (Microsoft.Data.Tools.Schema.Sql)

This is more than likely due to the version of the Client tools you are using.  If you created a new database, the default version will be the v12 release.  Or you may have upgraded your database to the v12 version.

What's new in SQL Database V12

If you have a v12 database, and you export it to a BACPAC, you could run into the above error if you are importing it into a lower version of SQL.  In my case, I was able to get the error when I tried to import it into SQL 2012 using the Management Studio for SQL 2012.

The issue here is the version of the Client Tools.  In my case, Management Studio.  If I use the SQL 2014 (v12) version of Management Studio to import that BACPAC to my SQL 2012 server, it works successfully.


You can also get the latest Client Tools from the Azure Portal by going to the Server and clicking on the Quick Start icon and click on Get Microsoft database management tools.


Adam W. Saxton | Microsoft SQL Support - Escalation Services
@GuyInACube | Mixes | YouTube |\guyinacube

Comments (5)
  1. Anonymous says:

    Please help.  I have this exact problem but I AM using SQL Server 2014 Management Studio already.  My version number is 12.0.2000.8 which is lower than your's.  Every link I find to express 2014 has the same version number I have.  How did you get that installed?

  2. Martin Johansson says:

    @Alan_Macdonald and anyone else experiencing this issue, This guide helped alot, but the final thing I had to do was to install SQL Server 2014 Service Pack 1 (I guess it wasn't released when this guide was written). I'm on Windows 8.1 and after the update everything works fine!

  3. Ryan White says:

    SQL Management Studio 2014 is still giving me the same error as well.

  4. Dan Kodituwakku says:

    SSMS 2014 was installed (…/SQLEXPRWT_x64_ENU.exe) but I still get the error.

  5. Monish says:

    Thank you very much! I was using SSMS v12 earlier and hence i used to get this error. I tried importing it in v13 and the import was successful.

Comments are closed.

Skip to main content