Hi, I have 2008 r2 instance of SSIS running on a server. I have created a simple package in BIDS and have deployed it to the msdb (no errors given). The package runs fine in BIDs On the server I have done the following: Added the instance service account to the Distributed COM Users Group In Component Services I went to MsDtsServer100 > Properties > Security tab In launch and Activation Permissions > Edit - I added the Service account and gave full permissions In Access Permissions > Edit - I added the Service account and gave full permissions Restarted SSIS Now when I connect via SSMS to Integration Services and try to expand Stored Packages > MSDB I get the following error: Can Anyone tell me If Im missing something? Thanks, Zoe The SQL Server instance specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in SQL Server 2008 R2 Books Online. Login timeout expired A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr) ------------------------------ Login timeout expired A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Server Native Client 10.0)

What caused the need to tweak the DCOM security? The account to run the SSIS service typically is configured at the install time, also the fact you were able to deploy the package indicates no issues with the service. The service itself, by the way, is not necessary to run the packages, the DCOM permissions are allowing to connect to it using SSMS. For example, SSIS 2008 allows remote connections to admins out of the box (not the case with SSIS 2012). If you connect with an underprivileged account then the DCOM security needs to be tweaked, and I think you go the message about inability to connect that let you to a KB article about how to tweak the DCOM to allow remote connections.Arthur My Blog

yeah thats right - that why I tweaked the DCOM permissions. But I can connect to the Instance, its just when I try an expand the Stored Packages and then the MSDB folder I get an error Any idea how to remedy that?

Hello Zoe, To be able to browse the packages the account needs to be granted at least the db_ssisoperator fixed role.Arthur My Blog

Hello Zoe, To be able to browse the packages the account needs to be granted at least the db_ssisoperator fixed role.Arthur My Blog

Hi Zoe.Ohara, A user must be a member of the db_ssisadmin, db_ssisltduser, or db_ssisoperator role to have read access to the package. For more information about it, please refer to the following article: Integration Services Roles (Legacy SSIS Service): http://msdn.microsoft.com/en-us/library/ms141053.aspx Thanks, Eileen

Hi Zoe.Ohara, A user must be a member of the db_ssisadmin, db_ssisltduser, or db_ssisoperator role to have read access to the package. For more information about it, please refer to the following article: Integration Services Roles (Legacy SSIS Service): http://msdn.microsoft.com/en-us/library/ms141053.aspx Thanks, Eileen

Check if the SSIS service is running, this can be the issueArthur My Blog

Hi there, Sorry to open this up again, but I still cant connect. Ive added my account all the roles mentioned above, but I still get the same error. The instance is on a cluster - would that make a difference? Thanks, Zoe Are you using the clustername when attempting to connect to integration services or the actual servername? Integration services is not cluster aware, you should be using the servername to connect.Chuck

Im using the servername - Like I mentioned before I can connect to it ok - its when I try and expand the msdb folder I get the error. Yes the service is running.. cheers, Zoe

This is probably a network latency, can you then go the server itself (e.g. via a terminal Session) and connect?Arthur My Blog

OK - then look at this article here: http://msdn.microsoft.com/en-us/library/ms137789.aspx Specifically the part about modifying the config file. I suspect that in the config file what you need to do is to point to the clustername in this section: <ServerName>ServerName\InstanceName</ServerName> By default the SSIS service would be looking for the MSDB on the individual servername rather than the clustername that controls the msdb Chuck

Thanks! Cluster name is 487634-ntclus servername is 379353-serv instancename is WSA1 - does that mean it should be: <ServerName>487634-ntclus</ServerName> or <ServerName>487634-ntclus\379353-serv</ServerName> or <ServerName>487634-ntclus\WSA1</ServerName> PS - I am running it on the server itself Zoe x

Should be: <ServerName>487634-ntclus\WSA1</ServerName> The same connection string you would use to connect any client application to a database on the clustered instance Chuck

Sorry - still not working :( I tried restarting the SSIS service after I changed it also, but no joy.. Really appreciate your help by the way! Zoe

See if anything else here helps you: http://msdn.microsoft.com/en-us/library/hh231005 I know that you are not trying to set it up as a cluster resource, but some of the same tricks apply when you are running non clustered on a clustered sql server.Chuck

Hey - got it to work! Once I had given the cluster an alias name, specifiying the clustername as you said above worked! Thank you! x

Hi there, Sorry to open this up again, but I still cant connect. Ive added my account all the roles mentioned above, but I still get the same error. The instance is on a cluster - would that make a difference? Thanks, Zoe