RE: ProtocolError?

From: Kevin Burton (KevinBurton_at_discussions.microsoft.com)
Date: 12/17/04

Next message: Kevin Burton: "RE: ProtocolError?"

Previous message: Kevin Burton: "The request failed with HTTP status 401: Unauthorized."
Next in thread: Kevin Burton: "RE: ProtocolError?"
Maybe reply: Kevin Burton: "RE: ProtocolError?"
Messages sorted by: [ date ] [ thread ]

Date: Fri, 17 Dec 2004 15:43:02 -0800

If I just do a simple TCP trace I get:

Sending:

POST /IVRService/IVRService.asmx HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 1.1.4322.2032)
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://tempuri.org/IVRRequest"
Content-Length: 508
Expect: 100-continue
Connection: Keep-Alive
Host: localhost:81

<?xml version="1.0" encoding="utf-8"?><soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><IVRRequest
xmlns="http://tempuri.org/"><IVRRequest
xmlns="http://dps.visa.com/PPC"><Request
xsi:type="GetCardProgramParametersRequest"><DNIS>2626412640</DNIS></Request><CorrelationID>89cb6442-e691-4d1f-8290-c1218e2fc836</CorrelationID></IVRRequest></IVRRequest></soap:Body></soap:Envelope>

Receiving:

HTTP/1.1 401 Unauthorized
Content-Length: 1656
Content-Type: text/html
Server: Microsoft-IIS/6.0
WWW-Authenticate: Negotiate
WWW-Authenticate: NTLM
MicrosoftOfficeWebServer: 5.0_Pub
X-Powered-By: ASP.NET
Date: Fri, 17 Dec 2004 23:39:01 GMT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>You are not authorized to view this page</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252">
<STYLE type="text/css">
  BODY { font: 8pt/12pt verdana }
  H1 { font: 13pt/15pt verdana }
  H2 { font: 8pt/12pt verdana }
  A:link { color: red }
  A:visited { color: maroon }
</STYLE>
</HEAD><BODY><TABLE width=500 border=0 cellspacing=10><TR><TD>

<h1>You are not authorized to view this page</h1>
You do not have permission to view this directory or page using the
credentials that you supplied because your Web browser is sending a
WWW-Authenticate header field that the Web server is not configured to accept.
<hr>
<p>Please try the following:</p>
<ul>
<li>Contact the Web site administrator if you believe you should be able to
view this directory or page.</li>
<li>Click the Refresh button to
try again with different credentials.</li>
</ul>
<h2>HTTP Error 401.2 - Unauthorized: Access is denied due to server
configuration.<br>Internet Information Services (IIS)</h2>
<hr>
<p>Technical Information (for support personnel)</p>
<ul>
<li>Go to <a href="http://go.microsoft.com/fwlink/?linkid=8180">Microsoft
Product Support Services</a> and perform a title search for the words
<b>HTTP</b> and <b>401</b>.</li>
<li>Open <b>IIS Help</b>, which is accessible in IIS Manager (inetmgr),
and search for topics titled <b>About Security</b>, <b>Authentication</b>,
and <b>About Custom Error Messages</b>.</li>
</ul>

</TD></TR></TABLE></BODY></HTML>

This response brings up more questions. The message indicates that the
browser is sending WWW-Authenticate header which I am not sure how to turn
off or control.

Kevin

"Dan Rogers" wrote:

