You are currently offline, waiting for your internet to reconnect

"Event: ID 0; Source: ESENT" Appears in Application Log Every Few Seconds

This article was previously published under Q226508
This article has been archived. It is offered "as is" and will no longer be updated.
When you examine the application event log in Windows 2000, you may notice the following event message appearing every few seconds:
Event: ID 0
Source: ESENT
Category: Performance

Description: grovel (1712) Unexpected Win32 error: 0x15
These events are usually preceded by the following single event:
Event ID: 12291
Source: Groveler
Category: None

Description: USN log read failure on partition drive letter
You may also receive an error message stating that the application event log is full.
This behavior can occur if the Single Instance Storage (SIS) Groveler service is running, but can no longer read the database file on the volume that it is supposed to manage. When the SIS Groveler service starts, it searches for volumes to manage by looking for a root folder named SIS Common Store.

The SIS service is part of the Remote Installation Service (RIS) installation and manages volumes that contain operating system images. The SIS service reduces the disk space consumed by these images by storing duplicate files in the SIS Common Store folder.

There are two situations in which the applications events listed above can occur:
  • If a volume is managed by the SIS service and is suddenly reformatted, or becomes damaged.
  • If you move a volume that contains Remote Installation images (a volume that contains a SIS Common Store folder) from one computer to an existing computer running the RIS service and then suddenly format that volume.

    NOTE: This can occur if you use the /X switch with the FORMAT command to force a volume dismount before formatting.
To resolve this issue, use the appropriate method:
  • On a computer that is no longer going to run the RIS service, remove the service with the Add/Remove Programs tool in Control Panel before formatting the volume. This also removes the SIS service and prevents the event messages from occurring.
  • Have the Groveler service reinstate your volumes by stopping and starting the Single Instance Storage Groveler service. You can do this either in the Computer Management snap-in, or by typing the following lines at a command prompt:

    net stop "Single Instance Storage Groveler"
    net start "Single Instance Storage Groveler"
The SIS service only manages volumes that contain a root folder named SIS Common Store.
1712 jet

Article ID: 226508 - Last Review: 12/05/2015 13:57:50 - Revision: 2.2

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Datacenter Server

  • kbnosurvey kbarchive kbenv kberrmsg kbprb KB226508