Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

We have an unsupported application that relies on IIS however intermittently brings out the website it is integrated with. I have looked at the logs and there is nothing in the logs to indicate what the issue could be as the logs only have GET verbs. I have also looked at the event viewer and there are no error logged in there either.

The application runs off a Windows 2008 server.

Is there a freely available application we can have running in the background that will listen to or is aware of the application running and traps the error when it crashes? The unsupported application is a bespoke implementation for which we don't have code for and the developer is no longer contactable.

share|improve this question
    
getting memory dump on crash is easy, doing anything with it without the code to be able to match memory locations to variable, method, class, function... names is the real problem. Visual studio has an on demand debugger that kicks in when windows detects a crash, but without debugging symbols or source code it's not often very useful. –  ewanm89 Jun 29 '12 at 2:11
    
@ewanm89 - I was afraid that was going to be the case. Any way I can get more output from IIS as I believe a request of some sort that the application is not designed to handled is being made? –  PeanutsMonkey Jun 29 '12 at 2:29
    
What do you mean by "however intermittently brings out the website it is integrated with"? How does it "rely" on IIS, is it a Web App? How is it 'crashing' (stops, or just to busy to answer)? What's actually crashing (the Application, the IIS App Pool, IIS itself? –  Ƭᴇcʜιᴇ007 Jun 29 '12 at 4:50
    
@techie007 - Yes it is an application that has a website within IIS. When it crashes, it stops the website in question. Crashing was probably not the right word to use. It stops the website and the application stops working. The IIS app pool for the application also stops. IIS does not stop itself. The only way to bring the application up again is to start the application pool and website. –  PeanutsMonkey Jul 3 '12 at 19:15
    
Is it running in it's own App Pool, and is that App Pool setup to be a web garden? –  Ƭᴇcʜιᴇ007 Jul 3 '12 at 23:09

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.