title: Where can I find a more information for an http 500 internal server error when debugging with visual studio 2015 using iis express?
body: <p>I have created an Asp.Net 5.0, MVC 6 application using the empty template in Visual Studio 2015. I have the debugger set up to launch IIS express and use Chrome as the browser. In my project, I have added a Home controller, and a view for the Index action. I have also added _Layout.cshtml and _ViewStart.cshtml. I have the default code that has been automatically generated. The only changes I have made are to add and use MVC in the ConfigureServices() and Configure() methods in Startup.cs; and to list Microsoft.AspNet.Mvc as a dependency in Project.json file. </p>
  
  <p>When I launch the debugger, nothing is sent to the browser even though I have a title in my index.cshtml page. When I pull up the F12 developer tools and look at the Console tab, it just says</p>
  
  <blockquote>
    <p>Failed to load resource: the server responded with a status of 500
    (Internal Server Error)</p>
  </blockquote>
  
  <p>Where can I find more information about the server error?</p>
  
  <p>The visual studio output window doesn't seem to have anything relevant. Is there a window in visual studio, or a log file in the OS where the actual server error is recorded? It used to be possible to debug the application_error handler in global asax file, which doesn't appear to be available in AspNet 5.0. Is there something similar to application_error?</p>
  
  <p>I have looked at the IIS express trace log file. It says</p>
  
  <blockquote>
    <p>ModuleName httpPlatformHandler </p>
    
    <p>Notification EXECUTE_REQUEST_HANDLER </p>
    
    <p>HttpStatus 500 </p>
    
    <p>HttpReason Internal Server Error </p>
    
    <p>HttpSubStatus 0 </p>
    
    <p>ErrorCode The operation completed successfully.  (0x0) </p>
    
    <p>ConfigExceptionInfo</p>
  </blockquote>
  
  <p>I'm asking this question because I'm interested in learning the process of identifying HTTP 500 server errors when they occur, not just fixing the particular error I have. </p>