Fixing “The ‘VSTS for Database Professionals Sql Server Data-tier Application’ package did not load correctly”

Visual Studio 2010 and SQL Server Express have an uneasy alliance, at best.  When you install Visual Studio 2010 it installs SQL Server Express 2008 for you, but only the database engine, not SQL Server Management Studio.  If you mess with SQL Server Express in order to install the management tools, or upgrade to 2008 R2, or install the Advanced Services version, things break and you can no longer reliably use the Visual Studio database projects.

In particular, if you remove SQL Server Express 2008 and install SQL Server Express 2008 R2, you’ll probably run into an issue where if you try to open a schema object in a Visual Studio database project you’ll get an error that says:

The ‘VSTS for Database Professionals Sql Server Data-tier Application’ package did not load correctly.

The fix for this problem can be found here.  Here’s the short version:

  1. Locate your Visual Studio 2010 installation media.
  2. In the \WCU\DAC folder, you’ll find three MSIs: DACFramework_enu.msi, DACProjectSystemSetup_enu.msi, and TSqlLanguageService_enu.msi.  Run and install each of them.
  3. Reapply Visual Studio 2010 SP1.

You should be back to a working state.

30 thoughts on “Fixing “The ‘VSTS for Database Professionals Sql Server Data-tier Application’ package did not load correctly””

  1. also visual studio command prompt – rightclick run as administrator
    devenv.exe /resetskippkgs
    should solve the messages

  2. oops that didn’t worked
    what worked was

    installing (don’t uninstall them when before you install SQLSERVER 2012)

    Microsoft SQL Server 2008 R2 Data-Tier Application Framework with this command:

    Microsoft SQL Server 2008 R2 Data-Tier Application Project:

    Microsoft SQL Server 2008 R2 Transact-SQL Language Service:

    if you make a layout as described below it contains the msi files mentioned above

    the above solved just f# message

    also after repairing Visual Studio 2010 had to Reapply Visual Studio 2010 SP1.
    VS10sp1-KB983509.exe /createlayout “%TEMP%\VS2010SP1”
    then run setup

    if i just ran without making a layout I had many msi files ware missing

    all this happend because i have removed sql server 2008 and tried to install sql server 2012
    but it failed it said need visual studio setup
    then i repaired the visual studio so it became missing sp1
    then i with a repaired visual studio i could install sql server 2012
    so then i got errors in visual studio and so i got these packages installed and seems like it worked out finally

  3. Hey Eric – Just a note to say thanks.

    This not only fixed the packages not loading exceptions, it also fixed another problem, in which the .NET Runtime Optimization Engine was running nonstop and eating up all my CPU time.

  4. @Swaminathan, I think the menu items for displaying the Errors list and Task list windows is located on the View top-level menu by default, so I don’t think there’s anything wrong there. At least it’s that way for me on VS 2012. You can move stuff around with Tools | Customize | Command tab.

    Or maybe I didn’t understand your question?

    1. Oops.. that was a big typo there.. I meant to say they are NOT getting displayed under View Menu..However, I just tried doing a devenv /resetsettings today and I have got them back now.. 🙂

  5. It doesn’t work for me, because DACProjectSystemSetup_enu.msi doesn’t install, it keeps asking for source, even though the file is there… the other two install with no problems… I don’t get it. What can I do to install DACProjectSystemSetup_enu.msi?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: