DB Project won't load in Visual Studio 2013

Question

The error says:

Failed to create extension manager for the target platform 'Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider'.

My teammate created the DB Project, but when I pulled it down from source control it failed to create.

Pearman

Answer 1

The solution is to get an update to the "SQL Server Data Tools". You apparently have an older version.

Look in Visual Studio 2013 under Tools-->Extentions and Updates. On the left pane from there, click on Updates. Hopefully you'll be able to find the update you need there.

(Alternatively, run a repair installation on "SQL Server Data Tools" under Windows' Control Panel-->Programs.)

Henrie

this was helpful, note I had to shut down VS2013 and reopen after the install of the SSDT update. – Jamarjamb

I got this error today and I don't have an SSDT update listed under Extensions and Updates. So, I ran a repair on Microsoft SQL Server Data Tools 2013 and that worked. – Mowry

Answer 2

I fixed this problem by lowering the required version of the tools. I'm not sure why they are installed on his machine and not on mine, but edit the dbproj file and change the requirement to a lower version, like this:

Original:

<SchemaVersion>2.0</SchemaVersion>
<ProjectVersion>4.1</ProjectVersion>
<ProjectGuid>{......}</ProjectGuid>
<DSP>Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider</DSP>
<OutputType>Database</OutputType>
<RootPath>
</RootPath>

Updated: (don't include the *'s)

<SchemaVersion>2.0</SchemaVersion>
<ProjectVersion>4.1</ProjectVersion>
<ProjectGuid>{......}</ProjectGuid>
**<DSP>Microsoft.Data.Tools.Schema.Sql.Sql110DatabaseSchemaProvider</DSP>**
<OutputType>Database</OutputType>
<RootPath>
</RootPath>

Pearman

Awesome! I had the same problem and your question and answer helped me a lot. – Frontpage

This isn't fixing the problem, this is accommodating it. If your project is trying to use the latest and greatest you shouldn't dumb it down. – Ramer

I think it's a byproduct of every developer not having exactly the same thing installed. Having a tightly controlled toolchain for everyone is probably the "fix". – Pearman

Downvoted because updating the SQL Server Data Tools should be the accepted answer/solution. – Abyssal

In my corporate environment, I am not allowed to install a higher version so this was the only solution that actually worked for me. – Albumin

My project is not 'trying to use the latest and greatest', our strategy is more 'string this stack along for as long as possible, ideally my retirement', so this is good for me. – Bohon

Answer 3

Had the same problem and tried the above solutions, though even creating a new project from scratch was getting the same error message. I was also getting "File exists" for some reason.

I found the following in the event viewer:

Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
   at System.IO.__Error.WinIOError(Int32, System.String)
   at System.IO.Path.InternalGetTempFileName(Boolean)

Cleared my temp directory and now the database projects are once again behaving. This is probably not a real common solution to this problem, but wanted to get the info out there in case it can help anyone else!

Forward

I tried the repair (both the SQL Server Data Tools and Visual Studio), neither worked. Finally deleted %TEMP% folder contents as suggested here and opened quickly and first time! Thanks @Brian – Medication

after doing all of the above deleting the %TEMP% contents worked for me. – Hanni

This should be the selected answer. I've wasted more than 3 hours. Thanks for letting us know about the TEMP folder – Excruciate

Answer 4

You can try these steps:

1. Try adding another database project in your solution.
2. Enter in the edit the DBProj File
3. Copy the DSP and use that one.

I was trying to move the proj from vs2013 to vs2012 and it worked for me. The provider was:

<DSP>Microsoft.Data.Tools.Schema.Sql.Sql110DatabaseSchemaProvider</DSP>

You can try the one above if you have VS2012.

Patmos