Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage
When trying to connect from SSMS v17.x to a SQL Server Integration Services 2016 instance or previous version, you get the error Connecting to the Integration Services service on the computer failed with the following error: "The specified service does not exist as an installed service".
If you have more services installed as SQL Server engine, SSAS or SSRS and confirming that all of those services are up and running:
You will be able to see them in SSMS v17.x when browsing for services but realize that SSIS services it is not being listed:
The solution is actually very simple but it is not so obvious. After many attempts to understand and solve this issue, a downgrade of the SSMS version eventually solved it. To connect to a SSIS 2016 instance you will need at least SSMS v16.5.3.
For some reason, SSMS v17.x (at the moment I am writing this article the last version is 17.2) has a limitation that does not let it be able to connect to any SSIS version prior to 2017. So if you need to use SSMS to work with SSIS the best you can do by now is to download and install SSMS v16.5.3.
Note: As stated above, this issue happens with SSMS v17.2 and previous minor releases of SSMS v17. It has been already reported to Microsoft so it is expected that in a future release this will be corrected. Meanwhile use an older version of SSMS when working with SSIS instances. You can track the SSMS releases bug fixes here to see when this specific bug will be fixed by Microsoft.
|Reading a wide CSV file (> 255 columns) using Access and SQL Server||859|
|Stellar SQL Database Toolkit is Best Solution for All SQL Database Issues||1,024|
|SQL Database Backup and Recovery - All you Need to Know||475|
|Top 5 Best SQL Recovery Software for Fixing Database Corruption||717|