Full Text Search breaks after disc replaced

Hello,
(I also posted to the WSS newsgroup but remembered
somebody suggesting that this type of question might be
better answered in the sqlserver.fulltext newsgroup).
We recently had to replace our discs with larger ones. So
we ghosted the original disc containing the WSS dbase,
configured new discs, then reimaged back. Everything
working fine, apart from the full-text search - searching
sites returns no results. This has happened before when
removing, replacing the discs. Strangely enough, when we
examined the services console, the MS Search Service had
reverted to an earlier domain logon (which is the domain
login with database rights - we changed this quite a while
back to the local system logon, which was recommended, and
search had been working correctly ever since). We changed
this logon once again back to local system and then
clicked on the enable full text search on the WSS
interface. The gatherer returned the errors, saying
it 'failed to filter 10052 documents' - 0 urls could not
be reached or were denied access. When we looked at the
full text catalogs in MSSQL Enterprise UI, they were only
1MB in size, but the actual full text files/catalogs on
the C drive were around 12Mb. I'm beginning to think
that some of those documents had been indexed at some
point by the domain logon, not the local system logon, and
now local system can't reach those documents? I am
thinking about opening Enterprise Manager, and 'rebuilding
the index' (this says it will delete the existing one and
build a new one), with the MS Search Service now switched
back to local system logon. Would this be the best course
of action
for me, would anything get lost, or does this simply look
at the existing dbases and rebuild from those?
Thanks,
Jeff
Can you try to change the SQL Server service account through EM as this KB
details?
http://support.microsoft.com/default...b;en-us;277549
This is applicable for SQL 2000 as well.
"Jeff" <anonymous@.discussions.microsoft.com> wrote in message
news:13bb001c4130f$9de78710$a301280a@.phx.gbl...
> Hello,
> (I also posted to the WSS newsgroup but remembered
> somebody suggesting that this type of question might be
> better answered in the sqlserver.fulltext newsgroup).
> We recently had to replace our discs with larger ones. So
> we ghosted the original disc containing the WSS dbase,
> configured new discs, then reimaged back. Everything
> working fine, apart from the full-text search - searching
> sites returns no results. This has happened before when
> removing, replacing the discs. Strangely enough, when we
> examined the services console, the MS Search Service had
> reverted to an earlier domain logon (which is the domain
> login with database rights - we changed this quite a while
> back to the local system logon, which was recommended, and
> search had been working correctly ever since). We changed
> this logon once again back to local system and then
> clicked on the enable full text search on the WSS
> interface. The gatherer returned the errors, saying
> it 'failed to filter 10052 documents' - 0 urls could not
> be reached or were denied access. When we looked at the
> full text catalogs in MSSQL Enterprise UI, they were only
> 1MB in size, but the actual full text files/catalogs on
> the C drive were around 12Mb. I'm beginning to think
> that some of those documents had been indexed at some
> point by the domain logon, not the local system logon, and
> now local system can't reach those documents? I am
> thinking about opening Enterprise Manager, and 'rebuilding
> the index' (this says it will delete the existing one and
> build a new one), with the MS Search Service now switched
> back to local system logon. Would this be the best course
> of action
> for me, would anything get lost, or does this simply look
> at the existing dbases and rebuild from those?
> Thanks,
> Jeff
|||Thanks Hilary, I'm going to try this over this weekend.
Would I need to 'rebuild' catalog after making the change
through the EM?
Jeff
>--Original Message--
>Can you try to change the SQL Server service account
through EM as this KB
>details?
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;277549
>This is applicable for SQL 2000 as well.
>"Jeff" <anonymous@.discussions.microsoft.com> wrote in
message
>news:13bb001c4130f$9de78710$a301280a@.phx.gbl...
So
searching
we
while
and
changed
only
and
and 'rebuilding
and
switched
course
look
>
>.
>
|||You shouldn't have to, but your catalog size indicates that you must.
"Jeff" <anonymous@.discussions.microsoft.com> wrote in message
news:1403f01c4135f$eaa92130$a301280a@.phx.gbl...
> Thanks Hilary, I'm going to try this over this weekend.
> Would I need to 'rebuild' catalog after making the change
> through the EM?
> Jeff
> through EM as this KB
> us;277549
> message
> So
> searching
> we
> while
> and
> changed
> only
> and
> and 'rebuilding
> and
> switched
> course
> look
sql