I'm on a new laptop, working in Visual Studio 2015 on a SQL Server Integration Services package.
In previous versions of Visual Studio there are several options in the Enumerator configuration section, like this...
In VS 2015, that section is blank and I cannot populate it with a data set.
I have updated SSDT and rebooted.
The problem was with the Target Server Version in the Project Properties. The new installation of Visual Studio 2015 had it defaulting to vNext. Switching it to SQL Server 2012 caused the configuration to show up.
I had the same issue and I resolved the problem by selecting Foreach File Enumerator option under collection. By default under Collections >> Foreach Loop Editor >>> Enumerator was set to foreach Item Enumerator as shown below
Default Config for Foreach Loop Container
Instead of "Foreach Item Container" aka the default value, I clicked on it and selected Foreach File Enumerator option and that resolved my problem. Please see snapshot below
Corrected configuration for Foreach Loop Editor
You have a problem is your visual studio. (below a screenshot of ADo enumerator from my computer , using visual studio 2015)
Try running visual studio in safe mode so if this was caused by an add-on it will be fixed. just run this command
devenv.exe /safemode
If not working Try repairing your SQL Server Data Tools installation or Download the Latest release
Related
i have an old SSIS integration project that i can only open via import wizard in Visual Studio 2019. I have tried in VS10,12,13,15,17 and i wont open.
My problem is when i deploy the project to the SQL server the server comes up with the error: the version number in the package is not valid. the version number cannot be greater than current. Can anyone help.
According to the error message, you have SSIS 2012, and try to start the package that is created for higher version of SSIS.
To fix it, open your SSIS project in Visual Studio, select Project and go to menu Project - Properties. Then on Project Properties window, select Configuration Properties - General and
select SQL Server 2012 in the TargetServerVersion dropdown.
Hit Ok, save and build/deploy project again.
I am running SQL Server 2014 on my machine. I have installed SSDT for Visual Studio 2017, which I also have. Now I am not able to find the SSIS Toolbox in my Visual Studio. Do I need to re-install the SSDT all over again? Please let me know. Thanks in advance.
Note on 2022-01-26: I updated my answer with more information about other cases since this question is highly viewed.
I. In case you are sure that you have installed SQL Server Data Tools
You can show the SSIS toolbox in 3 ways:
(1) Visual Studio Menu strip
Based on this Microsoft article:
If you can't see the toolbox, go to VIEW -> Other Windows -> SSIS Toolbox.
(2) From Context Menu strip
Or Right-click inside the Control Flow of any parent/child package and select 'SSIS toolbox', then the SSIS toolbox will be displayed after that click. Read more
(3) Near SSIS tab pages
You can find a small button near the SSIS tab pages, as shown in the following image:
II. If none of the above methods worked, ensure you have installed SSDT correctly.
In case you are using Visual Studio 2019 or newer versions, check for the SQL Server Integration Services extension in the Visual Studio Market Place:
SQL Server Integration Services Projects - Visual Studio Market Place
In case you are using the previous version of Visual Studio, you should download the SQL Server Data Tools from the following links:
Download SQL Server Data Tools (SSDT) for Visual Studio
Previous releases of SQL Server Data Tools (SSDT and SSDT-BI)
III. Integration Services extension for Visual Studio is installed correctly, and the SSIS toolbox is empty
In case the SSIS toolbox is not showing the SSIS tasks and components, from the Visual Studio menu strip, Go To:
Tools" >> Options >> Environment >> On the General Tab >> DISABLE "Optimize rendering for screens with different pixel densities"
Reference: Why is my SSIS toolbox empty in Visual Studio 2019 community?
IV. Last thing to try
If none of the above suggestions worked, try running Visual Studio in safe mode since some third-party extension causes malfunction sometimes. You can run in safe mode using the following command:
devenv.exe /safemode
You just need to click the upper right button of your ssis design board
I have like 1 hour of SSIS experience so I do not know why this is failing.
I am following this guide.
However when I get to the Foreach loop editor screen section and pick "Foreach ADO enumerator" I cannot see the ADO Object source variable section.
The screen should look like this
Any ideas?
I am using Visual Studio 2015 and a release candidate of SSDT so this may be an issue.
I have followed all steps correctly and have seen no errors in previous steps
I had the same issue; here's how I solved it:
If your package was developed in SQL 2014:
Right click Solution in Solution Explorer of Data Tools ->
Properties -> Configuration Properties -> General -> Change Target Version.
The SSIS ADO Enumerator was blank for me too.
For the latest version of SSDT [Release 17.0] [Build 14.0] the Project Level default TargetServerVerion is SQL Server vNext. That doesn't work.
Changing this to any other value was the fix for me.
Solution Explorer Window -> Right-click Project -> Properties -> Configuration Properties -> General -> TargetServerVersion = SQL Server 2016
I searched for this issue and i found two simple suggestions:
Try running visual studio in Safe mode using this command (this issue can be caused by a third-party add-on)
devenv.exe /safemode
Try repairing your SQL Server Data Tools installation or Download the Latest release
I accidentally oped 2008 SSIS solution file in a new 2012 version of Visual Studio. Cannot open the any 2008 SSIS package anymore. I've tried creating a new solution but is still gives the error shown below.
Please advise.
The point is that I do not need to open it in 2012 at all. 2008 packages are not compatible with 2012. I'm opening it through 2008 Integration services. But getting this error.
The solution to the issue is to open Integration Services 2008 solution file previously opened in later version Visual Studio version is open it with Visual Studio Version Selector
Looking at the error, it doesn't seem to be related to your solutions compatibility levels, but rather your installation of visual studio itself. Make sure it is fully updated (and in particular has this update: https://www.microsoft.com/en-nz/download/details.aspx?id=36020), and if that fails I'd try uninstall/reinstall visual studio/SQL server data tools.
I was trying to use Team Foundation Server 2012 with Sql Server Management Studio 2012. I installed the Microsoft Visual Studio Team Foundation Server 2013 & 2015 MSSCCI Provider 32-bit and choose it as Current source control plug-in under tools -> Source Control -> Plug-in Selection of SSMS.
The problem is when I create/open a solution, for the very first time, and try to add a solution to source control from file -> source control -> Add Solution to Source Control a dialog box appears asking to connect to tfs once connected and location of server is specified on server and ok button is pressed it shows a warning that my workspace is a local workspace and local workspaces do not work properly in MSSCCI. It asks if I want to change it to server workspace once I click on Yes
I get the following error
Unexpected error encountered. It is recommended that you restart the application as soon as possible.
Error: No such interface supported
File: Vsee\internal\inc\vscomptr.inl
Line number: 259
Trying again yield this error message as soon as I choose Add Solution to Source Control.
I have tried some of the hotfixes provided by Microsoft from the link :
https://support.microsoft.com/en-us/kb/2727824 but they do not install on my machine saying that my SSMS version is newer.
How can I get this problem resolved ?
As described in this article - Team Foundation Server 2012 brought up a change in the workspace options bringing a new type of workspace – a local workspace. A local workspace is an improvement in offline work and it allows performing a number of source control operations without the connection to Team Foundation Server.
For more information about server workspaces vs. local workspaces refer to the following article: http://blogs.msdn.com/b/phkelley/archive/2013/05/29/server-workspaces-vs-local-workspaces.aspx
The article states that Microsoft continues to fully support the older kind of workspaces (from VS/TFS 2005 - 2010), but they now call these “server” workspaces. In the VS/TFS 2005 - 2010 documentation there is no mention of these workspaces ever being called “server workspaces” – because before the existence of local workspaces, there was no need to have a special name for them - they were just “workspaces.”
Hope I helped.
I am using TFS Online (Visual Studio Online), SQL Server Management Studio 2012, Windows Server 2008 R2, and installed Microsoft Visual Studio Team Foundation Server 2013&2015 MSSCCI Provider 32 bit. I can add new solution in SSMS and add to source control with no issue. You might want to
1. go back and create the server workspace FIRST in Team Explorer 2012.
2. Then re-create the solution (Make sure you check the Add to Source Control),
3. then select the TFS with the correct server workspace.
4. from Solution Explorer, right click on the project and add existing items.
Hope it helps