none
'Origin.xml' is missing from the dacpac package - After upgrade SSDT to December 2012

    Question

  • I have a SSDT project in VS 2012 U1. I also have a dacpac retrieved from the client installation SQL Server 2008 R2 Express (10.50.1600.1).

    With this combination I was able to successfully compare the project to the client dacpac, I could perform this comparison in Visual Studio 2012, and using sqlpackage.exe in order to generate an update script.

    I then upgraded SSDT to December 2012, and I'm now unable to schema compare the project to the retrieved dacpac. I receive this error from within Visual Studio:

    Microsoft.Data.Tools.Schema.Utilities.Sql.Common.Exceptions.DacPackageException: 'Origin.xml' is missing from the dacpac package.
    
    Microsoft.Data.Tools.Schema.Sql.Build.SqlPackageException: 'Origin.xml' is missing from the dacpac package.

    If I compare at the command line using sqlpackage.exe then I receive no error, and my update script is produced.

    I can compare project snapshot dacpacs to the project.

    I have cleaned and rebuilt the project to generate a new project dacpac.

    Tuesday, March 05, 2013 4:32 AM

Answers

All replies

  • What tool do you use to create the client retrieved DACPAC?


    -GertD @ www.sqlproj.com

    Tuesday, March 05, 2013 6:20 PM
    Moderator
  • "Extract Data-tier application" from SSMS.
    Tuesday, March 05, 2013 10:09 PM
  • SSMS 2008 R2?

    -GertD @ www.sqlproj.com

    Wednesday, March 06, 2013 6:40 AM
    Moderator
  • I get this with SSMS 2008 R2 at the client:

    Microsoft SQL Server Management Studio      10.50.1600.1

    and with local tests with SSMS 2008 R2:

    Microsoft SQL Server Management Studio      10.50.4000.0

    Wednesday, March 06, 2013 9:43 PM
  • SSDT and DACFX v3.0 supports only importing DAC v1.1 and DAC v2.0 formats

    This means you need to have SQL Server 2008 R2 SP1 install, this include SSMS, so make sure you have SSMS updated.

    Hope that helps,


    -GertD @ www.sqlproj.com

    Wednesday, March 06, 2013 11:04 PM
    Moderator
  • Given that the only thing I did was update from SSDT November 2012 (as came with VS 2012 I believe), to SSDT December 2012, then I wouldn't expect anything to break. And I can't see any release notes that state that this version will break backwards compatibility. With the SSDT from November I could make this comparison in Visual Studio.

    I have also tested on my local machine on which I have VS 2012 U1, and SSDT December 2012. On my machine I also have SQL 2008 R2 SP2 (10.50.4000), and a version of SSMS that has version 10.50.4000.

    If I extract a data tier application via SSMS then I still get the 'origin.xml' error when I attempt compare the dacpac with a project. If I use sqlpackage.exe for the comparison then I don't get any errors, but I don't get the visual comparison that VS provides...

    This test makes me doubt that patching the client's SQL install will fix the problem.

    Wednesday, March 06, 2013 11:33 PM
  • Adam,

    Just to make sure I am totally clear on your scenario, are you doing the following:

    1. Schema Compare in SSDT VS2012 comparing:
    • DACPAC created using SSMS of SQL 2008R2 SP2 (10.50.4000)?
    • Database Project created with SSDT VS2012 December

    Thanks for your clarification,

    Adam


    Adam Mahood - Program Manager Windows Azure Import-Export Service / Data-Tier Application Framework (DACFx)/ SQL Server Data Tools

    Thursday, March 07, 2013 3:06 AM
    Owner
  • Just to make sure I am totally clear on your scenario, are you doing the following:

    1. Schema Compare in SSDT VS2012 comparing:
    • DACPAC created using SSMS of SQL 2008R2 SP2 (10.50.4000)?
    • Database Project created with SSDT VS2012 December

    Yes this is exactly what I'm doing.
    Thursday, March 07, 2013 4:47 AM
  • Thanks for reporting this.  The problem will be fixed in the next version of SSDT.
    Friday, March 08, 2013 8:58 PM
    Owner
  • Hi,

    I am still seeing this same problem with the following software versions:

    *) DACPAC created using SSMS of SQL 2008R2 SP2 (10.50.4000.0)
    *) SSDT create empty Database project using VS2012 SSDT 11.1.30822.0, then I import the above mentioned dacpac into the database project
    *) 2nd DACPAC created using SSMS of SQL 2008R2 SP2 (10.50.4000.0), but this is based on a newer database schema version of my product (so there will be schema differences)
    *) Schema Compare (with SSDT 11.1.30822.0) of Database project and 2nd DACPAC

    This results in:
    Microsoft.Data.Tools.Schema.Sql.Build.SqlPackageException: 'Origin.xml' is missing from the dacpac package.


    Can you confirm in which version of SSDT this problem is expected to be fixed? (or if this bug is indeed not fixed yet?)

    Thanks in advance,

    Jeroen Janssen

    Thursday, September 12, 2013 10:05 AM
  • Only SQL Server Manager Studio 2012 works, all DAC implementations before v3.0 are incompatible.


    -GertD @ www.sqlproj.com

    Friday, September 13, 2013 4:51 AM
    Moderator
  • Thanks for reporting this.  The problem will be fixed in the next version of SSDT.

    So, was this actually fixed in an upgrade of SSDT, by making sure that the SSDT could handle older dacpac files generated by SSMS 2008 R2 that did not include an Origin.xml file?

    Or was it fixed by the less convenient method of forcing an upgrade of SSMS to 2012?

    As someone who is running Windows 2008 Datacenter, it's a hard sell to disrupt operations to get an operating system upgraded to SP2, just so I can upgrade SSMS to extract a dacpac that works with the development tool.  Additionally, since the last time we tried to upgrade the OS to a SP, the apps broke horribly, and management aren't willing to risk it again.

    Thursday, June 05, 2014 10:13 PM