Hi "Maurice N ~ MVP"
Thanks for your posting. I did as you said and found a file "Windows
Update.log" (i.e. space after *s*, before *U*, so must be V4).
But then I also found a file "WindowsUpdate.log" (i.e. no space, so V5). I
copied the set of lines for the last session: these are below:-
2004-08-24 17:19:05+0100 792 4c0 Service Main starts
2004-08-24 17:19:05+0100 792 4c0 Using BatchFlushAge = 29824.
2004-08-24 17:19:05+0100 792 4c0 Using SamplingValue = 529.
2004-08-24 17:19:05+0100 792 4c0 Successfully loaded event namespace
dictionary.
2004-08-24 17:19:08+0100 792 4c0 Successfully loaded client event namespace
descriptor.
2004-08-24 17:19:08+0100 792 4c0 Successfully initialized local event
logger. Events will be logged at
C:\WINDOWS\SoftwareDistribution\ReportingEvents.lo g.
2004-08-24 17:19:08+0100 792 4c0 Successfully initialized NT event logger.
2004-08-24 17:19:08+0100 792 4c0 Successfully initialized event uploader 0.
2004-08-24 17:19:08+0100 792 4c0 Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{ADCE45 AE-BD83-47A6-A91B-271AD0D5
C447}.bin for writing.
2004-08-24 17:19:08+0100 792 4c0 Successfully initialized event uploader 1.
2004-08-24 17:19:09+0100 792 4c0 WU client with version 5.4.3790.2182
successfully initialized
2004-08-24 17:19:09+0100 792 4c0 Service status is now SERVICE_RUNNING
2004-08-24 17:19:10+0100 792 378 Successfully opened event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{ADCE45 AE-BD83-47A6-A91B-271AD0D5
C447}.bin for reading.
2004-08-24 17:19:11+0100 2172 888 Trying to make out of proc datastore
active
2004-08-24 17:19:15+0100 2172 888 Out of proc datastore is now active
2004-08-24 17:19:15+0100 792 378 PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-08-24 17:19:16+0100 792 378 PT: Using server URL
https://v5.windowsupdate.microsoft.c...ce/client.asmx
2004-08-24 17:19:16+0100 792 378 PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-08-24 17:19:17+0100 792 31c Service received connect notification
2004-08-24 17:19:17+0100 792 378 PT: Using server URL
https://v5.windowsupdate.microsoft.c...ce/client.asmx
2004-08-24 17:19:17+0100 792 378 URL for server is
http://v5stats.windowsupdate.microso...ebService.asmx
2004-08-24 17:19:17+0100 792 378 Trying to upload 7 events using cached
cookie.
2004-08-24 17:19:21+0100 792 378 DetectCompressionType returning type 0,
hr=0x1
2004-08-24 17:19:21+0100 792 378 Successfully uploaded 7 events.
2004-08-24 17:19:21+0100 792 378 Deleted event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{ADCE45 AE-BD83-47A6-A91B-271AD0D5
C447}.bin.
2004-08-24 17:19:54+0100 792 4c0 start delayed initialization of WU client
2004-08-24 17:19:54+0100 792 4c0 WU client successfully loaded ongoing
download call {3806F3AD-31F1-4920-BDC6-7F7B56B2F2C8} from datastore
2004-08-24 17:19:54+0100 792 4c0 WU client succeeded to load 1 persisted
Download Calls
2004-08-24 17:19:54+0100 792 4c0 Client Call Recorder finished delayed
initialization
2004-08-24 17:19:55+0100 792 4c0 AU is disabled, not initializing any
handlers
2004-08-24 17:19:55+0100 792 4c0 AU finished delayed initialization
2004-08-24 17:25:08+0100 2172 888 Out of proc datastore is shutting down
2004-08-24 17:25:09+0100 2172 888 Out of proc datastore is now inactive
Like Chinese to me, I fear!
Cheers,
John
[To reply to me ONLY, remove the 'zy_']
<> wrote in message
news:...
john wrote:
> According to a posting in 'Dell Talk', Microsoft have temporarily
> stopped WinXP SP2 downloads because of bugs in SP2. Does anyone know
> if this is true?
>
> I've certainly been having probs in downloading SP2. As recommended,
> I switched on 'Auto Updates' about a week ago and nothing seems to be
> happening. (I've got XP Home and a broadband connection).
>
> Cheers,
> John
> [To reply to me ONLY, remove the 'zy_']
Did not hear that. I downloaded the full SP2 network-install just on this
past Monday.
On the Auto updates, take a good look inside (at the bottom) your Windows
Update.log file.
On your C drive (that's usually the case. If you have multi-boot setup,
you'll know where to look).
Your Windows is either at C:\Windows or C:\WINNT (like Pete).
Then if it is V4 of Windows Update, look for file Windows Update.log
(space after *s* , before *U*)
For V5, no space WindowsUpdate.log
Use Notepad or Wordpad to open & view contents. Scan down to the very
bottom. Copy the set of lines for that last session-date & paste back into
a reply in here.
You may see some "Error" for your last session with Automatic Updates. Or
it may have posted the "next" scheduled date-time.
--
Maurice N
MVP Windows - Shell / User
-----