Index Server issue

[TonyKhela]

We have NT4 Server SP6.

The Index Server service (cisvc and cidaemon) is taking the whole cpu power and completely killing the server
(we have 2 PIII 600MHz CPUs).

Any ideas?

Can we schedule the indexing or will it run on a 'whenever it feels like' basis.
thx
TK

 

[ReddLefty]

Do you need the Indexing Service? If not, stop the services... or remove the indexes. I'm a little rusty in Windows NT v4.0, but I don't recall it having the Indexing Service.... I thought it started with Win2k.. but I could be wrong.






"In space, nobody can hear you click..."

 

[yannick]

We have also NT4 with SP6, running IIS.

Sometimes, the default web site stops by itself. I don't know why but I was thinking of the Indexing service because this is the only log I have in my event viewer. I know it's running so I will give a try to disable it. But in NT4, there is no service named "Indexing service" but one called "Content index". If you set it to start manually, there is no cisvc.exe and cidaemon.exe program running anymore.

 

[TonyKhela]

My issue still is that cisvc.exe and cidaemon.exe programs are taking up all the CPU processing 'all the time'.

Surely, this is something that someone has come across before.

Please help.

thx