Wednesday, March 7, 2012

Owner missing in Cluster

When I look at properties for FT in cluster administrator the only owner I
see is the node1 owner. Why doesn't owner node2 show up as a selection?
I'm thinking about doing the following below from a MS KB article to fix my
problem, any ideas?
You can reinstall the Full Text resource by manually running Ftsetup.exe.
However, before you can manually run Ftsetup.exe, you must perform the
following cleanup steps.
Note You must perform these cleanup steps on all nodes in the cluster group.
1. Delete the NewInstanceName subkey under the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\G athering
Manager\Applications
2. Delete the NewInstanceName subkey under the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\A pplications
3. Locate the shared data directory of the new clustered instance, and then
delete everything under the FTData folder.
Note Typically, the FTData folder includes some .0 files, some .1 files, and
a SQLServer$NewInstanceName folder.
After you have completed the cleanup steps, you can reinstall the Full Text
resource.
Note Make sure that you only run Ftsetup.exe from the node from which you
originally ran the SQL Server Setup program. Also, make sure that the node
has control of the shared drive.
To manually run Ftsetup.exe, you can use the following command-line
command:
"Path of the new clustered instance Bin folder\ftsetup.exe"
SQLServer$InstanceName SQL Server Account 1 0 1 0
Note InstanceName is the name of the new clustered instance of SQL Server.
SQL Server Account is the account under which SQL Server runs.
This account must have local administrator permissions on the node from
which you run Ftsetup.exe.
Tim,
Before you attempt re-installing the FT Search resource via the steps in KB
article 899580 "Full Text resource fails when you install a new clustered
instance after you apply SQL2K SP3 to an existing clustered instance" at
http://support.microsoft.com/default...;en-us;899580, what do you
see when you failover to the 2nd node (node2)?
As I don't have a clustered server at home <G>, you may want to call in to
PSS Microsoft SQL Server support and open a support case, as cluster issues
can be troublesome...
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Tim" <tim@.nospam.com> wrote in message
news:iTP7f.15378$B73.6907@.news.cpqcorp.net...
> When I look at properties for FT in cluster administrator the only owner I
> see is the node1 owner. Why doesn't owner node2 show up as a selection?
> I'm thinking about doing the following below from a MS KB article to fix
> my
> problem, any ideas?
> ----
> --
> You can reinstall the Full Text resource by manually running Ftsetup.exe.
> However, before you can manually run Ftsetup.exe, you must perform the
> following cleanup steps.
> Note You must perform these cleanup steps on all nodes in the cluster
> group.
> 1. Delete the NewInstanceName subkey under the following registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\G athering
> Manager\Applications
> 2. Delete the NewInstanceName subkey under the following registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\A pplications
> 3. Locate the shared data directory of the new clustered instance, and
> then
> delete everything under the FTData folder.
> Note Typically, the FTData folder includes some .0 files, some .1 files,
> and
> a SQLServer$NewInstanceName folder.
> After you have completed the cleanup steps, you can reinstall the Full
> Text
> resource.
> Note Make sure that you only run Ftsetup.exe from the node from which you
> originally ran the SQL Server Setup program. Also, make sure that the node
> has control of the shared drive.
> To manually run Ftsetup.exe, you can use the following command-line
> command:
> "Path of the new clustered instance Bin folder\ftsetup.exe"
> SQLServer$InstanceName SQL Server Account 1 0 1 0
> Note InstanceName is the name of the new clustered instance of SQL Server.
> SQL Server Account is the account under which SQL Server runs.
> This account must have local administrator permissions on the node from
> which you run Ftsetup.exe.
>
|||What happens when you failover to the other node? The owner name should
change? Is this a multi-instance cluster?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tim" <tim@.nospam.com> wrote in message
news:iTP7f.15378$B73.6907@.news.cpqcorp.net...
> When I look at properties for FT in cluster administrator the only owner I
> see is the node1 owner. Why doesn't owner node2 show up as a selection?
> I'm thinking about doing the following below from a MS KB article to fix
my
> problem, any ideas?
> ----
--
> --
> You can reinstall the Full Text resource by manually running Ftsetup.exe.
> However, before you can manually run Ftsetup.exe, you must perform the
> following cleanup steps.
> Note You must perform these cleanup steps on all nodes in the cluster
group.
> 1. Delete the NewInstanceName subkey under the following registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\G athering
> Manager\Applications
> 2. Delete the NewInstanceName subkey under the following registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\A pplications
> 3. Locate the shared data directory of the new clustered instance, and
then
> delete everything under the FTData folder.
> Note Typically, the FTData folder includes some .0 files, some .1 files,
and
> a SQLServer$NewInstanceName folder.
> After you have completed the cleanup steps, you can reinstall the Full
Text
> resource.
> Note Make sure that you only run Ftsetup.exe from the node from which you
> originally ran the SQL Server Setup program. Also, make sure that the node
> has control of the shared drive.
> To manually run Ftsetup.exe, you can use the following command-line
> command:
> "Path of the new clustered instance Bin folder\ftsetup.exe"
> SQLServer$InstanceName SQL Server Account 1 0 1 0
> Note InstanceName is the name of the new clustered instance of SQL Server.
> SQL Server Account is the account under which SQL Server runs.
> This account must have local administrator permissions on the node from
> which you run Ftsetup.exe.
>
|||Since FTS only has owner of node1 it will not failover to node2, error
message is 'An error occured when attempting to move the SQL Group Group. A
node is not availible for this resource'
"John Kane" <jt-kane@.comcast.net> wrote in message
news:%2328%23C7p2FHA.3300@.TK2MSFTNGP15.phx.gbl...
> Tim,
> Before you attempt re-installing the FT Search resource via the steps in
KB
> article 899580 "Full Text resource fails when you install a new clustered
> instance after you apply SQL2K SP3 to an existing clustered instance" at
> http://support.microsoft.com/default...;en-us;899580, what do
you
> see when you failover to the 2nd node (node2)?
> As I don't have a clustered server at home <G>, you may want to call in to
> PSS Microsoft SQL Server support and open a support case, as cluster
issues[vbcol=seagreen]
> can be troublesome...
> Regards,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Tim" <tim@.nospam.com> wrote in message
> news:iTP7f.15378$B73.6907@.news.cpqcorp.net...
I
> ----
--[vbcol=seagreen]
Ftsetup.exe.[vbcol=seagreen]
you[vbcol=seagreen]
node[vbcol=seagreen]
Server.
>
|||Sounds like SQL FTS is not installed correctly on the second node. Evict the
second node, remove SQL from this node, and then reinstall it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tim" <tim@.nospam.com> wrote in message
news:3K68f.15428$zO3.12361@.news.cpqcorp.net...
> Since FTS only has owner of node1 it will not failover to node2, error
> message is 'An error occured when attempting to move the SQL Group Group.
A[vbcol=seagreen]
> node is not availible for this resource'
>
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:%2328%23C7p2FHA.3300@.TK2MSFTNGP15.phx.gbl...
> KB
clustered[vbcol=seagreen]
> you
to[vbcol=seagreen]
> issues
owner[vbcol=seagreen]
> I
selection?[vbcol=seagreen]
fix[vbcol=seagreen]
> ----
> --
> Ftsetup.exe.
files,[vbcol=seagreen]
> you
> node
> Server.
from
>
|||Tim,
What errors (if any) are reported in the Cluster log? Additionally, review
the server's application event log for both "Microsoft Search" and MssCi
source events (warnings and errors), and let me know if you have any errors
with the following text: "80070002 - The system cannot find the file
specified".
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Tim" <tim@.nospam.com> wrote in message
news:3K68f.15428$zO3.12361@.news.cpqcorp.net...
> Since FTS only has owner of node1 it will not failover to node2, error
> message is 'An error occured when attempting to move the SQL Group Group.
> A
> node is not availible for this resource'
>
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:%2328%23C7p2FHA.3300@.TK2MSFTNGP15.phx.gbl...
> KB
> you
> issues
> I
> --
> Ftsetup.exe.
> you
> node
> Server.
>
|||By evicting the 2nd node and uninstalling/reinstalling sql then rejoining
will it break anything? We also have IIS clustered, MSDTC, etc... Is there
a good web site we can refer to, step-by-step instructions for the above
method?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eLded312FHA.3188@.TK2MSFTNGP12.phx.gbl...
> Sounds like SQL FTS is not installed correctly on the second node. Evict
the[vbcol=seagreen]
> second node, remove SQL from this node, and then reinstall it.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Tim" <tim@.nospam.com> wrote in message
> news:3K68f.15428$zO3.12361@.news.cpqcorp.net...
Group.[vbcol=seagreen]
> A
in[vbcol=seagreen]
> clustered
at[vbcol=seagreen]
do[vbcol=seagreen]
in[vbcol=seagreen]
> to
> owner
> selection?
> fix
> ----
the[vbcol=seagreen]
cluster[vbcol=seagreen]
key:[vbcol=seagreen]
key:[vbcol=seagreen]
and[vbcol=seagreen]
> files,
Full[vbcol=seagreen]
which[vbcol=seagreen]
the
> from
>
|||It appears as if your second node is hosed - or the fts part of it is. By
following the sequence I recommended it should rejoin file. I suggest
however that you post to the clustering newsgroup for clarification on what
the best way to proceed is.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tim" <tim@.nospam.com> wrote in message
news:jrx8f.15582$iF4.7525@.news.cpqcorp.net...
> By evicting the 2nd node and uninstalling/reinstalling sql then rejoining
> will it break anything? We also have IIS clustered, MSDTC, etc... Is
there[vbcol=seagreen]
> a good web site we can refer to, step-by-step instructions for the above
> method?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eLded312FHA.3188@.TK2MSFTNGP12.phx.gbl...
> the
> Group.
steps[vbcol=seagreen]
> in
instance"[vbcol=seagreen]
> at
[vbcol=seagreen]
> do
> in
to[vbcol=seagreen]
> ----
> the
> cluster
> key:
> key:
> and
> Full
> which
> the
command-line
>

No comments:

Post a Comment