 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / Web Services / February 2005Help!- Socket error in Web Service when network is disabled.
All the components have been developed using .NET C#. I have a web service installed on a windows 2003 server machine. I have a client application running from 10 different machines and calling that webservice. On a couple of machine(Windows 2003) when the network is disabled, then when creating an instance of the Web service it gives the following exception: System.Net.Sockets.SocketException Message - The requested name is valid, but no data of the requested type was found. On the other machines under the same scenario no exception comes. The exception of WebException is caught when actually calling a method on that Web Service. Help would be deeply appreciated. Thanks I am not sure that I am understanding the problem entirely, but it seems you are getting these exceptions when your network has been disabled? Is the network disabled on the Server, or on the Client machines? Are there multiple Servers? If there are multiple servers, and you are using load balancing , make sure your load balancing config's apps's are not pointing to fixed machine names. because if one goes down, you will get errors. > All the components have been developed using .NET C#. > [quoted text clipped - 12 lines] > > Help would be deeply appreciated. Thanks Hi Malroy, The problem comes when I disable the network on t he client machine. There is no load balancing implemented and we are talking about a single Web Servioce installed on a single server. We have written code to catch WebException when trying to call a method on that webservice and the network is down... but the above mentioned exception(System.Net.Sockets.SocketException) occurs at the very time of creating an instance of the Web Service..i.e. before calling any method on it. And the funny thing is that the same client application is installed on multiple machines but the problem comes only on a few machines. Thanks for trying to help. Awaiting your reply. > I am not sure that I am understanding the problem entirely, but it seems you > are getting these exceptions when your network has been disabled? Is the [quoted text clipped - 19 lines] > > > > Help would be deeply appreciated. Thanks I am having a similar problem on Windows 2003 servers when they are disconnected from the network. In my scenario I am using process-hosted remoting to host objects on the same server as the client (all the same Windows 2003 machine). When I use Activator.GetObject to get the remoting object and then call a method on it, I get the same socket exception, even though it is all on the same server and I am actually using the loopback IP address (127.0.0.1) in the URI. And also, it only seems to appear on some disconnected Windows 2003 servers, but it sounds like it could have the same root cause as your problem. If anyone knows anything, please let me know! Thanks! Dave Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.