fulltext search not working

HI!,
Fulltext search is not working, i have two databases, fulltext search
functionality was working fine on both of them till now. but suddenly
fulltext search on one of the databases started giving out errors.
when i try to populate, rebuild was giving out errors.
when i said sp_fulltext_database 'enable' on the db it gave out the error
"An unknown full-text failure (80004005) occurred in function EnumCatalogs
on full-text catalog ''."
when i said sp_help_fulltext_catalogs , it gave out this error
Full-Text Search is not enabled for the current database. Use
sp_fulltext_database to enable Full-Text Search.
whereas the fulltext catalog functionality is working fine on the other
database.
So, please help me resolve the problem.
The sql server was down for want of space. when space was cleared and sql
server restarted the fulltext catalog problem started.
Has the fulltext catalog problem got anything to do with sql server being
down.
Any help would be greatly appreciated.
Regards,
Prudhvi
I would try to rebuild the catalog.
Also the 80004005 is a generic access denied error message.
Consult this kb article for more information
http://support.microsoft.com/default...b;en-us;295772
"Prudhvi Raju" <PrudhviRaju@.discussions.microsoft.com> wrote in message
news:311D7D42-311B-41EC-9262-93402B8867ED@.microsoft.com...
> HI!,
> Fulltext search is not working, i have two databases, fulltext search
> functionality was working fine on both of them till now. but suddenly
> fulltext search on one of the databases started giving out errors.
> when i try to populate, rebuild was giving out errors.
> when i said sp_fulltext_database 'enable' on the db it gave out the error
> "An unknown full-text failure (80004005) occurred in function EnumCatalogs
> on full-text catalog ''."
> when i said sp_help_fulltext_catalogs , it gave out this error
> Full-Text Search is not enabled for the current database. Use
> sp_fulltext_database to enable Full-Text Search.
> whereas the fulltext catalog functionality is working fine on the other
> database.
> So, please help me resolve the problem.
> The sql server was down for want of space. when space was cleared and sql
> server restarted the fulltext catalog problem started.
> Has the fulltext catalog problem got anything to do with sql server being
> down.
> Any help would be greatly appreciated.
> Regards,
> Prudhvi
>
>
>
|||Prudhvi,
Could you post the full output of -- select @.@.version -- as this is most
important information needed to troubleshoot this FTS error message.
Depending upon the version of SQL Server, you are using, you may want to
review KB article: 295772 (Q295772) "How to debug full-text search when a
7608 (0x80004005) error message occurs in SQL Server" at:
http://support.microsoft.com/default...b;EN-US;295772
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Prudhvi Raju" <PrudhviRaju@.discussions.microsoft.com> wrote in message
news:311D7D42-311B-41EC-9262-93402B8867ED@.microsoft.com...
> HI!,
> Fulltext search is not working, i have two databases, fulltext search
> functionality was working fine on both of them till now. but suddenly
> fulltext search on one of the databases started giving out errors.
> when i try to populate, rebuild was giving out errors.
> when i said sp_fulltext_database 'enable' on the db it gave out the error
> "An unknown full-text failure (80004005) occurred in function EnumCatalogs
> on full-text catalog ''."
> when i said sp_help_fulltext_catalogs , it gave out this error
> Full-Text Search is not enabled for the current database. Use
> sp_fulltext_database to enable Full-Text Search.
> whereas the fulltext catalog functionality is working fine on the other
> database.
> So, please help me resolve the problem.
> The sql server was down for want of space. when space was cleared and sql
> server restarted the fulltext catalog problem started.
> Has the fulltext catalog problem got anything to do with sql server being
> down.
> Any help would be greatly appreciated.
> Regards,
> Prudhvi
>
>
>
|||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.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||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...b;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.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||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...b;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...
>
>
|||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[vbcol=seagreen]
> remote server.
> Regards,
> Prudhvi.
>
> "John Kane" wrote:
registry[vbcol=seagreen]
database[vbcol=seagreen]
installed[vbcol=seagreen]
as a[vbcol=seagreen]
key[vbcol=seagreen]
the[vbcol=seagreen]
When[vbcol=seagreen]
2000, so[vbcol=seagreen]
levels[vbcol=seagreen]
Search[vbcol=seagreen]