CISVC.EXE has left the building.

This was in TechNet-

PSS ID Number: Q191147
Article last modified on 07-28-1999

winnt:1.0,1.1,2.0

winnt

======================================================================
-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Index Server versions 1.0, 1.1, 2.0
-------------------------------------------------------------------------------

SYMPTOMS
========

You may see the error "the catalog is corrupt" when you issue a query in the
browser. You may also see catalog corruption errors in the application event
log. These messages will vary depending on the type of corruption detected.

CAUSE
=====

Index Server catalogs can be caused by unsafe computer shutdowns, system
crashes, or applications that write to or lock the catalog files while Index
Server is active.

RESOLUTION
==========

Normally, Index Server attempts to fix any corruption automatically; however,
sometimes it is necessary to manually fix the corruption. To do manually fix
corruption, stop and restart the Content Index service (for Index 1.x, stop and
restart the World Wide Web service.) This normally causes Index Server to
rebuild the catalog. If this does not work, stop Index Server again, locate the
Catalog.wci folder, and delete the contents of the folder. This manually deletes
the catalog. When you restart Index Server, the catalog is re-created.

See below

You know something, I could not stop the services on this machine but, the memory did it. Thanks a million.