Hi, I have a site on shared hosting (Windows 2003 Server; IIS6) running Asp.Net 2.0 and written in VB.Net. This site has been active for ~ 2 years, with frequent minor updates. For the last 3 months, about once per week, it shows "Service Unavailable". Recycling the App. Pool takes care of it, but it occurs again in 2 days to 2 weeks. My host is, unfortunately, unwilling to help other than to tell me that it is my code that is the problem. I have read the MS support artice that seems most relevant to this (http://support.microsoft.com/kb/842493), and it appears to me that this cannot be a code issue. I have read other forums however that both support and refute this assertion. The bottom line is that my client is, understandably, very upset (as the latest interruption caused the site to be down for 4 days at the end of last week), so I really need a definitive answer as to who is at fault and where the problem lies so that I can fix it. I have not been offered access to log files, so I do not what they contain (not that I could decipher them anyway). The web site runs a basic ecomm store and gets ~ 100 hits per day. It has been suggested that memory is an issue, and the cart on the site is a datagrid stored in a session, so that's plausible. However, I have a hard time buying that I'm crashing a site getting only 100 hits / day without a problem server-side at least contributing. Specifically, I am wondering the following: Could .Net code cause this (esp. given the low hit count)? If it could be code-related, is there anything I can do to let me know which page / code block is the culprit? What should I request from my host to get to the bottom of this? What have I missed??? Any thoughts / help is greatly appreciated. Thanks in advance.

Hi, Since this issue is more related to IIS 7, I would suggest you initate a new thread in our official IIS forum. The community members and professionals are familiar to IIS configuration. http://forums.iis.net/ Thank you for your understanding. Regards, Wilson JiaThis posting is provided "AS IS" with no warranties, and confers no rights.

Hi , Please follow wilson suggestiong of posting your question in IIS forum Additionaly i would suggest few tools for logging a) Use IIS debug diagnostic logging to debug memory and other process informaiton which should give you more insight about the problem. http://support.microsoft.com/default.aspx/kb/919790?p=1

Hi, Thanks for the advice - I have posted in the IIS forum as well. However any feedback would still be appreciated, as I'm not sure this is an IIS problem (vs. e.g. an Asp.Net problem). I also appreciate the advice re: the debuggers, but it's a shared environment, so I don't have access to install them. Is there something specific I should tell my host to do, or ask them for? Thanks again.

Hi , Yes, you need to instruct your client to install the debuggers and run for specific time ( ideally the time where you can reproduce the problem , because the log file would be pretty big ( upto gigs ) ) One of the advantage of the IIS debug logging is its graphing and reporting the faulting module. It gives you clear understanding of the stack back trace along with the each module memory consumption.