"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\Gathering
>
> Manager\Applications
>
> 2. Delete the NewInstanceName subkey under the following registry key:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Applications
>
> 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.
>
>

"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.aspx?scid=kb;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\Gathering
> >
> > Manager\Applications
> >
> > 2. Delete the NewInstanceName subkey under the following registry key:
> >
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Applications
> >
> > 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" <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\Gathering
>
> Manager\Applications
>
> 2. Delete the NewInstanceName subkey under the following registry key:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Applications
>
> 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" <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...
>> 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.aspx?scid=kb;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\Gathering
>> >
>> > Manager\Applications
>> >
>> > 2. Delete the NewInstanceName subkey under the following registry key:
>> >
>> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Applications
>> >
>> > 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" <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...
> > 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.aspx?scid=kb;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\Gathering
> > >
> > > Manager\Applications
> > >
> > > 2. Delete the NewInstanceName subkey under the following registry key:
> > >
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Applications
> > >
> > > 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.
> > >
> > >
> >
> >
>
>

"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
> 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
> > 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.aspx?scid=kb;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\Gathering
> > > >
> > > > Manager\Applications
> > > >
> > > > 2. Delete the NewInstanceName subkey under the following registry
key:
> > > >
> > > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Applications
> > > >
> > > > 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" <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
> 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
> > 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
> > > 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.aspx?scid=kb;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\Gathering
> > > > >
> > > > > Manager\Applications
> > > > >
> > > > > 2. Delete the NewInstanceName subkey under the following registry
> key:
> > > > >
> > > > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Applications
> > > > >
> > > > > 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.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>