(cross-post added to BITS)
"Walter" <> wrote in message
news:4002EBF8-6D3A-4A66-A7CA-...
> Hi,
>
> I've looked at some of the suggestions for resolving error "The website has
> encountered a problem and cannot display the page you are trying to view"
> with error 0x80190193. In my scenario I'm using Windows 2003 Enterprise
> Server - 64-bit edition.
> Unfortunately, some of the solutions e.g.
> installing an updated version of bits doesn't work (since I cannot seem to
> find a 64-bit version).
I think you may be misinterpreting something. BITS can be a cause
of the symptom. In order to use it you must enable anonymous connections
through your proxy server to the Microsoft sites. Alternatively, just use
the Windows Update Catalog or download updates manually, as those
would not require anonymous connections.
<title>You experience problems when you access the Windows Update
Version 5 or Version 6 Web site through a server that is running ISA Server</title>
http://support.microsoft.com/kb/885819
<quote>
The problem that is described in Scenario 2 occurs when the Windows
Update client authenticates with NULL credentials to the proxy server.
If the proxy server does not give access to the requested site for the NULL
logon, the request may be denied and Windows Update may fail.
</quote>
Or are you saying that you think there is a version of BITS which can avoid that problem?
Perhaps someone on the BITS NG can clarify? (Cross-post initiated.)
> I've even tried proxycfg and that doesn't seem to help either.
>
> Has anyone encountered this error on a 64-bit version and what have you done
> to troubleshoot? I'm also behind a proxy server in which all traffic is
> directed to port 8080.
The best place to troubleshoot would be at the proxy server
which is issuing the HTTP 403 response. E.g. find out what site
is being requested and make sure that that is one of the ones which
is allowed to pass through.
Alternatively, try using Fiddler2 to capture more detail about the request
which leads to that response. Etc.
BTW I don't know what would show in the WindowsUpdate.log for this
symptom but there may also be sufficient information there which you could
look at and thus avoid trying to get any other supplementary diagnostics.
>
> Thanks,
>
> Walter ...
Good luck
Robert Aldwinckle
---