Full Text Search Installation doesn't work??

I installed Full Text Search on my Standard Personal
Edition following the steps in this Microsoft Link:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;827449&Product=sql2k
When I try to enable full text search, I get the following
error message. Can anyone help? :
Server: Msg 7609, Level 17, State 2, Procedure
sp_fulltext_database, Line 46
Full-Text Search is not installed, or a full-text
component cannot be loaded.
I can see Microsoft search (which I didn't before) on the
Service Manager. I have also started the service. Why
does it show grayed out in Enterprise Mananager - Tools -
Full Text Indexing - eventhough I installed it? Please
HELPPPPP. Thanks
JohnCan anybody help me with this Please. I am waiting
desperately. The installation seemed fine but I dont seem
to see the Full Text Indexing thing - it is grayed out in
Enterprise Manager and not found in suporting services.
Help!!!!
John
>--Original Message--
>I installed Full Text Search on my Standard Personal
>Edition following the steps in this Microsoft Link:
>http://support.microsoft.com/default.aspx?scid=kb;en-
>us;827449&Product=sql2k
>When I try to enable full text search, I get the
following
>error message. Can anyone help? :
>Server: Msg 7609, Level 17, State 2, Procedure
>sp_fulltext_database, Line 46
>Full-Text Search is not installed, or a full-text
>component cannot be loaded.
>I can see Microsoft search (which I didn't before) on the
>Service Manager. I have also started the service. Why
>does it show grayed out in Enterprise Mananager - Tools -
>Full Text Indexing - eventhough I installed it? Please
>HELPPPPP. Thanks
>John
>.
>|||I fixed the problem. Reapply SP3a fixed the Full Text
problem. Thx.
John
>--Original Message--
>Can anybody help me with this Please. I am waiting
>desperately. The installation seemed fine but I dont
seem
>to see the Full Text Indexing thing - it is grayed out in
>Enterprise Manager and not found in suporting services.
>Help!!!!
>John
>
>>--Original Message--
>>I installed Full Text Search on my Standard Personal
>>Edition following the steps in this Microsoft Link:
>>http://support.microsoft.com/default.aspx?scid=kb;en-
>>us;827449&Product=sql2k
>>When I try to enable full text search, I get the
>following
>>error message. Can anyone help? :
>>Server: Msg 7609, Level 17, State 2, Procedure
>>sp_fulltext_database, Line 46
>>Full-Text Search is not installed, or a full-text
>>component cannot be loaded.
>>I can see Microsoft search (which I didn't before) on
the
>>Service Manager. I have also started the service. Why
>>does it show grayed out in Enterprise Mananager - Tools -
>>Full Text Indexing - eventhough I installed it? Please
>>HELPPPPP. Thanks
>>John
>>.
>.
>

Full Text Repair

We had a customer request a full text installation after
the application of SP4 and the slammer hotfix. It throws
an error that refers to a re-installation of SP4, which
will not work with any hot fixes applied after the fact.
Does anyone have a different route to follow that
uninstall the hotfix, then reapply the SP4, and then
reapply the hot fix?
Thanks in advance for any information.
Emil
what is the exact error message you are getting?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Emil" <emilcaruthers@.hotmail.com> wrote in message
news:698301c4758b$4e941cd0$a301280a@.phx.gbl...
> We had a customer request a full text installation after
> the application of SP4 and the slammer hotfix. It throws
> an error that refers to a re-installation of SP4, which
> will not work with any hot fixes applied after the fact.
> Does anyone have a different route to follow that
> uninstall the hotfix, then reapply the SP4, and then
> reapply the hot fix?
> Thanks in advance for any information.
> Emil
|||use culture;
SELECT * from FREETEXTTABLE(tblMasterEvents,*,'art');
Get this:
Search on full-text catalog 'culture' for database ID 41, table ID
1381579960 with search condition 'art' failed with unknown result (565f9c4).
The name of the database is not relevant, as all return the error.
Thanks for looking.
Emil Caruthers
"Hilary Cotter" wrote:

> what is the exact error message you are getting?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Emil" <emilcaruthers@.hotmail.com> wrote in message
> news:698301c4758b$4e941cd0$a301280a@.phx.gbl...
>
>
|||Emil,
Since your customer has already applied SP4, I'm assuming that this is a SQL
Server 7.0 installation as there currently is no publicly released SP4 for
SQL Sever 2000.
For SQL Server 7.0 installations, there is a registry key and value that you
can change in order to successfully re-install SP4 after applying a post-SP4
hotfix. Specifically, registry key called
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQL Server\Current Version\
"CSDVersion"
It will contain your hotfix build version number such that 7.00.xxx is the
build number. Record this value and then change it to the SP4 build value of
7.00.1063 and then re-install SP4. If successful, then re-install your
hotfix and confirm that this registry key value has changed back to your
recorded hotfix build number.
BTW, the hex value in the unknown result below is a 'garbage' value as this
is a bug with SQL Server 7.0 FTS and is fixed by applying (or re-applying)
the latest service pack.
Regards,
John
"Emil" <Emil@.discussions.microsoft.com> wrote in message
news:76173F35-121A-4ED7-852F-3328824CEC69@.microsoft.com...
> use culture;
> SELECT * from FREETEXTTABLE(tblMasterEvents,*,'art');
> Get this:
> Search on full-text catalog 'culture' for database ID 41, table ID
> 1381579960 with search condition 'art' failed with unknown result
(565f9c4).[vbcol=seagreen]
>
> The name of the database is not relevant, as all return the error.
> Thanks for looking.
> --
> Emil Caruthers
>
> "Hilary Cotter" wrote:
|||Thank you kindly, and I will try this.
Emil
Emil Caruthers
"John Kane" wrote:

> Emil,
> Since your customer has already applied SP4, I'm assuming that this is a SQL
> Server 7.0 installation as there currently is no publicly released SP4 for
> SQL Sever 2000.
> For SQL Server 7.0 installations, there is a registry key and value that you
> can change in order to successfully re-install SP4 after applying a post-SP4
> hotfix. Specifically, registry key called
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQL Server\Current Version\
> "CSDVersion"
> It will contain your hotfix build version number such that 7.00.xxx is the
> build number. Record this value and then change it to the SP4 build value of
> 7.00.1063 and then re-install SP4. If successful, then re-install your
> hotfix and confirm that this registry key value has changed back to your
> recorded hotfix build number.
> BTW, the hex value in the unknown result below is a 'garbage' value as this
> is a bug with SQL Server 7.0 FTS and is fixed by applying (or re-applying)
> the latest service pack.
> Regards,
> John
>
> "Emil" <Emil@.discussions.microsoft.com> wrote in message
> news:76173F35-121A-4ED7-852F-3328824CEC69@.microsoft.com...
> (565f9c4).
>
>

Full text index functino not installed properly

I recently upgraded a SQL server 7 installation to 2000 sp3a. This morning I
need to enable full text indexing. I went through the installation process
but the indexing options are not showing up. I tried a CLI and it told me
the services are not installed. How can I troubleshoot full text
installation or re-installs the serviceS?
The Microsoft Search service can be installed via the SQL Server setup
program. You might try the Add/Remove Programs entry for SQL Server to see
if you can add just the MS Search service.
HTH
Jerry
"CPLEV" <CPLEV@.discussions.microsoft.com> wrote in message
news:89D35CE3-D649-4AF6-8A3E-EB9ABD71105B@.microsoft.com...
>I recently upgraded a SQL server 7 installation to 2000 sp3a. This morning
>I
> need to enable full text indexing. I went through the installation
> process
> but the indexing options are not showing up. I tried a CLI and it told me
> the services are not installed. How can I troubleshoot full text
> installation or re-installs the serviceS?

Full text index functino not installed properly

I recently upgraded a SQL server 7 installation to 2000 sp3a. This morning
I
need to enable full text indexing. I went through the installation process
but the indexing options are not showing up. I tried a CLI and it told me
the services are not installed. How can I troubleshoot full text
installation or re-installs the serviceS?The Microsoft Search service can be installed via the SQL Server setup
program. You might try the Add/Remove Programs entry for SQL Server to see
if you can add just the MS Search service.
HTH
Jerry
"CPLEV" <CPLEV@.discussions.microsoft.com> wrote in message
news:89D35CE3-D649-4AF6-8A3E-EB9ABD71105B@.microsoft.com...
>I recently upgraded a SQL server 7 installation to 2000 sp3a. This morning
>I
> need to enable full text indexing. I went through the installation
> process
> but the indexing options are not showing up. I tried a CLI and it told me
> the services are not installed. How can I troubleshoot full text
> installation or re-installs the serviceS?

Full text index functino not installed properly

I recently upgraded a SQL server 7 installation to 2000 sp3a. This morning I
need to enable full text indexing. I went through the installation process
but the indexing options are not showing up. I tried a CLI and it told me
the services are not installed. How can I troubleshoot full text
installation or re-installs the serviceS?The Microsoft Search service can be installed via the SQL Server setup
program. You might try the Add/Remove Programs entry for SQL Server to see
if you can add just the MS Search service.
HTH
Jerry
"CPLEV" <CPLEV@.discussions.microsoft.com> wrote in message
news:89D35CE3-D649-4AF6-8A3E-EB9ABD71105B@.microsoft.com...
>I recently upgraded a SQL server 7 installation to 2000 sp3a. This morning
>I
> need to enable full text indexing. I went through the installation
> process
> but the indexing options are not showing up. I tried a CLI and it told me
> the services are not installed. How can I troubleshoot full text
> installation or re-installs the serviceS?

Full Text Index

Could Full Index option only be configured during installation? When I
try sp_fulltext_table on a table, I get the message that full text is
not enabled for the system.

--sharif"Sharif Islam" <mislam@.npspam.uiuc.eduwrote in message
news:fe8olf$aav$1@.news.ks.uiuc.edu...

Quote:

Originally Posted by

Could Full Index option only be configured during installation? When I try
sp_fulltext_table on a table, I get the message that full text is not
enabled for the system.
>
>
--sharif

You can install it after if you need to. Just pop in the CD.

Make sure to install any applicable Service Packs also afterwards.

--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

FTS Security Issue

Hi,
FTS will not populate the catalogs. 0 Items.
I have a new installation W2003 with SQL2K Sp3.
The SQL Server is running with a high security configuration.
All the SQL services are running under an account Domain\SQLService which is a plain old user in the domain and on the SQL Server box.
The local system account was chosen during installation. I changed to the domain user via the Enterprise Manager after the fact. SQL Server and SQL Agent run fine. BUILTIN\Administrators has been removed.
I saw a post that said changing the service account from one account and back to the original should fix the problem. It did not. I see "Login failed for NT AUTHORITY\SYSTEM" in the SQL Error Log when I try to build the catalog. I checked the account th
at is running MS Search in the Services dialog and it is still Local System. When I changed accounts on SQL Server, I changed it to myself a local admin and then back to the Domain\SQLService account. I tried changing the MS Search account via the Service
s dialog to Domain\SQLService account and now it will not start. Domain\SQLService has full control on the FTDATA directory. Any other directories or registery keys that perhaps Domain\SQLService needs access to, but is not being set?
Thanks,
Norman
Follow up...
Here are some messages from the event log:
12:14:21 PMSearch Service 7052The Search service has loaded project <SQLServer SQL0002000005>.
12:14:19 PMIndexer 7070The Search service has added project <SQL0002000005>.
12:14:19 PMIndexer 7071The Search service has removed project <SQL0002000005>.
12:14:19 PMIndexer 7042Project <SQLServer SQL0002000005> has been shut down as requested by user.
12:14:05 PMIndexer 7045The catalog was not propagated, because no new files were detected for the project <SQLServer SQL0002000005>.
12:14:05 PMGatherer 3018The end of crawl for project <SQLServer SQL0002000005> has been detected. The Gatherer successfully processed 0 documents totaling 0K. It failed to filter 1 documents. 0 URLs could not be reached or were denied access.
12:14:05 PMGatherer 3024The crawl for project <SQLServer SQL0002000005> could not be started, because no crawl seeds could be accessed. Fix the errors and try the crawl again.
12:14:05 PMGatherer 3036The crawl seed <MSSQL75://SQLServer/37fa4c37> in project <SQLServer SQL0002000005> cannot be accessed. Error: 800700e9 - No process is on the other end of the pipe. .
12:14:04 PMGatherer 3019The crawl on project <SQLServer SQL0002000005> has started.
|||Norman,
The MSSearch service requires that either the BUILTIN\Administrators login
be present or that [NT Authority\System] localsystem login have the below
rights and this is why you are seeing ("Login failed for NT
AUTHORITY\SYSTEM" ) after removing the BUILTIN\Administrators login:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
See also KB article Q263712 "INF: How To Prevent Windows NT Administrators
From Administering a Clustered SQL Server"
at http://support.microsoft.com/default...;EN-US;q263712 for more
info.
Regards,
John
"Norman" <anonymous@.discussions.microsoft.com> wrote in message
news:C6CE845A-0975-4801-8B0B-5B02D848F336@.microsoft.com...
> Follow up...
> Here are some messages from the event log:
> 12:14:21 PM Search Service 7052 The Search service has loaded project
<SQLServer SQL0002000005>.
> 12:14:19 PM Indexer 7070 The Search service has added project
<SQL0002000005>.
> 12:14:19 PM Indexer 7071 The Search service has removed project
<SQL0002000005>.
> 12:14:19 PM Indexer 7042 Project <SQLServer SQL0002000005> has been shut
down as requested by user.
> 12:14:05 PM Indexer 7045 The catalog was not propagated, because no new
files were detected for the project <SQLServer SQL0002000005>.
> 12:14:05 PM Gatherer 3018 The end of crawl for project <SQLServer
SQL0002000005> has been detected. The Gatherer successfully processed 0
documents totaling 0K. It failed to filter 1 documents. 0 URLs could not be
reached or were denied access.
> 12:14:05 PM Gatherer 3024 The crawl for project <SQLServer SQL0002000005>
could not be started, because no crawl seeds could be accessed. Fix the
errors and try the crawl again.
> 12:14:05 PM Gatherer 3036 The crawl seed <MSSQL75://SQLServer/37fa4c37> in
project <SQLServer SQL0002000005> cannot be accessed. Error: 800700e9 - No
process is on the other end of the pipe. .
> 12:14:04 PM Gatherer 3019 The crawl on project <SQLServer SQL0002000005>
has started.
>
|||John,
No kudos to Microsoft for the high level security requiements for MS Search and not providing a KB with a work around for highly secure environments.
FYI:
Even though I found posts that indicate the contrary, the MS Search service remains Local System Account regardless of which account you put in the the SQL Service or SQL Agent at installation or after the fact via the Enterprise Manager. I tried it on se
veral SQL Server installations on W2K and W2003.
My compromise solution was to create a domain account specifically for the MS Search service and make it local admin and sa in the SQL Server. This seems to function correctly for all the test I have tried. The SQL Server service is then still locked down
as long as there are no holes to exploit via the FTS queries. (I won't hold my breath)
Norman
|||Norman,
Unfortunately, I'd have to agree with you. FYI, the "Microsoft Search"
(mssearch.exe) service should ALWAYS be started and running under the
"system" or LocalSystem account as that how it is currently designed in SQL
Server 2000. However, for SQL Server 2005 (Yukon) this has changed and the
new MSSearch service, will be able to run under the same service account as
the MSSQLServer service.
If I was in the SQL MVP program, I'd be glad to volunteer and write such a
KB article, but alas I'm not *yet* in that program...
Regards,
John
"Norman" <anonymous@.discussions.microsoft.com> wrote in message
news:F954B2E0-FCDA-4692-8F80-D10DB1F5F701@.microsoft.com...
> John,
> No kudos to Microsoft for the high level security requiements for MS
Search and not providing a KB with a work around for highly secure
environments.
> FYI:
> Even though I found posts that indicate the contrary, the MS Search
service remains Local System Account regardless of which account you put in
the the SQL Service or SQL Agent at installation or after the fact via the
Enterprise Manager. I tried it on several SQL Server installations on W2K
and W2003.
> My compromise solution was to create a domain account specifically for the
MS Search service and make it local admin and sa in the SQL Server. This
seems to function correctly for all the test I have tried. The SQL Server
service is then still locked down as long as there are no holes to exploit
via the FTS queries. (I won't hold my breath)
> Norman

FTS Installation Problem - unavailable in SQL Server

Hello, I have a SQL Server 2000 sp4 server. Trying to install Full-Text
Search. I can see the Microsoft Search service and it shows as started. But
the Full-Text Search option in SEM is 'grayed out'. The FTS system procs
also report that FTS is not available. SQL Server has been stopped/restarted
but still no luck. Is there something else that needs to happen to make SQL
Server 2K see that FTS is installed?
- Thanks,
Chris M.
Does this help?
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
"Chris M" <ChrisM@.discussions.microsoft.com> wrote in message
news:C445089B-5F09-40D9-B376-C6F60B669E86@.microsoft.com...
> Hello, I have a SQL Server 2000 sp4 server. Trying to install Full-Text
> Search. I can see the Microsoft Search service and it shows as started.
> But
> the Full-Text Search option in SEM is 'grayed out'. The FTS system procs
> also report that FTS is not available. SQL Server has been
> stopped/restarted
> but still no luck. Is there something else that needs to happen to make
> SQL
> Server 2K see that FTS is installed?
> - Thanks,
> Chris M.