Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Update > 0x80190197 using new 3.0 Update Client

Reply
Thread Tools Display Modes

0x80190197 using new 3.0 Update Client

 
 
Shankomatic
Guest
Posts: n/a

 
      05-08-2007
We have several boxes that have received the 3.0 Windows Update Client from
WSUS 3.0. These clients will work fine connecting to Windows Update. When
using Microsoft Update instead they have a problem with our proxy servers.
We are using the NetApp Appliances.

In the past, (also still with Windows Update with the 3.x client) we are
prompted for a second authenticaion to the proxy server once we click either
"Express" or "Custom". Now when using the Microsoft Update site it goes
right to an error screen with the 0x80190197 error. Using a sniffer it
appears the proxy server is requesting authentication but it is never
retruned to the web page.

It appears somthing has changed between the two releases.
 
Reply With Quote
 
 
 
 
Sudheer GN [MSFT]
Guest
Posts: n/a

 
      05-09-2007
Hi,
We are sorry for the inconvenience and are investigating this issue.
In the meanwhile, can you please see if it is possible for you to exclude
Windows update URLs from requiring authentication in your proxy server to
make this scenario work.

--
Sudheer GN
Microsoft, WU Client

This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Shankomatic" <> wrote in message
news:70D553F8-24B7-4BB1-B470-...
> We have several boxes that have received the 3.0 Windows Update Client
> from
> WSUS 3.0. These clients will work fine connecting to Windows Update.
> When
> using Microsoft Update instead they have a problem with our proxy servers.
> We are using the NetApp Appliances.
>
> In the past, (also still with Windows Update with the 3.x client) we are
> prompted for a second authenticaion to the proxy server once we click
> either
> "Express" or "Custom". Now when using the Microsoft Update site it goes
> right to an error screen with the 0x80190197 error. Using a sniffer it
> appears the proxy server is requesting authentication but it is never
> retruned to the web page.
>
> It appears somthing has changed between the two releases.



 
Reply With Quote
 
Shankomatic
Guest
Posts: n/a

 
      05-09-2007
Our group is a small group in a major corporation. To get the team/vendor
that supports the proxy server to make that type of change would be nothing
short of a miracle.

"Sudheer GN [MSFT]" wrote:

> Hi,
> We are sorry for the inconvenience and are investigating this issue.
> In the meanwhile, can you please see if it is possible for you to exclude
> Windows update URLs from requiring authentication in your proxy server to
> make this scenario work.
>
> --
> Sudheer GN
> Microsoft, WU Client
>
> This posting is provided "As Is" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
> "Shankomatic" <> wrote in message
> news:70D553F8-24B7-4BB1-B470-...
> > We have several boxes that have received the 3.0 Windows Update Client
> > from
> > WSUS 3.0. These clients will work fine connecting to Windows Update.
> > When
> > using Microsoft Update instead they have a problem with our proxy servers.
> > We are using the NetApp Appliances.
> >
> > In the past, (also still with Windows Update with the 3.x client) we are
> > prompted for a second authenticaion to the proxy server once we click
> > either
> > "Express" or "Custom". Now when using the Microsoft Update site it goes
> > right to an error screen with the 0x80190197 error. Using a sniffer it
> > appears the proxy server is requesting authentication but it is never
> > retruned to the web page.
> >
> > It appears somthing has changed between the two releases.

>
>
>

 
Reply With Quote
 
Sudheer GN [MSFT]
Guest
Posts: n/a

 
      05-09-2007
Hi,
I would like to understand your situation more to see if there are any
work-arounds.
If your machines are being managed by WSUS 3.0 servers, what updates are you
trying to get from MU. Are those updates not available on Windows update
too?
You can contact me at my Microsoft email address. To get email address,
please remove "online." from my email address in this post.

--
Sudheer GN
Microsoft, WU Client

