Fullt Text Search fails in a 2 node cluster

Hi!
I have a problem with Full Text Search in a clustered enviroment.
The Resource Fullt Text Search will not come online, it fails and giving me
a error in the log that says
"An Error occurred during the online operation for instance <SQL Server
Fulltext (UTB2)>: 80070002 - the system cannot find the file specified."
I′ve tried to reinstall Full Text by reading the KB 827449, but when i get
to the part where i should use the command "ftsetup.exe" i get a error in the
application log saying:
"Faulting application ftsetup.exe, version 2000.80.2039.0 faulting module
msvcr71.dll, version 7.10.3052.4, fault adress 0x00014d5c."
I also get a similar error concerning msvcrt.dll version 7.0.3790.1830.
We are using Windows 2003 SP1 and SQL 2000 Enterprise edition SP4
The strange about this is that right now there are 4 instances on the same
node where 2 of them has full text online and working but the 2 others has
the error mentioned above, so as i can understand there are no problem with
the nodes but instead i believe that the instances is not aware of Microsoft
Search. therefore as the KB article says i need to run the command
FTSETUP.EXE to configure the instances with Microsoft Search.
Right now i have no other ideas, fearing that the only thing to solve this
is to reinstall the whole SQL instance :o( wich is nothing i′m looking
forward to.
So please if you have any ideas, fill me in...
SweGuy
Sweden
Look in the FTData folder for each instance for files called Clus0.0,
clus0.1 etc. If those are not there, you may want to consider calling PSS
on this, as clustered FT issues are very difficult to troubleshoot.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"SweGuy" <SweGuy@.discussions.microsoft.com> wrote in message
news:FB3CFE0A-FDB8-4DE6-ACD0-9395599AE818@.microsoft.com...
> Hi!
> I have a problem with Full Text Search in a clustered enviroment.
> The Resource Fullt Text Search will not come online, it fails and giving
> me
> a error in the log that says
> "An Error occurred during the online operation for instance <SQL Server
> Fulltext (UTB2)>: 80070002 - the system cannot find the file specified."
> Ive tried to reinstall Full Text by reading the KB 827449, but when i get
> to the part where i should use the command "ftsetup.exe" i get a error in
> the
> application log saying:
> "Faulting application ftsetup.exe, version 2000.80.2039.0 faulting module
> msvcr71.dll, version 7.10.3052.4, fault adress 0x00014d5c."
> I also get a similar error concerning msvcrt.dll version 7.0.3790.1830.
> We are using Windows 2003 SP1 and SQL 2000 Enterprise edition SP4
> The strange about this is that right now there are 4 instances on the same
> node where 2 of them has full text online and working but the 2 others has
> the error mentioned above, so as i can understand there are no problem
> with
> the nodes but instead i believe that the instances is not aware of
> Microsoft
> Search. therefore as the KB article says i need to run the command
> FTSETUP.EXE to configure the instances with Microsoft Search.
> Right now i have no other ideas, fearing that the only thing to solve this
> is to reinstall the whole SQL instance :o( wich is nothing im looking
> forward to.
> So please if you have any ideas, fill me in...
> --
> SweGuy
> Sweden
|||Yes the FDATA folder exist and i have also granted both the SQL and the
Cluster Service Account full control to the folder. Also checked permissions
in the registry. It looks OK everywhere but it fails on the DLLs mentioned
before.
SweGuy
IT Professional
Sweden
"Kevin3NF" wrote:

> Look in the FTData folder for each instance for files called Clus0.0,
> clus0.1 etc. If those are not there, you may want to consider calling PSS
> on this, as clustered FT issues are very difficult to troubleshoot.
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> http://kevin3nf.blogspot.com
>
> "SweGuy" <SweGuy@.discussions.microsoft.com> wrote in message
> news:FB3CFE0A-FDB8-4DE6-ACD0-9395599AE818@.microsoft.com...
>
>
|||does this help?
http://www.indexserverfaq.com/clusterfailure.htm
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"SweGuy" <SweGuy@.discussions.microsoft.com> wrote in message
news:FB3CFE0A-FDB8-4DE6-ACD0-9395599AE818@.microsoft.com...
> Hi!
> I have a problem with Full Text Search in a clustered enviroment.
> The Resource Fullt Text Search will not come online, it fails and giving
> me
> a error in the log that says
> "An Error occurred during the online operation for instance <SQL Server
> Fulltext (UTB2)>: 80070002 - the system cannot find the file specified."
> Ive tried to reinstall Full Text by reading the KB 827449, but when i get
> to the part where i should use the command "ftsetup.exe" i get a error in
> the
> application log saying:
> "Faulting application ftsetup.exe, version 2000.80.2039.0 faulting module
> msvcr71.dll, version 7.10.3052.4, fault adress 0x00014d5c."
> I also get a similar error concerning msvcrt.dll version 7.0.3790.1830.
> We are using Windows 2003 SP1 and SQL 2000 Enterprise edition SP4
> The strange about this is that right now there are 4 instances on the same
> node where 2 of them has full text online and working but the 2 others has
> the error mentioned above, so as i can understand there are no problem
> with
> the nodes but instead i believe that the instances is not aware of
> Microsoft
> Search. therefore as the KB article says i need to run the command
> FTSETUP.EXE to configure the instances with Microsoft Search.
> Right now i have no other ideas, fearing that the only thing to solve this
> is to reinstall the whole SQL instance :o( wich is nothing im looking
> forward to.
> So please if you have any ideas, fill me in...
> --
> SweGuy
> Sweden
|||I have opened a case with Microsoft Support. Hopefully we can clear this out.
I′l let you know how it goes.
SweGuy
IT Professional
Sweden
"Hilary Cotter" wrote:

> does this help?
> http://www.indexserverfaq.com/clusterfailure.htm
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "SweGuy" <SweGuy@.discussions.microsoft.com> wrote in message
> news:FB3CFE0A-FDB8-4DE6-ACD0-9395599AE818@.microsoft.com...
>
>
|||Who got your case? I mean the support engineer at MS...
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"SweGuy" <SweGuy@.discussions.microsoft.com> wrote in message
news:01CAF11F-F93A-44B5-9631-206DCB2885D0@.microsoft.com...[vbcol=seagreen]
>I have opened a case with Microsoft Support. Hopefully we can clear this
>out.
> Il let you know how it goes.
> --
> SweGuy
> IT Professional
> Sweden
>
> "Hilary Cotter" wrote:
|||I have no specific name but the guy i talked to in the phone was Daniel
Berglund. He has passed the problem forward to other support engineers.
Apperently this kind of problems ususally result in a re-installation of the
SQL instance, but Daniel thought that maybe someone has solved this matter in
another way.
And thats what i′m hoping for :o)
SweGuy
IT Professional
Sweden
"Kevin3NF" wrote:

> Who got your case? I mean the support engineer at MS...
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "SweGuy" <SweGuy@.discussions.microsoft.com> wrote in message
> news:01CAF11F-F93A-44B5-9631-206DCB2885D0@.microsoft.com...
>
>
|||Yup. The only "Official" way to fix most full-text resource issues is
uninstall/re-install.
Download filemon from sysinternals to get the exact file and path it is
looking for and go from there...
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"SweGuy" <SweGuy@.discussions.microsoft.com> wrote in message
news:FD031460-357C-414A-A2E4-2B69293DC12F@.microsoft.com...[vbcol=seagreen]
>I have no specific name but the guy i talked to in the phone was Daniel
> Berglund. He has passed the problem forward to other support engineers.
> Apperently this kind of problems ususally result in a re-installation of
> the
> SQL instance, but Daniel thought that maybe someone has solved this matter
> in
> another way.
> And thats what im hoping for :o)
> --
> SweGuy
> IT Professional
> Sweden
>
> "Kevin3NF" wrote:

Full Text Search Resource

Can u install FTS later on? I have a clustered env. and due to failure in
registering FTS the entire install is rolling back? so perhaps I can delete
the FTS Resource and install it later...
TIA
Yes, it can be installed later, just like any other component of the SQL
Server 2005 install.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Vai2000" <nospam@.microsoft.com> wrote in message
news:uEsn7dQIGHA.528@.TK2MSFTNGP12.phx.gbl...
> Can u install FTS later on? I have a clustered env. and due to failure in
> registering FTS the entire install is rolling back? so perhaps I can
> delete
> the FTS Resource and install it later...
> TIA
>

Full Text Compatible index

I want to put a full text search on a table. using SQL Server Management
Studio 20005.
The table has a clustered Key Like this:
Thing,Version,Field1,Field2 and so on.
The Key is Thing and Version.
I can create a index on these columns but it will not show up in the Full
Text Index utility (Full Text Index)(Define Full Text Index) Selection from
the table right click menu.
I have also tried no Clustered Key and just a index of the two fields which
does not work.
I might mention that other tables with only one column for the key work for
Full Text search.
Thank you
Jerry
Hi Jerry,
From your description, I understand that the indexed columns were not
displayed in the Full Text Index wizard in SSMS. The table had a clustered
key index with two columns. This issue did not occur if there is only one
Key column.
If I have misunderstood, please let me know.
This is expected by design. Essentially the problem was caused by KEY INDEX
constraints.
You may refer to:
CREATE FULLTEXT INDEX (Transact-SQL)
http://technet.microsoft.com/en-us/library/ms187317.aspx
From the article, we can see the following description regarding KEY INDEX:
<ref>
KEY INDEX index_name
Is the name of the unique key index on table_name. The KEY INDEX must be a
unique, single-key, non-nullable column. Select the smallest unique key
index for the full-text unique key. For best performance, a CLUSTERED index
is recommended.
</ref>
As you can see that the KEY INDEX can only be a single-key. Compound keys
are not allowed. To work around this issue, I recommend that you create a
single column with unique index so that the full-text index can be
correlated to rows in the table.
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Charles,
Thanks. I will use a identity column for the Index
Jerry
"Charles Wang[MSFT]" wrote:

> Hi Jerry,
> From your description, I understand that the indexed columns were not
> displayed in the Full Text Index wizard in SSMS. The table had a clustered
> key index with two columns. This issue did not occur if there is only one
> Key column.
> If I have misunderstood, please let me know.
> This is expected by design. Essentially the problem was caused by KEY INDEX
> constraints.
> You may refer to:
> CREATE FULLTEXT INDEX (Transact-SQL)
> http://technet.microsoft.com/en-us/library/ms187317.aspx
> From the article, we can see the following description regarding KEY INDEX:
> <ref>
> KEY INDEX index_name
> Is the name of the unique key index on table_name. The KEY INDEX must be a
> unique, single-key, non-nullable column. Select the smallest unique key
> index for the full-text unique key. For best performance, a CLUSTERED index
> is recommended.
> </ref>
> As you can see that the KEY INDEX can only be a single-key. Compound keys
> are not allowed. To work around this issue, I recommend that you create a
> single column with unique index so that the full-text index can be
> correlated to rows in the table.
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know. It is my pleasure to be of assistance.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>

Full Text Compatible index

I want to put a full text search on a table. using SQL Server Management
Studio 20005.
The table has a clustered Key Like this:
Thing,Version,Field1,Field2 and so on.
The Key is Thing and Version.
I can create a index on these columns but it will not show up in the Full
Text Index utility (Full Text Index)(Define Full Text Index) Selection from
the table right click menu.
I have also tried no Clustered Key and just a index of the two fields which
does not work.
I might mention that other tables with only one column for the key work for
Full Text search.
Thank you
--
JerryHi Jerry,
From your description, I understand that the indexed columns were not
displayed in the Full Text Index wizard in SSMS. The table had a clustered
key index with two columns. This issue did not occur if there is only one
Key column.
If I have misunderstood, please let me know.
This is expected by design. Essentially the problem was caused by KEY INDEX
constraints.
You may refer to:
CREATE FULLTEXT INDEX (Transact-SQL)
http://technet.microsoft.com/en-us/library/ms187317.aspx
From the article, we can see the following description regarding KEY INDEX:
<ref>
KEY INDEX index_name
Is the name of the unique key index on table_name. The KEY INDEX must be a
unique, single-key, non-nullable column. Select the smallest unique key
index for the full-text unique key. For best performance, a CLUSTERED index
is recommended.
</ref>
As you can see that the KEY INDEX can only be a single-key. Compound keys
are not allowed. To work around this issue, I recommend that you create a
single column with unique index so that the full-text index can be
correlated to rows in the table.
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Charles,
Thanks. I will use a identity column for the Index
--
Jerry
"Charles Wang[MSFT]" wrote:
> Hi Jerry,
> From your description, I understand that the indexed columns were not
> displayed in the Full Text Index wizard in SSMS. The table had a clustered
> key index with two columns. This issue did not occur if there is only one
> Key column.
> If I have misunderstood, please let me know.
> This is expected by design. Essentially the problem was caused by KEY INDEX
> constraints.
> You may refer to:
> CREATE FULLTEXT INDEX (Transact-SQL)
> http://technet.microsoft.com/en-us/library/ms187317.aspx
> From the article, we can see the following description regarding KEY INDEX:
> <ref>
> KEY INDEX index_name
> Is the name of the unique key index on table_name. The KEY INDEX must be a
> unique, single-key, non-nullable column. Select the smallest unique key
> index for the full-text unique key. For best performance, a CLUSTERED index
> is recommended.
> </ref>
> As you can see that the KEY INDEX can only be a single-key. Compound keys
> are not allowed. To work around this issue, I recommend that you create a
> single column with unique index so that the full-text index can be
> correlated to rows in the table.
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know. It is my pleasure to be of assistance.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>|||Hi Jerry,
Appreciate your update and response. I am glad to hear that the suggestions
are helpful. If you have any other questions or concerns, please do not
hesitate to contact us. It is always our pleasure to be of assistance.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

Full Text Compatible index

I want to put a full text search on a table. using SQL Server Management
Studio 20005.
The table has a clustered Key Like this:
Thing,Version,Field1,Field2 and so on.
The Key is Thing and Version.
I can create a index on these columns but it will not show up in the Full
Text Index utility (Full Text Index)(Define Full Text Index) Selection from
the table right click menu.
I have also tried no Clustered Key and just a index of the two fields which
does not work.
I might mention that other tables with only one column for the key work for
Full Text search.
Thank you
JerryHi Jerry,
From your description, I understand that the indexed columns were not
displayed in the Full Text Index wizard in SSMS. The table had a clustered
key index with two columns. This issue did not occur if there is only one
Key column.
If I have misunderstood, please let me know.
This is expected by design. Essentially the problem was caused by KEY INDEX
constraints.
You may refer to:
CREATE FULLTEXT INDEX (Transact-SQL)
http://technet.microsoft.com/en-us/...y/ms187317.aspx
From the article, we can see the following description regarding KEY INDEX:
<ref>
KEY INDEX index_name
Is the name of the unique key index on table_name. The KEY INDEX must be a
unique, single-key, non-nullable column. Select the smallest unique key
index for the full-text unique key. For best performance, a CLUSTERED index
is recommended.
</ref>
As you can see that the KEY INDEX can only be a single-key. Compound keys
are not allowed. To work around this issue, I recommend that you create a
single column with unique index so that the full-text index can be
correlated to rows in the table.
Hope this helps. If you have any other questions or concerns, please feel
free to let me know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Charles,
Thanks. I will use a identity column for the Index
--
Jerry
"Charles Wang[MSFT]" wrote:

> Hi Jerry,
> From your description, I understand that the indexed columns were not
> displayed in the Full Text Index wizard in SSMS. The table had a clustered
> key index with two columns. This issue did not occur if there is only one
> Key column.
> If I have misunderstood, please let me know.
> This is expected by design. Essentially the problem was caused by KEY INDE
X
> constraints.
> You may refer to:
> CREATE FULLTEXT INDEX (Transact-SQL)
> http://technet.microsoft.com/en-us/...y/ms187317.aspx
> From the article, we can see the following description regarding KEY INDEX
:
> <ref>
> KEY INDEX index_name
> Is the name of the unique key index on table_name. The KEY INDEX must be a
> unique, single-key, non-nullable column. Select the smallest unique key
> index for the full-text unique key. For best performance, a CLUSTERED inde
x
> is recommended.
> </ref>
> As you can see that the KEY INDEX can only be a single-key. Compound keys
> are not allowed. To work around this issue, I recommend that you create a
> single column with unique index so that the full-text index can be
> correlated to rows in the table.
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know. It is my pleasure to be of assistance.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
=============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>