We've created a webservice using .Net 2003. We got a report from a consumer of the service and did some work to trace down the problem.

To reproduce, I created a VB desktop client with a single button that invokes the service. The webservice object is created and set to nothing when the button is clicked. The first time the service is invoked, it works, and any immediate usage as well. If the application sits for, say, 10 minutes and the service is invoked again, it does not work. It hangs and finally times out ("The underlying connection was closed: An unexpected error occurred on a receive."). After that happens, the service works again.

Any ideas what might be going wrong? Thanks!

I'm guessing that your timeout value for your session cache is expiring.

I'd do a couple of things....first add code to check for the object and reinitialize it if necessary.

You can also manipulate the timeout value for the caching.

Try this link for info regarding caching.

http://www.codeguru.com/vb_internet/PK102302.html