(cross-post added to Vista General)
"Eric Aling" <Eric [email]Aling@discussions.microsoft.com[/email]> wrote in message news:113BF242-4C32-4ACB-8F6E-BD222A066FDC@microsoft.com...[color=blue]
> Hi,
>
> Having the same problem with the same build, but on one machine only. On my
> other it works ok, strange. Both had clean install. Logfile says:
>
>
> 2006-10-07 10:56:59:546 992 498 PT + ServiceId =
> {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL =
> [url]https://update.microsoft.com/v6/ClientWebService/client.asmx[/url]
> 2006-10-07 10:57:01:796 992 498 PT WARNING: GetConfig failure, error =
> 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code =
> 200
>
>
> So, looks like it is not possible to update this build right now using this
> webservice.[/color]


I don't think there is enough information here to diagnose this symptom.
The URL is https: so you can't trace the SOAP message flow with
something like FiddlerTool or netcap. You might be able to get some
extra detail from winhttptracecfg (assuming it still works on Vista.)
(Ref. KB307272)


Good luck

Robert
---

Hi,

I guess MS has turned off updates for build 5728. I'm using RC2 now, build
5744 and update is working ok.

Cheers

- Eric

"Robert Aldwinckle" wrote:
[color=blue]
> (cross-post added to Vista General)
> "Eric Aling" <Eric [email]Aling@discussions.microsoft.com[/email]> wrote in message news:113BF242-4C32-4ACB-8F6E-BD222A066FDC@microsoft.com...[color=green]
> > Hi,
> >
> > Having the same problem with the same build, but on one machine only. On my
> > other it works ok, strange. Both had clean install. Logfile says:
> >
> >
> > 2006-10-07 10:56:59:546 992 498 PT + ServiceId =
> > {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL =
> > [url]https://update.microsoft.com/v6/ClientWebService/client.asmx[/url]
> > 2006-10-07 10:57:01:796 992 498 PT WARNING: GetConfig failure, error =
> > 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code =
> > 200
> >
> >
> > So, looks like it is not possible to update this build right now using this
> > webservice.[/color]
>
>
> I don't think there is enough information here to diagnose this symptom.
> The URL is https: so you can't trace the SOAP message flow with
> something like FiddlerTool or netcap. You might be able to get some
> extra detail from winhttptracecfg (assuming it still works on Vista.)
> (Ref. KB307272)
>
>
> Good luck
>
> Robert
> ---
>
>
>[/color]

Hi,

Using RC2 (build 5744) now and update is working ok again. Guess that
updates for the unsupported 5728 was turned off.

Cheers

- Eric

"Robert Aldwinckle" wrote:
[color=blue]
> (cross-post added to Vista General)
> "Eric Aling" <Eric [email]Aling@discussions.microsoft.com[/email]> wrote in message news:113BF242-4C32-4ACB-8F6E-BD222A066FDC@microsoft.com...[color=green]
> > Hi,
> >
> > Having the same problem with the same build, but on one machine only. On my
> > other it works ok, strange. Both had clean install. Logfile says:
> >
> >
> > 2006-10-07 10:56:59:546 992 498 PT + ServiceId =
> > {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL =
> > [url]https://update.microsoft.com/v6/ClientWebService/client.asmx[/url]
> > 2006-10-07 10:57:01:796 992 498 PT WARNING: GetConfig failure, error =
> > 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code =
> > 200
> >
> >
> > So, looks like it is not possible to update this build right now using this
> > webservice.[/color]
>
>
> I don't think there is enough information here to diagnose this symptom.
> The URL is https: so you can't trace the SOAP message flow with
> something like FiddlerTool or netcap. You might be able to get some
> extra detail from winhttptracecfg (assuming it still works on Vista.)
> (Ref. KB307272)
>
>
> Good luck
>
> Robert
> ---
>
>
>[/color]

"Eric Aling" wrote:
[color=blue]
> Hi,
>
> Using RC2 (build 5744) now and update is working ok again. Guess that
> updates for the unsupported 5728 was turned off.
>
> Cheers
>
> - Eric
>
> "Robert Aldwinckle" wrote:
>[color=green]
> > (cross-post added to Vista General)
> > "Eric Aling" <Eric [email]Aling@discussions.microsoft.com[/email]> wrote in message news:113BF242-4C32-4ACB-8F6E-BD222A066FDC@microsoft.com...[color=darkred]
> > > Hi,
> > >
> > > Having the same problem with the same build, but on one machine only. On my
> > > other it works ok, strange. Both had clean install. Logfile says:
> > >
> > >
> > > 2006-10-07 10:56:59:546 992 498 PT + ServiceId =
> > > {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL =
> > > [url]https://update.microsoft.com/v6/ClientWebService/client.asmx[/url]
> > > 2006-10-07 10:57:01:796 992 498 PT WARNING: GetConfig failure, error =
> > > 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code =
> > > 200
> > >
> > >
> > > So, looks like it is not possible to update this build right now using this
> > > webservice.[/color]
> >
> >
> > I don't think there is enough information here to diagnose this symptom.
> > The URL is https: so you can't trace the SOAP message flow with
> > something like FiddlerTool or netcap. You might be able to get some
> > extra detail from winhttptracecfg (assuming it still works on Vista.)
> > (Ref. KB307272)
> >
> >
> > Good luck
> >
> > Robert
> > ---
> >
> >
> >[/color][/color]

And where can we find RC2??

greetz

CrAsHeR