Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Adding Integration Services to clustered nodes


Adding Integration Services to clustered nodes

Author
Message
joffwilliams
joffwilliams
SSC-Enthusiastic
SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)

Group: General Forum Members
Points: 103 Visits: 221
I have installed Integration Services 2008 R2 on two clustered nodes, 'NODE1' and 'NODE2', part of an active/passive cluster named 'SQLCLUSTER'. Now SSIS is installed (and patched up to the same level as the DB engine). I can run BIDS on the nodes, build and execute packages.

My problem is that I cannot connect to SSIS in Management Studio using the cluster name 'SQLCLUSTER'. I receive the following error:

Connecting to the Integration Services service on the computer "SQLCLUSTER" failed with the following error: "The RPC server is unavailable."


I know RPC is running on the node currently owning the cluster, and I can connect just fine in SSMS if I use the node name instead.

I have updated the <ServerName> element in msdtssrvr.ini.xml to "SQLCLUSTER" as indicated in http://msdn.microsoft.com/en-us/library/ms137789.aspx.

If anyone has any clues I'd be grateful. Thank you!
SQLArcher
SQLArcher
SSC-Enthusiastic
SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)

Group: General Forum Members
Points: 150 Visits: 3166
Have you tried to restart to SSIS services on both nodes? Also remember, the modification needs to happen on both nodes in some cases that I've seen.
MysteryJimbo
MysteryJimbo
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1348 Visits: 15327
I don't install SSIS on clusters as its not recommended and isnt cluster aware. Have you read this article?

http://msdn.microsoft.com/en-us/library/ms345193.aspx
SQLArcher
SQLArcher
SSC-Enthusiastic
SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)

Group: General Forum Members
Points: 150 Visits: 3166
The article doesn't state that it is not recommended on a cluster, the article states that it is not recommended to configure SSIS as cluster resource.

To install SSIS on a cluster is perfectly fine as the SSIS engines will run independently of one another on each node.
joffwilliams
joffwilliams
SSC-Enthusiastic
SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)

Group: General Forum Members
Points: 103 Visits: 221
MysteryJimbo (10/28/2011)
I don't install SSIS on clusters as its not recommended and isnt cluster aware. Have you read this article?

http://msdn.microsoft.com/en-us/library/ms345193.aspx


Thanks for your help. SQLArcher is correct - Installing SSIS on a clustered node does not necessarily make it a clustered service. A clustered service fails over between nodes. What I have done is installed SSIS as a service on each node of the cluster, without failover. See the third paragraph of the MSDN article. It just means that SSIS is available on every node of the cluster, which is why it is preferable that it can be reached by cluster name, not just node name.

SQLArcher - thanks for your advice. I was working on just the active node's configuration. I'll try updating both nodes and restarting the service this afternoon and see what that does.
MysteryJimbo
MysteryJimbo
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1348 Visits: 15327
SQLArcher (10/28/2011)
The article doesn't state that it is not recommended on a cluster, the article states that it is not recommended to configure SSIS as cluster resource.

To install SSIS on a cluster is perfectly fine as the SSIS engines will run independently of one another on each node.


Not quite what I said/meant as I know this

MysteryJimbo (10/28/2011)
I don't install SSIS on clusters as its not recommended and isnt cluster aware. Have you read this article?

http://msdn.microsoft.com/en-us/library/ms345193.aspx


Clustering Integration Services is not recommended because the Integration Services service is not a clustered or cluster-aware service


Why have it on a cluster if you cannot cluster the service unless its licence cost implications? Its an extra memory hog which is most likely better off running on another server. You'll also experience fewer issues.
joffwilliams
joffwilliams
SSC-Enthusiastic
SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)

Group: General Forum Members
Points: 103 Visits: 221
Thank you for your input. Your point has been taken into consideration. You are indeed correct regarding licensing as a serious consideration, in addition to other factors.

My original question is regarding why I cannot connect to SSIS using the cluster name. I'd appreciate any feedback on that.
SQLArcher
SQLArcher
SSC-Enthusiastic
SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)

Group: General Forum Members
Points: 150 Visits: 3166
Have you changed the service account of the SSIS services on any of the nodes? This can have an effect, especially if you are using domain authentication instead of the default accounts.

You have also net yet commented if you did the modification on both of the nodes, and if you restarted both of the services...
joffwilliams
joffwilliams
SSC-Enthusiastic
SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)

Group: General Forum Members
Points: 103 Visits: 221
I'm in a position where I cannot make changes until later in the day. I'll let you know what I find when I try later.
joffwilliams
joffwilliams
SSC-Enthusiastic
SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)

Group: General Forum Members
Points: 103 Visits: 221
It turned out to be the result of Windows Server 2008 R2's firewall rules. After adjusting the firewall settings I am now able to connect using the cluster name.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search