When I run a no-touch-deployed windows form app under .net framework 1.1 on XP pro, calling a web service (on the same win 2003 server site), it works great, but if I let it sit for 5 or 10 minutes and call the web service again, it times out. The next call to the web service works fine.
This reminds me of a problem (that Microsoft Developer Support could not help me with) where an http request after some idle time would give the exception "Cannot access a disposed object named System.Net.TlsStream". The next request would always work, so I worked around it by catching that particular exception and issuing an immediate retry. The problem with the web service call exception "the operation has timed- out" is that I don't get it right away. I tried looking for something proactive I could check before the call, but I couldn't find anything. The problem demonstrates itself in a simple model where both the app and the web service are in the localhost default site, using the sample hello world web service method. The interesting part is that if the app is started locally (not using IEExec) this is not a problem. No-touch deployment is a great thing, but using web services will be important since the app has no privileges on the client machine. Has anybody seen this, and if so does anyone know how to approach it? Thanks! Charlie Butts Pathology Associates Medical Laboratories Spokane, WA [EMAIL PROTECTED] =================================== This list is hosted by DevelopMentorŪ http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
