Windows Forum

Ask something
Discussion Locked

Groveler errors

0 helpful
3 replies

by desktop jinx

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

On my RIS server in the Application log I'm getting a Groveler Error EventID 12292 (groveler has failed due to a database error) every few hours (as little as 4, as many as 11 hours apart). The error is followed about 30 seconds later by a grovel stop and a grovel start, and in another 5 seconds a Groveler Warning EventID 8194 (USN log overrun).

How can I get rid of this persistent error?

3 replies

by joseph moore

Here is a piece of Technet article Q247611:

The following event message has also been seen immediately after the 8194 event message and may be caused by other SIS volume related problems:

Event Type: Error
Event Source: Groveler
Event Category: None
Event ID: 12292
Date: 12/15/1999
Time: 7:20:52 PM
User: N/A
Computer:
Description: The groveler on partition d:\has failed due to a database error.

In this case, you can use the Grovctrl.exe utility to rescan the affected volume by issuing the grovctrl.exe v drive_letter: command.

NOTE : The Grovctrl.exe utility is included on the Windows 2000 Server CD-ROM in the i386 folder and is compressed, but it is not installed during Setup. Use the expand d:\i386\grovctrl.ex_ c:\winnt\system32\grovctrl.exe command to expand it before attempting to use it.

And the same article says to just ignore the 8194 errors, it is just that the Groveler service"recreates the Groveler service database, and rescans the volume for duplicate files"

Here is the URL for the article:
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q247611
(please remove any spaces)

hope this helps

by desktop jinx

I've already done a grovctrl v four times now over the past couple of weeks, to no effect. The more-than-daily errors persist.

Perhaps only a complete reload will resolve it. Ouch.

This discussion is closed to new replies.