Home
%3CLINGO-SUB%20id%3D%22lingo-sub-368765%22%20slang%3D%22en-US%22%3EBACPAC%3A%20Could%20not%20load%20schema%20model%20from%20package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-368765%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Apr%2008%2C%202015%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20%3CIFRAME%20frameborder%3D%220%22%20height%3D%22391%22%20src%3D%22https%3A%2F%2Fmix.office.com%2Fembed%2F1l9pdy3la73ei%22%20width%3D%22608%22%3E%20%3C%2FIFRAME%3E%3CP%3EWhen%20trying%20to%20import%20a%20BACPAC%20file%2C%20you%20could%20run%20into%20the%20following%20error.%3C%2FP%3E%0A%20%20%3CBLOCKQUOTE%3E%0A%20%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F88866i65DCA59450AD3E2D%22%20%2F%3E%3C%2FP%3E%0A%20%20%20%3CP%3ECount%20not%20load%20schema%20model%20from%20package.%20(Microsoft.SqlServer.Dac)%3C%2FP%3E%0A%20%20%20%3CP%3EAdditional%20Information%3A%20%3CBR%20%2F%3E%20Internal%20Error.%20The%20database%20platform%20service%20with%20type%20Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider%20is%20not%20valid.%20You%20must%20make%20sure%20the%20service%20is%20loaded%2C%20or%20you%20must%20provide%20the%20full%20type%20name%20of%20a%20valid%20database%20platform%20service.%20(Microsoft.Data.Tools.Schema.Sql)%20%3CBR%20%2F%3E%3C%2FP%3E%0A%20%20%3C%2FBLOCKQUOTE%3E%0A%20%20%3CP%3EThis%20is%20more%20than%20likely%20due%20to%20the%20version%20of%20the%20Client%20tools%20you%20are%20using.%26nbsp%3B%20If%20you%20created%20a%20new%20database%2C%20the%20default%20version%20will%20be%20the%20v12%20release.%26nbsp%3B%20Or%20you%20may%20have%20upgraded%20your%20database%20to%20the%20v12%20version.%3C%2FP%3E%0A%20%20%3CBLOCKQUOTE%3E%0A%20%20%20%3CP%3EWhat's%20new%20in%20SQL%20Database%20V12%20%3CBR%20%2F%3E%20%3CA%20href%3D%22http%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fdocumentation%2Farticles%2Fsql-database-preview-whats-new%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20http%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fdocumentation%2Farticles%2Fsql-database-preview-whats-new%2F%3C%2FA%3E%3C%2FP%3E%0A%20%20%3C%2FBLOCKQUOTE%3E%0A%20%20%3CP%3EIf%20you%20have%20a%20v12%20database%2C%20and%20you%20export%20it%20to%20a%20BACPAC%2C%20you%20could%20run%20into%20the%20above%20error%20if%20you%20are%20importing%20it%20into%20a%20lower%20version%20of%20SQL.%26nbsp%3B%20In%20my%20case%2C%20I%20was%20able%20to%20get%20the%20error%20when%20I%20tried%20to%20import%20it%20into%20SQL%202012%20using%20the%20Management%20Studio%20for%20SQL%202012.%3C%2FP%3E%0A%20%20%3CP%3EThe%20issue%20here%20is%20the%20version%20of%20the%20Client%20Tools.%26nbsp%3B%20In%20my%20case%2C%20Management%20Studio.%26nbsp%3B%20If%20I%20use%20the%20SQL%202014%20(v12)%20version%20of%20Management%20Studio%20to%20import%20that%20BACPAC%20to%20my%20SQL%202012%20server%2C%20it%20works%20successfully.%3C%2FP%3E%0A%20%20%3CBLOCKQUOTE%3E%0A%20%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F88867iDAB3413DBF4A3910%22%20%2F%3E%3C%2FP%3E%0A%20%20%3C%2FBLOCKQUOTE%3E%0A%20%20%3CP%3EYou%20can%20also%20get%20the%20latest%20Client%20Tools%20from%20the%20Azure%20Portal%20by%20going%20to%20the%20Server%20and%20clicking%20on%20the%20%3CSTRONG%3E%20Quick%20Start%20%3C%2FSTRONG%3E%20icon%20and%20click%20on%20%3CSTRONG%3E%20Get%20Microsoft%20database%20management%20tools%20%3C%2FSTRONG%3E%20.%3C%2FP%3E%0A%20%20%3CBLOCKQUOTE%3E%0A%20%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F88868i5BDA5D3F3E032F8F%22%20%2F%3E%3C%2FP%3E%0A%20%20%3C%2FBLOCKQUOTE%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EAdam%20W.%20Saxton%20%7C%20Microsoft%20SQL%20Support%20-%20Escalation%20Services%20%3CBR%20%2F%3E%20%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Fguyinacube%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20%40GuyInACube%20%3C%2FA%3E%20%7C%20%3CA%20href%3D%22https%3A%2F%2Fmix.office.com%2Fuser%2Fcw0m3rxgy39z%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Mixes%20%3C%2FA%3E%20%7C%20%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fchannel%2FUCFp1vaKzpfvoGai0vE5VJ0w%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20YouTube%20%3C%2FA%3E%20%7C%20%3CA%20href%3D%22https%3A%2F%2Fwww.facebook.com%2FGuyInACube%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Facebook.com%5Cguyinacube%3C%2FA%3E%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-368765%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Apr%2008%2C%202015%20When%20trying%20to%20import%20a%20BACPAC%20file%2C%20you%20could%20run%20into%20the%20following%20error.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-368765%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ebacpac%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eimportexport%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft
First published on MSDN on Apr 08, 2015

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
http://azure.microsoft.com/en-us/documentation/articles/sql-database-preview-whats-new/

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 | Facebook.com\guyinacube