Re: fulltext search not working

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: John Kane (jt-kane_at_comcast.net)
Date: 02/25/05 

Date: Fri, 25 Feb 2005 08:44:43 -0800

Prudhvi,
Sorry, I missed that info in the first post.... Usually, this error (An
unknown full-text failure (80004005)...) indicates a problem with the
MSSearch service components or registry key &/or values at the server level
and generally not specific to one database on a server. However, it may be
that specific FT Catalog registry keys/values maybe mis-configured or
missing that are linked to one database. However, you would need to open a
support case with Microsoft PSS SQL Server support as they have methods for
doing extended debugging of this issue to identify the exact cause of this
issue for you. If you cannot re-install the FTS components per the KB
article or the below method, then I'd recommend that you open a support case
with Microsoft SQL Server support.

Thanks,
John 

-- 
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Prudhvi Raju" <PrudhviRaju@discussions.microsoft.com> wrote in message
news:11DA5ABC-19AD-460C-84D1-94E3646BC34D@microsoft.com...
> John,
> As i told you in my first post, the FTS component is working fine on
another
> database in the same instance of sql server.
> i was just wondering if this issue can be sorted out without re-installing
> the FTS component as the server is a production database and is hosted on
a
> remote server.
>
> Regards,
> Prudhvi.
>
>
> "John Kane" wrote:
>
> > Prudhvi,
> > Thanks for providing the @@version info as that allows me to provide you
> > with a solution to error . Basically, this is a FTS component or
registry
> > key issue, that cannot be resolved by detaching & re-attaching the
database
> > as this problem is at the SQL Server level and not database specific.
> >
> > What you must do is to "re-install" the SQL Server 2000 Full-text Search
> > components via your SQL Server 2000 setup CD. As the FTS components are
> > already installed you will need to force the removal of the FTS
installed
> > checkmark via the removal or renaming of the following tracking registry
> > key. (If you're not using a named instance, remove "<Instance_Name>\".)
> >
> > NOTE: be sure to be logged on to the server as either Administrator or
as a
> > member of the server's Admin Group before deleting the below registry
key
> > and stop both the MSSQLServer and the MSSearch services.
> >
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> > Server\<Instance_Name>\Tracking\
> > {E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
> >
> > Once you're done removed (renamed) the above tracking key, then delete
the
> > MSSearch directory from either:
> >
> > drive_letter:\Program Files\Common Files\Microsoft Shared\
> > or
> > drive_letter::\Program Files\Common Files\System\
> >
> > Then using your SQL Server 2000 installation CD re-install via "Custom
> > Installation" the Full-Text Search component (it should be un-checked).
When
> > this completes find and save these files: SearchSetup.log (usually under
> > \windows or \winnt folders) and sqlsp.log. If any problems, please post
> > these files.
> >
> > Re-install the service pack that you may have applied to SQL Server
2000, so
> > that the newly re-installed MSSearch components are upgraded to SP3
levels
> > and then re-boot &/or restart the MSSearch and MSSQLServer services.
> >
> > You may also want to consult or perform the procedures document in the
> > following Kb article: 827449 "How to manually reinstall the Microsoft
Search
> > service for an instance of SQL 2000" at:
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;827449
> >
> > Hope that helps!
> > John
> >
> >
> >
> > -- 
> > SQL Full Text Search Blog
> > http://spaces.msn.com/members/jtkane/
> >
> >
> > "Prudhvi Manthena" <prudhvi.m@gmail.com> wrote in message
> > news:uqzgeGjGFHA.1528@TK2MSFTNGP09.phx.gbl...
> > > John,
> > >
> > > output of select @@version
> > >
> > > Microsoft SQL Server  2000 - 8.00.760 (Intel X86)
> > > Dec 17 2002 14:22:05
> > > Copyright (c) 1988-2003 Microsoft Corporation
> > > Standard Edition on Windows NT 5.2 (Build 3790: )
> > >
> > > It doesn't allow me to even rebuild.
> > >
> > > Can detaching and re-attaching the db solve my probs.
> > >
> > > regards,
> > > Prudhvi
> > >
> > > *** Sent via Developersdex http://www.developersdex.com ***
> > > Don't just participate in USENET...get rewarded for it!
> >
> >
> >

Relevant Pages

  • Re: fulltext search not working
    ... this is a FTS component or registry ... as this problem is at the SQL Server level and not database specific. ... and stop both the MSSQLServer and the MSSearch services. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: fulltext search not working
    ... As i told you in my first post, the FTS component is working fine on another ... database in the same instance of sql server. ... > as this problem is at the SQL Server level and not database specific. ... > and stop both the MSSQLServer and the MSSearch services. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: How to move system databases to new SAN drive in cluster serve
    ... See following article which contains information about Registry and editing ... Stop all services of virtual SQL Server by cluster administrator. ... On NODE1 change value of Key ... Start all services of virtual SQL Server by cluster administrator. ...
    (microsoft.public.sqlserver.clustering)
  • Re: SQL Performance Objects (sqlctr80.dll)
    ... reasons, such as Permission, Server Crash, Registry Modification and Virus. ... and "First Counter" values can vary between SQL Server ... Unload the SQL Server Counters ... In command line, execute "unlodctr MSSQLServer" (Without quotation, the ...
    (microsoft.public.sqlserver.setup)
  • Re: Failure to Login
    ... I had already checked the Registry ... At a command prompt, if I ... the MSDE was install with OS Authentication. ... >is the default setup for the SQL Server 2000 Data Engine.) ...
    (microsoft.public.sqlserver.msde)