This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Shankomatic" <> wrote in message
news:106D9FAD-88C9-4BBF-9552-...
> Our group is a small group in a major corporation. To get the team/vendor
> that supports the proxy server to make that type of change would be
> nothing
> short of a miracle.
>
> "Sudheer GN [MSFT]" wrote:
>
>> Hi,
>> We are sorry for the inconvenience and are investigating this issue.
>> In the meanwhile, can you please see if it is possible for you to exclude
>> Windows update URLs from requiring authentication in your proxy server to
>> make this scenario work.
>>
>> --
>> Sudheer GN
>> Microsoft, WU Client
>>
>> This posting is provided "As Is" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>>
>> "Shankomatic" <> wrote in message
>> news:70D553F8-24B7-4BB1-B470-...
>> > We have several boxes that have received the 3.0 Windows Update Client
>> > from
>> > WSUS 3.0. These clients will work fine connecting to Windows Update.
>> > When
>> > using Microsoft Update instead they have a problem with our proxy
>> > servers.
>> > We are using the NetApp Appliances.
>> >
>> > In the past, (also still with Windows Update with the 3.x client) we
>> > are
>> > prompted for a second authenticaion to the proxy server once we click
>> > either
>> > "Express" or "Custom". Now when using the Microsoft Update site it
>> > goes
>> > right to an error screen with the 0x80190197 error. Using a sniffer it
>> > appears the proxy server is requesting authentication but it is never
>> > retruned to the web page.
>> >
>> > It appears somthing has changed between the two releases.

>>
>>
>>



 
Reply With Quote
 
Shankomatic
Guest
Posts: n/a

 
      05-09-2007
Generally 99 times out of 100 we don't need this. But there are cases when
IT support people want to scan a users machine from Microsoft to be sure
everything is installed. It is not a major problem at this time, it would be
nice to have that functionaliaty.

"Sudheer GN [MSFT]" wrote:

> Hi,
> I would like to understand your situation more to see if there are any
> work-arounds.
> If your machines are being managed by WSUS 3.0 servers, what updates are you
> trying to get from MU. Are those updates not available on Windows update
> too?
> You can contact me at my Microsoft email address. To get email address,
> please remove "online." from my email address in this post.
>
> --
> Sudheer GN
> Microsoft, WU Client
>
> This posting is provided "As Is" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
> "Shankomatic" <> wrote in message
> news:106D9FAD-88C9-4BBF-9552-...
> > Our group is a small group in a major corporation. To get the team/vendor
> > that supports the proxy server to make that type of change would be
> > nothing
> > short of a miracle.
> >
> > "Sudheer GN [MSFT]" wrote:
> >
> >> Hi,
> >> We are sorry for the inconvenience and are investigating this issue.
> >> In the meanwhile, can you please see if it is possible for you to exclude
> >> Windows update URLs from requiring authentication in your proxy server to
> >> make this scenario work.
> >>
> >> --
> >> Sudheer GN
> >> Microsoft, WU Client
> >>
> >> This posting is provided "As Is" with no warranties, and confers no
> >> rights.
> >> Use of included script samples are subject to the terms specified at
> >> http://www.microsoft.com/info/cpyright.htm
> >>
> >> "Shankomatic" <> wrote in message
> >> news:70D553F8-24B7-4BB1-B470-...
> >> > We have several boxes that have received the 3.0 Windows Update Client
> >> > from
> >> > WSUS 3.0. These clients will work fine connecting to Windows Update.
> >> > When
> >> > using Microsoft Update instead they have a problem with our proxy
> >> > servers.
> >> > We are using the NetApp Appliances.
> >> >
> >> > In the past, (also still with Windows Update with the 3.x client) we
> >> > are
> >> > prompted for a second authenticaion to the proxy server once we click
> >> > either
> >> > "Express" or "Custom". Now when using the Microsoft Update site it
> >> > goes
> >> > right to an error screen with the 0x80190197 error. Using a sniffer it
> >> > appears the proxy server is requesting authentication but it is never
> >> > retruned to the web page.
> >> >
> >> > It appears somthing has changed between the two releases.
> >>
> >>
> >>

>
>
>

 
Reply With Quote
 
Sudheer GN [MSFT]
Guest
Posts: n/a

 
      06-05-2007
