Full Text Indexing Option Disabled

i, like hundreds of other people, am unable to use the Full Text indexing
feature because of the bug in SQL Server Enterprise Manager that disables
the ability to configure it.
See the Microsoft Knowledge Base article, but realize that it doesn't apply.
http://support.microsoft.com/?kbid=270671
It suggests that the problem is due to being logged onto your client
computer using a local account. It implies that because the account is local
to your computer (as opposed to being a domain account), you are not able to
query the state of the MSSearch service on the target SQL Server machine.
When Enterprise Manager is unable to query the state of the MSSearch on the
target SQL Server machine, it assumes the MSSearch service on the target SQL
Server machine is either disabled or not installed - and therefore prevents
you from configuring Full-Text indexing.
Problem is, we are not logged on using a local account; we are logged on
using a domain account. What is more, the domain account we are using is a
domain administrative account - the account has full ability to query state
of services on the remote SQL Server machine.
The we are experiencing has nothing to do with logging onto the client
computer using a local account. So what does it have to do with? What should
the knowledge base article say about this problem? What is the actual
problem?
i know this bug was introduced in Enterprise Manager with 2000sp2. Does
anyone know if this will be fixed in an upcoming service pack?
References:
http://support.microsoft.com/?kbid=270671
http://tinyurl.com/2wseqa
http://tinyurl.com/2mj8aj
http://tinyurl.com/3aqhea
http://tinyurl.com/35gf54
http://tinyurl.com/384wq7
http://tinyurl.com/3bmnab
http://tinyurl.com/2spgfq
http://tinyurl.com/3df22d
Keywords:
SQL Server Enterprise Manager Full-Text Indexing option disabled grayed out
greyed out "Full-Text Indexing..." full text indexing disabled sqlem, cannot
configure full text, fulltext disabled, fulltext indexing feature disabled,
howto configure fulltext indexing menu item disabled
did you try this?
http://www.indexserverfaq.com/TableNotEnabled.htm
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
"Ian Boyd" <ian.msnews010@.avatopia.com> wrote in message
news:OQDnYS1RHHA.488@.TK2MSFTNGP06.phx.gbl...
> i, like hundreds of other people, am unable to use the Full Text indexing
> feature because of the bug in SQL Server Enterprise Manager that disables
> the ability to configure it.
> See the Microsoft Knowledge Base article, but realize that it doesn't
> apply.
> http://support.microsoft.com/?kbid=270671
>
> It suggests that the problem is due to being logged onto your client
> computer using a local account. It implies that because the account is
> local to your computer (as opposed to being a domain account), you are not
> able to query the state of the MSSearch service on the target SQL Server
> machine. When Enterprise Manager is unable to query the state of the
> MSSearch on the target SQL Server machine, it assumes the MSSearch service
> on the target SQL Server machine is either disabled or not installed - and
> therefore prevents you from configuring Full-Text indexing.
> Problem is, we are not logged on using a local account; we are logged on
> using a domain account. What is more, the domain account we are using is a
> domain administrative account - the account has full ability to query
> state of services on the remote SQL Server machine.
> The we are experiencing has nothing to do with logging onto the client
> computer using a local account. So what does it have to do with? What
> should the knowledge base article say about this problem? What is the
> actual problem?
> i know this bug was introduced in Enterprise Manager with 2000sp2. Does
> anyone know if this will be fixed in an upcoming service pack?
> References:
> http://support.microsoft.com/?kbid=270671
> http://tinyurl.com/2wseqa
> http://tinyurl.com/2mj8aj
> http://tinyurl.com/3aqhea
> http://tinyurl.com/35gf54
> http://tinyurl.com/384wq7
> http://tinyurl.com/3bmnab
> http://tinyurl.com/2spgfq
> http://tinyurl.com/3df22d
> Keywords:
> SQL Server Enterprise Manager Full-Text Indexing option disabled grayed
> out greyed out "Full-Text Indexing..." full text indexing disabled sqlem,
> cannot configure full text, fulltext disabled, fulltext indexing feature
> disabled, howto configure fulltext indexing menu item disabled
>
>
|||Hello Ian,
Its not just permissions but also firewalls that can get in the way. I have
this and am pretty sure it was looking at my local machine.
Run EM on the server itself should allow you to create your indexes.
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons

> i, like hundreds of other people, am unable to use the Full Text
> indexing feature because of the bug in SQL Server Enterprise Manager
> that disables the ability to configure it.
> See the Microsoft Knowledge Base article, but realize that it doesn't
> apply. http://support.microsoft.com/?kbid=270671
> It suggests that the problem is due to being logged onto your client
> computer using a local account. It implies that because the account is
> local to your computer (as opposed to being a domain account), you are
> not able to query the state of the MSSearch service on the target SQL
> Server machine. When Enterprise Manager is unable to query the state
> of the MSSearch on the target SQL Server machine, it assumes the
> MSSearch service on the target SQL Server machine is either disabled
> or not installed - and therefore prevents you from configuring
> Full-Text indexing.
> Problem is, we are not logged on using a local account; we are logged
> on using a domain account. What is more, the domain account we are
> using is a domain administrative account - the account has full
> ability to query state of services on the remote SQL Server machine.
> The we are experiencing has nothing to do with logging onto the client
> computer using a local account. So what does it have to do with? What
> should the knowledge base article say about this problem? What is the
> actual problem?
> i know this bug was introduced in Enterprise Manager with 2000sp2.
> Does anyone know if this will be fixed in an upcoming service pack?
> References:
> http://support.microsoft.com/?kbid=270671
> http://tinyurl.com/2wseqa
> http://tinyurl.com/2mj8aj
> http://tinyurl.com/3aqhea
> http://tinyurl.com/35gf54
> http://tinyurl.com/384wq7
> http://tinyurl.com/3bmnab
> http://tinyurl.com/2spgfq
> http://tinyurl.com/3df22d
> Keywords:
> SQL Server Enterprise Manager Full-Text Indexing option disabled
> grayed out
> greyed out "Full-Text Indexing..." full text indexing disabled sqlem,
> cannot
> configure full text, fulltext disabled, fulltext indexing feature
> disabled,
> howto configure fulltext indexing menu item disabled
|||> did you try this?
> http://www.indexserverfaq.com/TableNotEnabled.htm
Yes.
|||> Its not just permissions but also firewalls that can get in the way. I
> have this and am pretty sure it was looking at my local machine.
The windows firewall is not enabled on my Windows XP SP2 machine. The server
is Windows 2000.

> Run EM on the server itself should allow you to create your indexes.
This, oddly enough, works.
Thank you.
|||Ian,
Make sure your polling interval is turned on in EM. To do this,
select Tools --> Options... and check the box for "Server state
polling".
If polling is not on, EM can't check to see if the MS Search service
is running. This results in the options being grayed out.
This only works on the server where SQL Server is intalled. As a
general rule, I turn this off for client machines, as it generates a
lot of network traffic, especially if you have a bunch of servers
defined in EM.
Hope this works. I spent days following all the instructions out
there from MS and the groups. Finally figured it out after comparing
registry entries for a server that worked and one that didn't.
Rick
On Feb 4, 3:29 pm, Simon Sabin <SimonSa...@.noemail.noemail> wrote:
> Hello Ian,
> Its not just permissions but also firewalls that can get in the way. I have
> this and am pretty sure it was looking at my local machine.
> Run EM on the server itself should allow you to create your indexes.
> Simon Sabin
> SQL Server MVPhttp://sqlblogcasts.com/blogs/simons
>
>
>
>
>
> - Show quoted text -