RE: WebException - ProtocolError from web service on new server
- From: "MattM" <MattM@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 14 Apr 2005 16:18:03 -0700
I started looking at the IIS logs and discovered a difference between the
test server log (which works) and the live sever (which fails).
A successful return from the web service via the WinApp looks like:
cs-method sc-status sc-substatus
POST 401 2
POST 200 0
But the failed attempts look like this:
cs-method sc-status sc-substatus
POST 302 0
I'm still hoping someone can throw out some ideas.
"MattM" wrote:
> More information on this problem. I tried to call the web service using an
> invalid URL I get the same error. I was expecting to get a 404 or not found
> error since the URL didn't exist (ex
> http:\\myserver\webservice\thisisinvalid.asmx). I think this means that the
> Windows 2003 server is configured incorrectly. If I try to use an invalid
> port (ex http:\\myserver:81\webservice\valid.asmx) I get the error saying the
> connection was closed and unable to connect to remote server.
>
> Does anyone know of a server setting that may prevent web services from
> functioning? We don't have any problems with our web sites (both ASP.Net and
> ASP sites).
>
> "MattM" wrote:
>
> > Some additional notes on this topic.
> >
> > The message for the system.net.webException is blank. This is why I can't
> > figure out what is wrong.
> >
> > The WSDL appears to work file when browsing the web service using the URL in
> > IE. I even enabled remote testing on the page and was able to successfully
> > test. Trying to call the web service in my VB Windows application fails as
> > indicated.
> >
> > I do not think it's a proxy issue. I've looked at the proxy settings and the
> > IP for the server appears on the bypass list just like my test server (both
> > are internal servers).
> >
> > "MattM" wrote:
> >
> > > I have a simple "hello world" web service that works fine on 2 out of 3
> > > servers. The problem server will only return a system.net.webexception with a
> > > status of "ProtocolError". I realize this must be a problem with permissions
> > > or something like that but the error is so unhelpful that I'm just guessing
> > > where to even begin looking.
> > >
> > > Can anyone give more details on what "ProtocolError" means so I can try and
> > > figure this out?
> > >
> > > Here's how I'm calling my web service which works locally, and on the test
> > > server, but not our production server:
> > >
> > > Dim oWs As New ws.Test
> > > oWs.Url = cmbUrl.SelectedItem.ToString
> > > oWs.Credentials = System.Net.CredentialCache.DefaultCredentials
> > > lstMsgs.Items.Add("about to call ws")
> > > lstMsgs.Items.Add(oWs.TestHelloWorld)
> > > lstMsgs.Items.Add("finish call to ws")
> > >
.
- References:
- Prev by Date: Advice needed on Servere side WS, which is activated by SQL Trigge
- Next by Date: Re: request exceeds the limit
- Previous by thread: RE: WebException - ProtocolError from web service on new server
- Next by thread: Newbie question
- Index(es):
Relevant Pages
|
Loading