search

BIDeveloperExtensions / bideveloperextensions

A Visual Studio extension that enhances development functionality in Business Intelligence Development Studio (BIDS) and SQL Server Data Tools (SSDT).
https://bideveloperextensions.github.io
Other
87 stars 24 forks source link

Unable to find the directories containing Tasks and Data Flow Task components. #31

Open mabramsBlythedale opened 6 years ago

mabramsBlythedale commented 6 years ago

Hi I have visual studio 2017 with an instance that has SSDT installed. I am using SQL Server 2014. I installed BI Developer Extensions, many of which work perfectly and are great. However, when I try to run the Design Warning Scanner (the feature we are most interested in), I get the error message "Unable to find the directories containing Tasks and Data Flow Task components. Check the integrity of your installation." There are additional error message notifications from .net below, but it's in a messagebox so I can't copy them from the message. See the image below. We tried looking this error up in Google, and after a couple of hours of failed attempts to find a solution, we're hoping you can help us resolve this issue. We are very eager to use the Design Warning Scanner! Thank you so much for this great utility!!

image

furmangg commented 6 years ago

Are you in project deployment model (deploy to SSISDB) or package deployment model?

When you look at project properties what is the TargetServerVersion you are deploying to?

mabramsBlythedale commented 6 years ago

Thanks for getting back to me so quickly! We have not gotten far enough with our project planning to make a definitive decision on the deployment model, but so far they have been deploying packages as files to their server, so my guess is that they are intent on using package deployment.

As for the TargetServerVersion, it is pointing to SQL Server 2017. I tried updating the value to SQL 2014 but it gave me a warning saying:

You are about to change the TargetServerVersion property to SQL Server 2014 of this project. If your project contains extensions that are not supported nor installed in SQL Server 2014, your packages may not be run properly.

It is highly recommended to:

  1. install all the needed extensions for SQL Server 2014 and
  2. back up your project before you proceed with this change

VS doesn't provide any further information on that, and when I go to Extensions and Updates, I do not see anything that corresponds to "SQL Server 2014" specifically. Also, on my local machine SQL 2014 is currently installed and functions normally. I tried looking for "install all the needed extensions for SQL Server 2014" in google and did find this...

https://blogs.msdn.microsoft.com/ssdt/2014/03/25/sql-server-data-tools-for-sql-server-2014-is-available/

... though I'm not sure if this is obsolete or the correct installation to use. Can you advise us on this as well? Thank you!

furmangg commented 6 years ago

Do you have custom SSIS components or tasks installed and used in your packages? If so which ones?

mabramsBlythedale commented 6 years ago

I'm pretty sure the answer to that is no, but I didn't create the package, so I'm only 99% sure. As far as I can tell it's using the standard SSIS components and tasks.

The puzzler for me is that when I try to find "SQL Server Data Tools 2014" I do locate this page: https://docs.microsoft.com/en-us/sql/ssdt/previous-releases-of-sql-server-data-tools-ssdt-and-ssdt-bi

... but it appears that 2014 is actually skipped over, which makes the message from Visual Studio confusing.

mabramsBlythedale commented 6 years ago

Update... after further research we decided to go with Project Deployment. I didn't attempt to do an install of the SSDT 2014, but was able to change the TargetServerVersion to 2014 after ignoring the warning. I was able to deploy the package to our development SQL Server 2014 into SSISDB. No problems surfaced.

So that's the current state. We still get the same error when attempting to use the Design Warning Scanner. Thanks for any help you can offer! We're looking forward to using that feature!

mabramsBlythedale commented 6 years ago

Still hoping we can get some guidance on this. It is still not working for us. Any advice would e greatly appreciated. Thanks!

furmangg commented 6 years ago

It's likely a BI Developer Extensions bug for this specific situation. It's on the list of bugs to look into and fix and we will update the thread as we have time. We all have day jobs so please be patient as there are many other items requiring our attention.

If it's urgent to you then feel free to download the source code and debug yourself further and create a pull request with any code changes you deem necessary.

mabramsBlythedale commented 6 years ago

Ok. I see. Not a problem. Thanks for the utility even if it does have a bug or two. It's great. Looking forward to whenever you can get to this item. My hope is that we can use it to identify items that have been created in the packages that are not being used, and/or are creating conflicts within the packages. Thanks again. Great job!

furmangg commented 5 years ago

Is this still an issue with the latest BI Developer Extensions 2.3.0 release and with the latest SSDT 15.9.0 install (SSIS extension 2.1 or 2.2 in the Tools... Extensions and Updates dialog)?

erenirmak commented 1 year ago

I have SQL Server 2022. It is my local database. I am using SSMS 18.12.1. I want to create new job, but when I try to add "new step", I encounter the same error:

"Unable to find the directories containing Tasks and Data Flow Task components. Check the integrity of your installation."

I uninstalled SSMS and reinstalled it, but the error still persists.

Is it version mismatch or something ?

furmangg commented 1 year ago

I have SQL Server 2022. It is my local database. I am using SSMS 18.12.1. I want to create new job, but when I try to add "new step", I encounter the same error:

"Unable to find the directories containing Tasks and Data Flow Task components. Check the integrity of your installation."

I uninstalled SSMS and reinstalled it, but the error still persists.

Is it version mismatch or something ?

@erenirmak i don’t think this has anything to do with BI Developer Extensions right?

erenirmak commented 1 year ago

I don't know what causes it, but I couldn't find this error on anywhere except here. Is there a common component used in both SSMS or SQL Server 2022/SQL Agent and BI Developer Extension?