1

How can the application not be able to lookup localhost?

The remote name could not be resolved: 'localhost'; 

StackTrace;    
      at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
      at System.Net.HttpWebRequest.GetRequestStream()
      at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

the application works a couple of hours and then stops.

Edit I import the service as a webreference and call it using the generated Reference.vb file.

jgauffin
  • 99,844
  • 45
  • 235
  • 372
  • Maybe you should also show, how you call the WebService. It's too hard to guess what you're doing/trying to achieve – Scoregraphic Aug 23 '10 at 07:14

1 Answers1

3

Odd things like this can happen when your app is leaking operating system resources. Like handles or kernel memory pool. Stuff stops working when it exceeds the process quota, error messages aren't always great.

Run Taskmgr.exe, Process tab, View + Select Columns. Tick at least Handles and Threads.

Hans Passant
  • 922,412
  • 146
  • 1,693
  • 2,536
  • Correct. I'm tracking down the memory leak with the help of the following articles: http://blogs.msdn.com/b/jfoscoding/archive/2006/05/03/588974.aspx and http://www.componentfactory.com/blog/2006/07/find-net-memory-leaks/ – jgauffin Aug 25 '10 at 06:45