Problems with Indexing service on Windows 2000 SP4

T

Tom

I am running Windows 2000 SP4 on a IBM server. The box
serves as a Intranet server running on IIS 5 with Server
Extensions 2002. Approx. 15 web-sites are hosted on it.
While the IIS functionality is flawless I am having severe
problems with the Indexing service. It works fine for a
couple of days and then all of a sudden the catalog
becomes unavailable. The service seems to be started but
unless I stop and restart indexing, the catalog remains
unavailable. I get event id's that point to the catalog of
a single intranet site but once this problem appears it
affects all catalogs on the server.

I get the following errors in the Application event log:
Event ID: 4128 - Error 3221225529 detected in content
index on e:\esc\indexcatalog\catalog.wci.
Event ID: 4126 - Cleaning up corrupt content index
metadata on e:\esc\indexcatalog\catalog.wci. Index will
be automatically restored by refiltering all documents.

I have tried to delete the old catalog and re-create a
brand new one at a new location but the problem persists.

Does anybody have an idea on how to approach this issue?

Cheers,
Tom
 
M

Mark-Allen Perry

Check: http://www.eventid.net/display.asp?eventid=4128&eventno=1899&source=Ci&phase=1

--
And always try the MS KB first before posting.
The answer is probably already posted.
MS KB: http://support.microsoft.com/default.aspx?scid=fh;EN-US;KBHOWTO
----
Mark-Allen Perry
ALPHA Systems
Marly, Switzerland
mark-allen_AT_mvps_DOT_org

I am running Windows 2000 SP4 on a IBM server. The box
serves as a Intranet server running on IIS 5 with Server
Extensions 2002. Approx. 15 web-sites are hosted on it.
While the IIS functionality is flawless I am having severe
problems with the Indexing service. It works fine for a
couple of days and then all of a sudden the catalog
becomes unavailable. The service seems to be started but
unless I stop and restart indexing, the catalog remains
unavailable. I get event id's that point to the catalog of
a single intranet site but once this problem appears it
affects all catalogs on the server.

I get the following errors in the Application event log:
Event ID: 4128 - Error 3221225529 detected in content
index on e:\esc\indexcatalog\catalog.wci.
Event ID: 4126 - Cleaning up corrupt content index
metadata on e:\esc\indexcatalog\catalog.wci. Index will
be automatically restored by refiltering all documents.

I have tried to delete the old catalog and re-create a
brand new one at a new location but the problem persists.

Does anybody have an idea on how to approach this issue?

Cheers,
Tom
 
T

Tom

I have to admit I did see that KB before but had already
taken all precautions as outlined in there.
However, you did help me fix my problems as I discovered
that all exception rules that I had applied to our
AntiVirus application (McAfee) had simply disappeared
which meant a conflict between AntiVirus and the index
service. EPO seems to be working fine, I just have to know
about it :)
We removed that particular server from having exception
and scan rules pushed to it and voila, seems to be working
just fine.

Thank you for spending time on my post. Much appreciated.
 
M

Mark-Allen Perry

Glad to help (even indirectly....) :)

--
And always try the MS KB first before posting.
The answer is probably already posted.
MS KB: http://support.microsoft.com/default.aspx?scid=fh;EN-US;KBHOWTO
----
Mark-Allen Perry
ALPHA Systems
Marly, Switzerland
mark-allen_AT_mvps_DOT_org

I have to admit I did see that KB before but had already
taken all precautions as outlined in there.
However, you did help me fix my problems as I discovered
that all exception rules that I had applied to our
AntiVirus application (McAfee) had simply disappeared
which meant a conflict between AntiVirus and the index
service. EPO seems to be working fine, I just have to know
about it :)
We removed that particular server from having exception
and scan rules pushed to it and voila, seems to be working
just fine.

Thank you for spending time on my post. Much appreciated.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top