Hi Robert
The last download from Windows updater was 15.09.2004 which
was SP2, which according to the lo the Installation History was Successful
and the source was the Windows Update site. The only other log that i can
find that mentions the error No. 0xC8000147 is from the 31.12.2004 which is a
pretty big file.
The fist few lines are:
2004-12-27 17:28:22-0000 1092 608 URL for server is
http://v5stats.windowsupdate.microso...ebService.asmx
2004-12-27 17:28:22-0000 1092 608 Trying to upload 3 events using cached
cookie.
2004-12-27 17:28:37-0000 1092 608 DetectCompressionType returning type 0,
hr=0x1
2004-12-27 17:28:37-0000 1092 608 Successfully uploaded 3 events.
2004-12-27 17:28:37-0000 1092 608 Deleted event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{B09DBF 41-1F7E-44DE-9D05-B05D44056F06}.bin.
2004-12-27 17:33:22-0000 2268 dec Out of proc datastore is shutting down
2004-12-27 17:33:23-0000 2268 dec Out of proc datastore is now inactive
2004-12-27 18:03:34-0000 1092 448 Service received logoff notification.
I tried the URL
http://v5stats.windowsupdate.microso...ebService.asmx
on my browser and it came up with; Server Error in '/ReportingWebService'
Application, and indicated a Runtime Error.
Any help or suggestions would be most helpful, or would i be better off
uninstalling SP2 and reinstalling it fdrom a SP2 disk as all the problems
seem to have occured around the time it was installed.
Thanks for your assistance in this matter.
A very feed up Toby963
"Robert Aldwinckle" wrote:
> "Toby963" <> wrote in message
> news:FCF2ABF7-2194-40E2-86D6-...
> > Hi Robert
> > Sorry if i am appearing ignorant, but where do i find the
> > log(s) that you would like me to post?
>
>
> The names of an update's log(s) depend on the type of update.
> To be sure that I am seeing all possible diagnostics what I do is use
> Search Companion to find all files modified on the day that the update
> was done, then sort that result by Date Modified and look for files which
> changed about the time of the update.
>
> Less generally what you could try is searching for *.log files which
> contain your error code. I would omit the 0x prefix just in case
> some diagnostics refer to just the hex digits without identifying it
> explicitly as a hex constant.
>
>
> Good luck
>
> Robert
> ---
>
>
>