title: How to find cause of 500 Internal Server Error in IIS server logs?
body: <p>A user is getting a 500 error, but I'm unable to reproduce it, so I took a look at the logs.</p>
  
  <p>The logs only tell me when and on what path the 500.0 error happened; is there any way to (retroactively) find the line or stack trace of the error?</p>