Hi,
Microsoft update web site has been modified to fix this issue.
Can you please let us know if it resolves the issue?

--
Sudheer GN
Microsoft, WU Client


This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Shankomatic" <> wrote in message
news:AE126869-A7B2-460C-9596-...
> Generally 99 times out of 100 we don't need this. But there are cases
> when
> IT support people want to scan a users machine from Microsoft to be sure
> everything is installed. It is not a major problem at this time, it would
> be
> nice to have that functionaliaty.
>
> "Sudheer GN [MSFT]" wrote:
>
>> Hi,
>> I would like to understand your situation more to see if there are any
>> work-arounds.
>> If your machines are being managed by WSUS 3.0 servers, what updates are
>> you
>> trying to get from MU. Are those updates not available on Windows update
>> too?
>> You can contact me at my Microsoft email address. To get email address,
>> please remove "online." from my email address in this post.
>>
>> --
>> Sudheer GN
>> Microsoft, WU Client
>>
>> This posting is provided "As Is" with no warranties, and confers no
>> rights.
>> Use of included script samples are subject to the terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>>
>> "Shankomatic" <> wrote in message
>> news:106D9FAD-88C9-4BBF-9552-...
>> > Our group is a small group in a major corporation. To get the
>> > team/vendor
>> > that supports the proxy server to make that type of change would be
>> > nothing
>> > short of a miracle.
>> >
>> > "Sudheer GN [MSFT]" wrote:
>> >
>> >> Hi,
>> >> We are sorry for the inconvenience and are investigating this issue.
>> >> In the meanwhile, can you please see if it is possible for you to
>> >> exclude
>> >> Windows update URLs from requiring authentication in your proxy server
>> >> to
>> >> make this scenario work.
>> >>
>> >> --
>> >> Sudheer GN
>> >> Microsoft, WU Client
>> >>
>> >> This posting is provided "As Is" with no warranties, and confers no
>> >> rights.
>> >> Use of included script samples are subject to the terms specified at
>> >> http://www.microsoft.com/info/cpyright.htm
>> >>
>> >> "Shankomatic" <> wrote in message
>> >> news:70D553F8-24B7-4BB1-B470-...
>> >> > We have several boxes that have received the 3.0 Windows Update
>> >> > Client
>> >> > from
>> >> > WSUS 3.0. These clients will work fine connecting to Windows
>> >> > Update.
>> >> > When
>> >> > using Microsoft Update instead they have a problem with our proxy
>> >> > servers.
>> >> > We are using the NetApp Appliances.
>> >> >
>> >> > In the past, (also still with Windows Update with the 3.x client) we
>> >> > are
>> >> > prompted for a second authenticaion to the proxy server once we
>> >> > click
>> >> > either
>> >> > "Express" or "Custom". Now when using the Microsoft Update site it
>> >> > goes
>> >> > right to an error screen with the 0x80190197 error. Using a sniffer
>> >> > it
>> >> > appears the proxy server is requesting authentication but it is
>> >> > never
>> >> > retruned to the web page.
>> >> >
>> >> > It appears somthing has changed between the two releases.
>> >>
>> >>
>> >>

>>
>>
>>


--
To resolve the issue, I recommend that you contact Microsoft support by
following the steps in
http://support.microsoft.com/oas/def...spx?gprid=6527

There is no charge for support issues with Windows Update.
It would be great if you can post back to the newsgroup about how the issue
was resolved.

--
Sudheer GN
Microsoft, WU Client

This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Error 0x80190197 while accessing Windows Update Chuck Windows Update 0 11-16-2006 07:10 PM
AutoUpdate error 0x80190197 Pat Willener Windows Update 3 11-12-2004 05:28 PM
GPO ISA Client-> SUS Client error 0x80190197 Ivan Goverdovskiy Windows Update 2 07-05-2004 04:58 AM
Windows Update fails with 0x80190197 - on Windows XP SP2 RC2 updat David Richards Windows Update 1 06-17-2004 03:54 PM
Error Message (0x80190197) Problem Child Windows Update 1 12-08-2003 02:33 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59