title: ASP.NET Web Services troubleshooting?
body: <p>Working with one of our partners, we have developed now two separate sets of web services for their use. The first one was a simple "post to an https URL" style web service, which we facilitated by building a web page in ASP.NET that inspected the arguments in the URL, and then acted accordingly. This "web service" (if you can call it that) has been very stable.</p>
  
  <p>At some point, the partner asked us to begin using SOAP based web services.  At their request, we built them a new set of web services largely based on the previous objects, reimplemented as an actual "Web Service". This web service has not been very stable: around once a week, Nagios will alert us that our web service is not responding - and a quick iisreset does the trick.  </p>
  
  <p>Analyzing the log output and working in a debugger has not led us to anything concrete.  The volume on this new web service is actually much lower than the HTTP web service.  I think this could be a code problem or a platform problem, or of course something in between.  </p>
  
  <p>We've tried, with little improvement:</p>
  
  <ul>
  <li>To duplicate the behavior in the lab </li>
  <li>Debugging in the Visual Studio debugger</li>
  <li>Tinkering with IIS options to give it its own application pool</li>
  </ul>
  
  <p>My question, what are the next steps for troubleshooting?</p>
  
  <p>Environment:
  Windows Server 2003 Standard Edition R2 Service Pack 2 32 bit, Visual Studio 2005, MS SQL 2005, .NET Framework 2.0.50727</p>