> Hi Kevin,
>
> I looked on gotDotNet.com today for a trace utility and didn't find the
> george lindsay files any more. But I did see a number of suitable web
> service extensions that write to the ASP.net trace display. Search on
> "trace".
>
> BTW, you are right that 2003 server is much more secure than Win2K or WinXP
> Pro were when they shipped.
>
> One thought comes to mind - are you sure the URL's weren't changed? Does
> refreshing the proxy on the client code have any effect?
>
> Regards
>
> Dan
> --------------------
> >Thread-Topic: ProtocolError?
> >thread-index: AcTRy2m9o3iLsOplTOChvAxZMy2tyg==
> >X-WBNR-Posting-Host: 198.241.217.3
> >From: =?Utf-8?B?S2V2aW4gQnVydG9u?= <KevinBurton@discussions.microsoft.com>
> >References: <ACA6A231-4739-4F4A-A09A-9046F85238BA@microsoft.com>
> <7BMRo2b0EHA.3152@cpmsftngxa10.phx.gbl>
> >Subject: RE: ProtocolError?
> >Date: Tue, 23 Nov 2004 18:15:05 -0800
> >Lines: 82
> >Message-ID: <8A6337F8-AAB9-4A7E-8EAC-425D3F3AE4E3@microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: cpmsftngxa10.phx.gbl
> microsoft.public.dotnet.framework.aspnet.webservices:26795
> >X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
> >
> >The more I dig into this the more I think it something to do with
> increased
> >security with Windows 2003. But I can't put my finger on it yet. For
> testing
> >the client is running on the same machine as the server (IIS). So the
> client
> >is issuing a call to the web service on the same machine as the web server.
> >
> >I looked in gotdotnet.com and could not find George Lindsay's name. Where
> >was this utility? Wouldn't Microsoft's SOAP trace utility do the same
> thing?
> >I will try that and see what I get.
> >
> >Thank you for your assistance.
> >
> >Kevin
> >
> >"Dan Rogers" wrote:
> >
> >> Hi,
> >>
> >> Is it safe to assume that the server portion of the application was
> >> upgraded, but the client portion was not? Some things to think about -
> on
> >> 2003 Server, the stack is running CLR 1.1, SOAP 1.2, and the ASP.net
> >> service doesn't run as system. All of these could be contributing to
> the
> >> error you are seeing. Is a client that is on the same server
> experiencing
> >> this symptom?
> >>
> >> Have you tried tracing the input (e.g. installing a trace Web Service
> >> Extension such as George Lindsay's trace extension from gotdotnet.com
> and
> >> then viewing the trace.axd output on the server? This would show what
> the
> >> received packet looks like, and reveal whether the IIS server is
> rejecting
> >> the call (unauthorized caller for a vroot that is not allowing anon
> >> access), or if it is getting thru to the service itself.
> >>
> >> Just some things to start with...
> >>
> >> Dan Rogers
> >> Microsoft Corporation
> >> --------------------
> >> >Thread-Topic: ProtocolError?
> >> >thread-index: AcTRolWEeLr6+NRCSf626Q/ExZYrUg==
> >> >X-WBNR-Posting-Host: 198.241.217.3
> >> >From: =?Utf-8?B?S2V2aW4gQnVydG9u?=
> <KevinBurton@discussions.microsoft.com>
> >> >Subject: ProtocolError?
> >> >Date: Tue, 23 Nov 2004 13:21:02 -0800
> >> >Lines: 16
> >> >Message-ID: <ACA6A231-4739-4F4A-A09A-9046F85238BA@microsoft.com>
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain;
> >> > charset="Utf-8"
> >> >Content-Transfer-Encoding: 7bit
> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >Content-Class: urn:content-classes:message
> >> >Importance: normal
> >> >Priority: normal
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> >> >Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >> >Xref: cpmsftngxa10.phx.gbl
> >> microsoft.public.dotnet.framework.aspnet.webservices:26776
> >> >X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
> >> >
> >> >I recently converted to Windows 2003 and I am not sure if this has a
> >> bearing
> >> >on my problem or not. I am getting a WebException now:
> >> >
> >> >WebException: 'The request failed with HTTP status 401: Unauthorized.'
> >> >Status: 'ProtocolError'
> >> > at
> >>
> >System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClien
> >> tMessage message, WebResponse response, Stream responseStream, Boolean
> >> asyncCall)
> >> > at
> System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> >> >methodName, Object[] parameters)
> >> >
> >> >Why is the client not "unauthorized"? Where do you think I should start
> to
> >> >diagnos the problem?
> >> >
> >> >Thank you.
> >> >
> >> >Kevin Burton
> >> >
> >>
> >>
> >
>
>

Next message: Kevin Burton: "RE: ProtocolError?"

Previous message: Kevin Burton: "The request failed with HTTP status 401: Unauthorized."
Next in thread: Kevin Burton: "RE: ProtocolError?"
Maybe reply: Kevin Burton: "RE: ProtocolError?"
Messages sorted by: [ date ] [ thread ]