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.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
"palefox" <> wrote in message
news:02E92C1E-2457-4E32-BAD2-...
> Running XP Home pre-SP2...
>
> Has anyone else noticed multiple instances of 4 ESENT entries in the
> Application log of Event Viewer? Do I have to live with this or is this
> behavior fixable?
>
> The first one being this: (they all have to do with wuauclt)
>
> Event Type: Information
> Event Source: ESENT
> Event Category: General
> Event ID: 100
> Date: 8/11/2004
> Time: 10:29:30 AM
> User: N/A
> Computer: CPQ49314066312
> Description:
> wuauclt (3276) The database engine 5.01.2600.0000 started.
>
>
>
>
> They started right after this, in the System Log:
>
> Event Type: Information
> Event Source: Windows Update Agent
> Event Category: Installation
> Event ID: 19
> Date: 8/11/2004
> Time: 10:28:51 AM
> User: N/A
> Computer: CPQ49314066312
> Description:
> Installation Successful: Windows successfully installed the following
> update: Automatic Updates
>
> I think the above has to do with the v5 site. I checked my install history
> and it said my last was the IE update on 8/3.
|
Similar Threads
Linear Mode
