|
Probably your endpoint Url is wrong, then.
and see
the various services deployed. View the WSDL for the service you are
trying to contact , and verify that the endpoint Url in that WSDL is the same
one your .NET app is using.
In .NET, as with
the Axis client, the Url is a read/write property on the webservice proxy
class.
You will also
get the "unable to connect" if for some reason you have specified an
HTTP proxy, either in the xxx.exe.config file, or in the application
code in your .NET client, and that Http proxy is not available. This is
less common, though. Every once in a while when I forget to start my
proxytrace , I get this error.
-D
From: Suzy Fynes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 02, 2005 11:24 AM To: axis-user@ws.apache.org Subject: RE: failed requests The only detail I have
is that the client is unable to connect to the
service….. The client a .NET
client and the client can connect to other services on the same
server. -----Original
Message----- need more
detail on the failure From: Suzy
Fynes [mailto:[EMAIL PROTECTED] Hi, Can anyone give me some reason as to why a
request to an axis web service would fail given that other services setup in the
same way and on the same site work fine? Other than the typical,
Firewalls, client not been connected to the
internet, invalid data ….. Thanks Suzy |
