April 10, 2018 at 2:24 pm
I am getting an error when trying to Integration Services using ssms 17.6 (The specified service does not exist as an installed service). New install of SQL2016 and verified service is running Integration Services 13.0). Restarted and upgraded ssms to 17.6 to no avail. I am thinking I may need to go backwards. Any idea of what version of ssms and how to obtain an older version or any other fixes?
April 10, 2018 at 3:57 pm
jamesforest - Tuesday, April 10, 2018 2:23 PMI am getting an error when trying to Integration Services using ssms 17.6 (The specified service does not exist as an installed service). New install of SQL2016 and verified service is running Integration Services 13.0). Restarted and upgraded ssms to 17.6 to no avail. I am thinking I may need to go backwards. Any idea of what version of ssms and how to obtain an older version or any other fixes?
You can try this link for some previous versions of SSMS:
Previous SSMS releases
They all list what was fixed with each version - and they all point to the defunct connect site items so you can't tell what is fixed with what versions anymore. The additional downloads link for other versions from the download center is pretty worthless. But there is one towards the bottom of the page.
Sue
April 10, 2018 at 6:17 pm
Try running SSMS as Administrator then connect to integration services.
April 11, 2018 at 5:58 am
Sue,
Thanks for the link. Uninstalled\reinstalled 16.5 and was able top connect.
Joe, I have full admin rights but tried 'run as admin' to no avail before going back to 16.5
A tad disappointed in MS. They should be able to do better than this. I now have 6 servers with 17.x installed and determining a game plan. Would like a SSMS fix that is backward compatible.
July 9, 2018 at 2:17 am
Hi,
I can relate. I have a SQL 2016 server running SSIS and can only connect to it using SSMS 16. If I try using SSMS 17.X Is get this error:
"TITLE: Connect to Server
Cannot connect to csdc-d01sql040v.
ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
Connecting to the Integration Services service on the computer "*****" failed with the following error: "Class not registered".
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.
For help, click: http://go.microsoft.com/fwlink/?LinkId=506689
Both url's aren't helpful, neither is the error - I'm not trying to connect to a 2005 instance. Microsoft needs to catch this error correctly and provide *helpful* errors and urls.
Michael Gilchrist
Database Specialist
There are 10 types of people in the world, those who understand binary and those that don't. 😀
July 9, 2018 at 2:18 pm
I am totally disappointed with the mess. I have to keep a few versions of SSMS. The monthly new versions of SSMS has resulted in needing more versions rather than one. And then I have to remember what bugs with what versions. One solid, well tested release that actually is backwards compatible and works with other components (like SSIS) would be better than what's been happening.
Sue
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply