After installing the latest version of SSMS (17.2), I was not able to connect to SQL Server Integration Services SSIS on my local machine.
Here is the text of the error message.
Connecting to the Integration Services service on the computer “LOCALHOST” failed with the following error: “The specified service does not exist as an installed service.”.
This error can occur when you try to connect to a SQL Server 2005 Integration Services service from the current version of the SQL Server tools. Instead, add folders to the service configuration file to let the local Integration Services service manage packages on the SQL Server 2005 instance.
This error can occur when you try to connect to a SQL Server 2005 Integration Services service from the current version of the SQL Server tools. Instead, add folders to the service configuration file to let the local Integration Services service manage packages on the SQL Server 2005 instance.
I checked services.msc to make sure it was running.
Above image confirmed that error message “The specified service does not exist as an installed service” is totally misleading.
WORKAROUND/SOLUTION
After trying various steps given on various sites, I was looking at the documentation and found https://docs.microsoft.com/en-us/sql/integration-services/service/integration-services-service-ssis-service#manage-the-service This says:
To connect directly to an instance of the legacy Integration Services, Service, you have to use the version of SQL Server Management Studio (SSMS) aligned with the version of SQL Server on which the Integration Services Service is running. For example, to connect to the legacy Integration Services, Service running on an instance of SQL Server 2016, you have to use the version of SSMS released for SQL Server 2016
Which means that, I need to download and install older version of SQL Server Management Studio. (16.5.3).
As of today, the download link is http://go.microsoft.com/fwlink/?LinkID=840946 which might change in the future so follow below steps.
- Go to https://docs.microsoft.com/en-us/sql/ssms/sql-server-management-studio-changelog-ssms
- Search for “SSMS 16.5.3” and you should reach to the below image.
- Click on the hyperlink to download
Hope this would help someone’s time as I wasted close to 30 min.
Reference: Pinal Dave (https://blog.sqlauthority.com)
53 Comments. Leave new
Very helpful, thank you!
I am glad that it helped you.
I spent almost 4 hours installing/uninstalling and reading SQL VIPs comments for the above issue about why I cant see Integration Services via SSMS and connect to that. Finally I find your hint! I appreciate for a complete help and links !
Yeah. It is one of an annoying behavior.
Thank you for the article. It works.
Great! Thanks.
You are, indeed, the man – this answered my problem. I had a predecessor problem with not having granted rights to SSIS 2014 – some time around there they started only giving administrator access to SSIS by default.
I’m not sure why all my other 2014 services (database, SSRS, SSAS) can be accessed with SSMS 17.3, but SSIS needs the older software – hope they fix this in the future.
I truly hope they fix it.
Thanks Pinal, installing 16.5.3 did fix the issue for me. Wonder when they would incorporate this fix in the latest version.
I truly wish that they fix it.
Thank you very much for having a solution to this vexing error. I had to uninstall SSMS 17.4 and to reinstall SSMS 16/2016 to get rid of this problem. As of version 17.4 update, this problem has not been fixed.
Agreed. Why can’t they have backward compatibility?
This is a complete and utter load of crap from Microsoft. Really, really pathetic that they have continued to ignore this PROBLEM (it’s not an ‘issue’) for so many versions.
Agreed.
thanks…. spot on for the fix
I am glad to see this comment.
Thanks for this – This post has saved me many hours of additional troubleshooting!
Thanks TrixyB
Thank you! This was driving me crazy. Yours was the only article that pinpointed the issue.
My pleasure.
Thank yo, very helpful.
Your blog help me several times to fix issues, thx you.
How can this not be a bug? It’s hugely annoying.
Anna, this worked for me, you are Awesome!!!, always looking for your blog URL in Google search, Thank u!
It worked for me , thanks a lot , saved lot of time :)
Worked for me too, you saved my day
Awesome, thaks a lot Sr, I´m a big fan. You, Brent, Paul Randal and so on save me a lot of times.
Thanks Pinal, i was struggled to resolved it by few hours. But it works for me after using SSMS 2016 for SQL SERVER 2016.
Thanx that was the Help !!!
Hi, Am using MSSMS 17.9.1 with SQL Server 2014 and am seeing same error message, can you help me with which version of MSSMS I must use to fix this? or is there any other option to fix this?
Thanks for this. I have been using SSMS 17 with SQL Server 2016 for a long time without the need to connect to Integration services. Similar story, had problems but was able to connect to it using SSMS 2016.