<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 Administration
»
Adding Integration Services to clustered...
12 posts, Page 1 of 2
1
2
»»
Adding Integration Services to clustered nodes
Rate Topic
Display Mode
Topic Options
Author
Message
joffwilliams
joffwilliams
Posted Thursday, October 27, 2011 10:46 AM
SSC Journeyman
Group: General Forum Members
Last Login: Thursday, March 14, 2013 11:36 AM
Points: 91,
Visits: 149
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!
Post #1197081
SQLArcher
SQLArcher
Posted Thursday, October 27, 2011 10:29 PM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 3:33 AM
Points: 150,
Visits: 3,149
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.
Post #1197321
MysteryJimbo
MysteryJimbo
Posted Friday, October 28, 2011 12:19 AM
Ten Centuries
Group: General Forum Members
Last Login: Monday, May 06, 2013 8:14 AM
Points: 1,125,
Visits: 14,510
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
Post #1197326
SQLArcher
SQLArcher
Posted Friday, October 28, 2011 12:47 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 3:33 AM
Points: 150,
Visits: 3,149
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.
Post #1197335
joffwilliams
joffwilliams
Posted Monday, October 31, 2011 9:41 AM
SSC Journeyman
Group: General Forum Members
Last Login: Thursday, March 14, 2013 11:36 AM
Points: 91,
Visits: 149
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.
Post #1198144
MysteryJimbo
MysteryJimbo
Posted Monday, October 31, 2011 10:43 AM
Ten Centuries
Group: General Forum Members
Last Login: Monday, May 06, 2013 8:14 AM
Points: 1,125,
Visits: 14,510
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.
Post #1198210
joffwilliams
joffwilliams
Posted Monday, October 31, 2011 12:01 PM
SSC Journeyman
Group: General Forum Members
Last Login: Thursday, March 14, 2013 11:36 AM
Points: 91,
Visits: 149
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.
Post #1198238
SQLArcher
SQLArcher
Posted Monday, October 31, 2011 1:56 PM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 3:33 AM
Points: 150,
Visits: 3,149
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...
Post #1198299
joffwilliams
joffwilliams
Posted Monday, October 31, 2011 1:59 PM
SSC Journeyman
Group: General Forum Members
Last Login: Thursday, March 14, 2013 11:36 AM
Points: 91,
Visits: 149
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.
Post #1198301
joffwilliams
joffwilliams
Posted Thursday, November 03, 2011 3:05 PM
SSC Journeyman
Group: General Forum Members
Last Login: Thursday, March 14, 2013 11:36 AM
Points: 91,
Visits: 149
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.
Post #1200252
« Prev Topic
|
Next Topic »
12 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
