 | |
Can not Switch to 3rd node: error ID 5042: cluster node was not fo
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#31
 
| |||
| |||
|
Re: Can not Switch to 3rd node: error ID 5042: cluster node was no -
08-30-2008
, 04:11 PM
|
Thanks Geo I was able to switch cluster group including MSDTC to 3# node, and other group for instance 2 is ok too. and I did try bring SQLAPP group offline but still could not move with the same error. and more, tried to uninstall node 2#+3#, then reinstall node 2#+3# together(which was succeeded), still, I only can move group SQLAPP between 1# and 2#, 3# is in trouble. any clue? thanks George "Geoff N. Hiten" wrote: Are you able to move the cluster group to node 3? If so, take all resources offline inthe SQL group, move them to Node 3 and bring them online one at a time to see which resource fails. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "George" <George (AT) discussions (DOT) microsoft.com> wrote in message news:ED41D3AC-67C1-4C39-A749-E8BA84824954 (AT) microsoft (DOT) com... I have a active-active node running well, and need to add 3rd node. following bol I was able to install 2 instances on 3rd node, however, I only can swtich 2# instance to 3rd node, but 1# instance gives me the error: An error occurred attempting to move the 'SQLAPP' group. The cluster node was not found. Error ID: 5042 (000013b2). I tried to reinstall 3rd for instance 1# but noticed 3rd node is in the selected nodes list. On the properties of group SQLAPP, the 3rd node is in the preferred owners. pls what should I do to fix it? thanks! George |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.