After SP2 - New Events being logged

After I applied SP2 to my Win XP Pro, I see multiple entries of the
following type in the Event Log:


wuauclt (4052) The database engine stopped. (Event ID#101)

wuaueng.dll (4052) SUS20ClientDataStore: The database engine stopped
the instance (0). (Event ID#103)

wuaueng.dll (4052) SUS20ClientDataStore: The database engine started a
new instance (0). (Event ID#102)

wuauclt (4052) The database engine 5.01.2600.2180 started. (Event
ID#100)

wuaueng.dll (2944) SUS20ClientDataStore: The database engine has
successfully completed recovery steps. (Event

ID#302)

wuaueng.dll (2944) SUS20ClientDataStore: The database engine has begun
replaying logfile
C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb .log. (Event ID#301)



Can someone enlighten me as to what is going on and what to do about
it?

Thanks in advance

Matt

I would also appreciate knowing what these are - I am getting them regularly
too.
Thanks. I did not apply SP2, just the v5 software update from v4. The Event
Source in all these is ESENT.


"Admin" <Net*> wrote in message
news:...
> After I applied SP2 to my Win XP Pro, I see multiple entries of the
> following type in the Event Log:
>
>
> wuauclt (4052) The database engine stopped. (Event ID#101)
>
> wuaueng.dll (4052) SUS20ClientDataStore: The database engine stopped
> the instance (0). (Event ID#103)
>
> wuaueng.dll (4052) SUS20ClientDataStore: The database engine started a
> new instance (0). (Event ID#102)
>
> wuauclt (4052) The database engine 5.01.2600.2180 started. (Event
> ID#100)
>
> wuaueng.dll (2944) SUS20ClientDataStore: The database engine has
> successfully completed recovery steps. (Event
>
> ID#302)
>
> wuaueng.dll (2944) SUS20ClientDataStore: The database engine has begun
> replaying logfile
> C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb .log. (Event ID#301)
>
>
>
> Can someone enlighten me as to what is going on and what to do about
> it?
>
> Thanks in advance
>
> Matt

Admin wrote:

> After I applied SP2 to my Win XP Pro, I see multiple entries of the
> following type in the Event Log:
>
>
> wuauclt (4052) The database engine stopped. (Event ID#101)
>
> wuaueng.dll (4052) SUS20ClientDataStore: The database engine stopped
> the instance (0). (Event ID#103)
>
> wuaueng.dll (4052) SUS20ClientDataStore: The database engine started a
> new instance (0). (Event ID#102)
>
> wuauclt (4052) The database engine 5.01.2600.2180 started. (Event
> ID#100)
>
> wuaueng.dll (2944) SUS20ClientDataStore: The database engine has
> successfully completed recovery steps. (Event
>
> ID#302)
>
> wuaueng.dll (2944) SUS20ClientDataStore: The database engine has begun
> replaying logfile
> C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb .log. (Event ID#301)
>
>
>
> Can someone enlighten me as to what is going on and what to do about
> it?
>
> Thanks in advance
>
> Matt

Don't worry about them. They are an effect of the new update service.
MS might take care of it at a future time but they don't indicate a
problem.

Admin wrote:

> After I applied SP2 to my Win XP Pro, I see multiple entries of
> the following type in the Event Log:
>
> wuauclt (4052) The database engine stopped. (Event ID#101)
> [snip]
>
> Can someone enlighten me as to what is going on and what to do
> about it?
Hi

They come from the WU v5 client, and they are information entries
only (they does not indicate that you have a problem).

From a recent post about this issue:

From: "David Kays [MSFT]" <>
Subject: Re: ESENT Messages
Date: Fri, 13 Aug 2004 15:01:45 -0700
Message-ID: <>
Newsgroups: microsoft.public.windowsupdate

<quote>
This is a known issue with the WU v5 client. It has to do with how the
client agent interacts with the Jet database engine. This is something
we'll consider fixing in a future version of the WU client. I'm not aware
of work arounds for this issue, sorry.
</quote>


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

"Torgeir Bakken \(MVP\)" <Torgeir.Bakken-> wrote in message news:<>...
> Admin wrote:
>
> > After I applied SP2 to my Win XP Pro, I see multiple entries of
> > the following type in the Event Log:
> >
> > wuauclt (4052) The database engine stopped. (Event ID#101)
> > [snip]
> >
> > Can someone enlighten me as to what is going on and what to do
> > about it?
> Hi
>
> They come from the WU v5 client, and they are information entries
> only (they does not indicate that you have a problem).
>
> From a recent post about this issue:
>
> From: "David Kays [MSFT]" <>
> Subject: Re: ESENT Messages
> Date: Fri, 13 Aug 2004 15:01:45 -0700
> Message-ID: <>
> Newsgroups: microsoft.public.windowsupdate
>
> <quote>
> This is a known issue with the WU v5 client. It has to do with how the
> client agent interacts with the Jet database engine. This is something
> we'll consider fixing in a future version of the WU client. I'm not aware
> of work arounds for this issue, sorry.
> </quote>

I, too, noticed the ESENT events after installing SP2 and going to
Windows Update. Probably the latter that triggered the new events.

I was able to stop them by setting the Automatic Update Service to
Manual in Administrative Tools > Services, noting that the description
states turning it off will also cripple Automatic Updates (I always
update manually) and the Windows Update web site itself. I'll just
have to remember to restart the Service when visiting there.

---
David