Connection from SSMS to SSIS fails with "The specified service does not exist as an installed service."

Question

Connecting using Microsoft SQL Server Management Studio (SSMS) v16.5.3 to Microsoft SQL Server Integration Services (SSIS) v13 (these are the matching versions for this long term legacy horror, and SSMS is run as an administrator).

On one computer (RDP Server 2016) the connection from SSMS 16.5.3 to the SQL SSIS server works just fine. On another computer (Win10 Pro) the following unhelpful message is shown:

TITLE: Connect to Server

------------------------------

Cannot connect to SQL.

------------------------------

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 "XXX" 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.
For help, click: http://go.microsoft.com/fwlink/?LinkId=506689**

Both computers are using installations of SSMS v16.5.3 from the same installation file. Both computers SSMS is being executed using the same administrator account, which is a member of the Local Administrators group on both computers and the DCOM configuration shows the same local/remote launch and execute settings.

The SSIS service definitely exists as an installed service - the server is running the service and a different computer can connect just fine. A "no access" I'd expect if the authentication was not working, this error message is trying to tell me that the target service does not exist.

Answer 1

Hi @Nick Ryan ,

The Microsoft SQL Server Integration Services OS Service exists only for backward compatibility with the obsolete SSIS versions 2005 - 2008R2.

Starting from SSIS 2012 onwards there is no need in that OS Service.

Here is an excerpt from the official Microsoft documentation: integration-services-service-ssis-service

The topics in this section discuss the Integration Services service, a Windows service for managing Integration Services packages. This service is not required to create, save, and run Integration Services packages. SQL Server 2012 (11.x) supports the Integration Services service for backward compatibility with earlier releases of Integration Services.

Answer 2

Hi @Nick Ryan ,

In SQL 2016 you may create an integration services catalog to hold your packages and you could connect to that database engine.

Once the catalog is in place, you can deploy your projects, and they’ll show up in a folder under the catalog. From here, you can set up environments, map parameters, and run packages.

So in summary, connection to Integration Services when starting up SSMS is unnecessary for 2012+ since you can create to the Database Engine and execute SSIS packages from the catalogue without. It is just there for backwards compatibility.

ssis-catalog

"The specified service does not exist as an installed service."

As this error message said, I suppose that you have not installed the Integration Services component of SQL Server.

You may check like below too see if you have the feature in Win10 Pro.

If you want to install this, please refer install-integration-services.

Regards，

Zoe

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.