SSIS – Resolving “Failed to Deploy the Project” Messages

Have you seen this screen when trying to deploy?

Needless to say, this indicates the SSIS package didn’t load to the server. This is especially frustrating as this particular package worked fine in Visual Studio. Believe it or not this screen actually contains information which can be used to resolve the error.

Finding a Useful Error Message

How do you go about determining what to do? Click on the word Failed. This will bring up some useful information, although it may not appear that way at first. Here’s the error message I received


The message Failed to deploy project isn’t very useful, but the rest of the message is. The operation_messages view lives in SSISDB, and the operation identifier number is how to determine what the error is. Run this query, using the number provided in the error message, which in this case is 173

Select * from catalog.operation_messages where operation_id = 173

Here are the results from that query.

operation_message_id operation_id message_time message_type message_source_type message extended_info_id
50719 173 2016-02-29 15:02:08.2478928 -07:00 120 20 Failed to deploy the project. Fix the problems and try again later.:SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM. NULL


Now this message is quite useful as it provides information that I can use to fix the issue. This SSIS Project contains a date parameter BackDate, which I had not set. Here’s the parameter.


I set this parameter to a date between 1/1/1753 and 12/31/9999 and deployed the project again. This time, no error.

I hope that you have found this post helpful, especially if you haven’t deployed a package to SSIS in SQL Server 2012 or later.

Yours Always

Ginger Grant

Data aficionado et SQL Raconteur


7 comments on “SSIS – Resolving “Failed to Deploy the Project” Messages

  1. Pingback: Failed To Deploy Project In SSIS – Curated SQL

    1. Ginger Grant

      Thanks for the reading my blog! To be honest, this error surprised me too, and I thought this would be a good topic for #EntryLevel blog for PASS.


  2. thesmilingdba

    Thanks for the post, never thought that would be a problem with deploying – invalid date parameter.

    I had a problem deploying, but it was a permission issue.


  3. Navish Singh


    The information in this blog has completely changed the way I view error messages now. In the past, I was so quick to dismiss the error and continue debugging, now I will pay closer attention to “catalog.operation_messsages”, thank you.

    Kind Regards
    Navish Singh

  4. Donald Kidd

    For details: We just upgraded our DEV servers from 2012 to 2016. There are four projects all in the same folder on the catalog. The other three deploy fine. Only the one project that contains a DQS cleansing component fails to deploy. I am using Visual Studio 2012 to deploy the projects.

    I get this error but the message after looking at the catalog.operation_messages reads: Failed to deploy the project. Fix the problems and try again later.:The method or operation is not implemented.

    1. Ginger Grant

      Donald —
      Based on the message you were getting, I would check to make sure that you are reference the same version of DQS on your local machine as what exists on SQL Server 2016. You might also want to convert to Visual Studio 2015, as it was designed to work with SQL Server 2016, which Visual Studio 2012 was not.

      Good Luck


Leave a Reply