Deploy SSIS Package Error: "The selected folder does not contain package..."

  • Hi All

    It seems TFS is not behaving itself!

    When I deploy a package I am getting the error above.

    I've tried rebuilding the solution etc. and I can open and edit the package but can't deploy to the server.

    Does anyone have any idea on how to fix this?

    Thanks

    Mattie

  • What makes you think that this is a TFS issue?

    If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.
    See https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help/ for details of how to post T-SQL code-related questions.

  • That is a good question.

    I guess the only response to that is the package runs fine on my PC and we do have two new people checking packages in and some changes have been rolled back etc. so I assume it's a TFS issue.

    If not let me know if you have any ideas 🙂

  • I agree with Phil that it probably isn't a TFS issue.

    Step 1 with debugging that for me would be to grab a different developer and have them try what I was doing.  If it works for them, it is a problem with my setup.  If it doesn't work for them, then something is configured funny.

    Alternately, any good version control system will have the ability to check out an older version of the code.  Grab an older version that is known-good and see if you can deploy.  If you can, go up a version and repeat until you get to the version that is bad.  Then compare the differences between those 2 versions.

    My guess is there is a configuration change that happened at some point or possibly you don't have permissions to the deployment folder location hence the error.

    That being said, I never use the deploy option from SSIS.  I take my DTSX and push it into the SSIS catalog manually.  It is very rare that I am changing more than 1 or 2 DTSX's at a time, so using deploy feels like overkill.

  • One problem I have seen before with SSIS and VCSs is that people sometimes make changes which affect the project file (eg, add or remove parameters, add or remove packages) but neglect/forget to check in the project file. Instead, they check in only the packages which have been changed.

    When this happens, your project file gets out of step with the actual files in the project folder.

    • This reply was modified 1 month, 1 week ago by  Phil Parkin. Reason: Added clarification

    If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.
    See https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help/ for details of how to post T-SQL code-related questions.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply