RE: WebException - ProtocolError from web service on new server

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")
> >
.

Relevant Pages

  • RE: Web Service Implementation Security Question
    ... Server was unable to process ... CompilerParameters parameters, Assembly assembly, Hashtable assemblies) at ... > As for the security problems regarding on using TypedDAtaset in asp.net ... Web Service Implementation Security Question ...
    (microsoft.public.inetserver.iis.security)
  • Re: Permission Errors
    ... >a domain account so that it can be validated on the win2k server machine. ... However I have discovered that I can deploy the web service to the W2K ... domain server and there it runs with no problems, ... for me to decide that the new XP dev machine is up and usable. ...
    (microsoft.public.dotnet.general)
  • Re: Permission Errors
    ... I built the TempConvert3 sample web service on the XP work ... Next I looked at the 2003 server and saw that the local path was ... XP work station. ... >>local workstation, not the server. ...
    (microsoft.public.dotnet.general)
  • Re: Permission Errors
    ... So when we move a webproject to a new server (creating the new virtual ... I built the TempConvert3 sample web service on the XP work ... |>>local workstation, not the server. ... visual studio automatically selected my work station as the ...
    (microsoft.public.dotnet.general)
  • RE: The underlying connection was closed: An unexpected error occurred on a receive
    ... down thru the thread tells me that you know your web service logic is ... the server timeout logic does what it is designed to do ... Each request is allocated to ... you can log the batch and relate it to the caller assigned ID. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)