I cannot delete, remove, rebuild, or repopulate fulltext catalogue.

I have SQL Server 7 on an NT server. The catalogue has
been working for a long time, however, it stopped and I
cannot seem to get it to repopulate. It stopped during an
incremental population. I have tried deleting it so I can
rebuild it, but whatever I try to do, I get the same
message: "Database is not full-text enabled yet". Can
anyone help?
Linda,
Could you review your server's Application Event log for any "Microsoft
Search" or MssCi source events (warnings, or errors) near the day & time
that the FT Catalog stopped working? Additionally, review the server System
Event log for any relate disk i/o warnings of low free disk space on both
your server's system disk drive (usually, the C:\ drive) or the drive where
the FT Catalog reside.
Most likely the FT Catalog is corrupt (and you may see a MssCi event with a
stack trace in it) and you may be in a "Catch-22" situation where you cannot
drop the FT Catalog (please try this), nor re-build it as well as not able
to run a Full or Incremental Population. IF so and depending upon the errors
in the Application event log, I have as sql script that you can "manually
de-reference" the FT Catalog, however, it is highly dependent on the type of
errors you are seeing and you may need to remove and re-install the FTS and
MSSearch components as well. Please, post any related application event
errors in your reply!
Thanks,
John
"Linda" <anonymous@.discussions.microsoft.com> wrote in message
news:2865701c46458$a8cf3cf0$a501280a@.phx.gbl...
> I have SQL Server 7 on an NT server. The catalogue has
> been working for a long time, however, it stopped and I
> cannot seem to get it to repopulate. It stopped during an
> incremental population. I have tried deleting it so I can
> rebuild it, but whatever I try to do, I get the same
> message: "Database is not full-text enabled yet". Can
> anyone help?
|||John,
I examined all logs but could not find anything concerning
the FT catalog. The logs for that date are no longer
available. It seems that the server was rebooted while
the catalog was performing an incremental update, freezing
the catalog.
I tried to drop it, but again got the message "Database is
not full-text enabled Please run
sp_fulltext_database 'enable' . When I do that, the query
never finishes. I have to reboot the server to clear it.
Maybe the script can help?
Thanks!!
Linda
>--Original Message--
>Linda,
>Could you review your server's Application Event log for
any "Microsoft
>Search" or MssCi source events (warnings, or errors) near
the day & time
>that the FT Catalog stopped working? Additionally, review
the server System
>Event log for any relate disk i/o warnings of low free
disk space on both
>your server's system disk drive (usually, the C:\ drive)
or the drive where
>the FT Catalog reside.
>Most likely the FT Catalog is corrupt (and you may see a
MssCi event with a
>stack trace in it) and you may be in a "Catch-22"
situation where you cannot
>drop the FT Catalog (please try this), nor re-build it as
well as not able
>to run a Full or Incremental Population. IF so and
depending upon the errors
>in the Application event log, I have as sql script that
you can "manually
>de-reference" the FT Catalog, however, it is highly
dependent on the type of
>errors you are seeing and you may need to remove and re-
install the FTS and
>MSSearch components as well. Please, post any related
application event
>errors in your reply!
>Thanks,
>John
>
>"Linda" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:2865701c46458$a8cf3cf0$a501280a@.phx.gbl...
an[vbcol=seagreen]
can
>
>.
>
|||Linda,
I emailed you the SQL Server 7.0 version to "manually de-reference" a FT
Catalog, please use it with caution as it requires modification to both
system tables as well as the registry hive. I highly recommend that you
backup both your database as well as the registry hive BEFORE using the
script as well as testing the procedure in a test environment prior to using
it.
Regards,
John
<anonymous@.discussions.microsoft.com> wrote in message
news:287e401c464fa$6a21ad10$a601280a@.phx.gbl...[vbcol=seagreen]
> John,
> I examined all logs but could not find anything concerning
> the FT catalog. The logs for that date are no longer
> available. It seems that the server was rebooted while
> the catalog was performing an incremental update, freezing
> the catalog.
> I tried to drop it, but again got the message "Database is
> not full-text enabled Please run
> sp_fulltext_database 'enable' . When I do that, the query
> never finishes. I have to reboot the server to clear it.
> Maybe the script can help?
> Thanks!!
> Linda
> any "Microsoft
> the day & time
> the server System
> disk space on both
> or the drive where
> MssCi event with a
> situation where you cannot
> well as not able
> depending upon the errors
> you can "manually
> dependent on the type of
> install the FTS and
> application event
> message
> an
> can
|||John,
Before I received your SQL I tried something that worked.
Since I couldn't stop the MSSearch engine, I changed the
startup from automatic to manual. Then I rebooted the
server. With MSSearch service off, I was then able to
manipulate the gatherlogs so I copied the entire folders
to another directory (as a backup). Then I deleted the
original folders, started the service, and
ran "sp_fulltext_database 'enable'" which worked this
time. I was then able to rebuild the fulltext catalogue
and repopulate it. The search is working fine now. You
were right...I think the files were corrupted. We are
still trying to find out how that happened.
Thanks for your help. I will keep the SQL in case that
happens again.
Linda
>--Original Message--
>Linda,
>I emailed you the SQL Server 7.0 version to "manually de-
reference" a FT
>Catalog, please use it with caution as it requires
modification to both
>system tables as well as the registry hive. I highly
recommend that you
>backup both your database as well as the registry hive
BEFORE using the
>script as well as testing the procedure in a test
environment prior to using[vbcol=seagreen]
>it.
>Regards,
>John
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:287e401c464fa$6a21ad10$a601280a@.phx.gbl...
concerning[vbcol=seagreen]
freezing[vbcol=seagreen]
is[vbcol=seagreen]
query[vbcol=seagreen]
it.[vbcol=seagreen]
for[vbcol=seagreen]
near[vbcol=seagreen]
review[vbcol=seagreen]
drive)[vbcol=seagreen]
a[vbcol=seagreen]
as[vbcol=seagreen]
re-[vbcol=seagreen]
has[vbcol=seagreen]
and I[vbcol=seagreen]
during[vbcol=seagreen]
I
>
>.
>
|||You're welcome, Linda,
As they say, there are many ways to 'skin a cat' (not that i'm anti-cat ;-),
but there are many ways to solve a problem and to further mix my metaphors,
the proof is in the pudding, i.e., whatever works, go with it!
Regards,
John
<anonymous@.discussions.microsoft.com> wrote in message
news:2d96a01c46a6d$2d545ea0$a501280a@.phx.gbl...[vbcol=seagreen]
> John,
> Before I received your SQL I tried something that worked.
> Since I couldn't stop the MSSearch engine, I changed the
> startup from automatic to manual. Then I rebooted the
> server. With MSSearch service off, I was then able to
> manipulate the gatherlogs so I copied the entire folders
> to another directory (as a backup). Then I deleted the
> original folders, started the service, and
> ran "sp_fulltext_database 'enable'" which worked this
> time. I was then able to rebuild the fulltext catalogue
> and repopulate it. The search is working fine now. You
> were right...I think the files were corrupted. We are
> still trying to find out how that happened.
> Thanks for your help. I will keep the SQL in case that
> happens again.
> Linda
> reference" a FT
> modification to both
> recommend that you
> BEFORE using the
> environment prior to using
> concerning
> freezing
> is
> query
> it.
> for
> near
> review
> drive)
> a
> as
> re-
> has
> and I
> during
> I
|||I would like a copy of that script if it's still
available! Thanks!
>--Original Message--
>Linda,
>I emailed you the SQL Server 7.0 version to "manually de-
reference" a FT
>Catalog, please use it with caution as it requires
modification to both
>system tables as well as the registry hive. I highly
recommend that you
>backup both your database as well as the registry hive
BEFORE using the
>script as well as testing the procedure in a test
environment prior to using[vbcol=seagreen]
>it.
>Regards,
>John
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:287e401c464fa$6a21ad10$a601280a@.phx.gbl...
concerning[vbcol=seagreen]
freezing[vbcol=seagreen]
is[vbcol=seagreen]
query[vbcol=seagreen]
it.[vbcol=seagreen]
for[vbcol=seagreen]
near[vbcol=seagreen]
review[vbcol=seagreen]
drive)[vbcol=seagreen]
a[vbcol=seagreen]
as[vbcol=seagreen]
re-[vbcol=seagreen]
has[vbcol=seagreen]
and I[vbcol=seagreen]
during[vbcol=seagreen]
I
>
>.
>