Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Here's the top of the HTTP 500 error dump I was getting:</p> <blockquote> <p>HTTP Error 500.0 - Internal Server Error</p> <p>Description: The page cannot be displayed because an internal server error has occurred. </p> <p>Error Code: 0x800700c1 </p> <p>Notification: ExecuteRequestHandler </p> <p>Module: IsapiModule </p> <p>Requested URL: <a href="http://localhost/ccnet/default.aspx" rel="nofollow noreferrer">http://localhost/ccnet/default.aspx</a> </p> <p>Physical Path: C:\Program Files (x86)\CruiseControl.NET\webdashboard\default.aspx </p> <p>Logon User: Anonymous </p> <p>Logon Method: Anonymous </p> <p>Handler: AboMapperCustom-80778 </p> <p>Most likely causes: </p> <p>IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. The request is mapped to a managed handler but the .NET Extensibility Feature is not installed. </p> </blockquote> <p>The key to fixing this for me was the Handler line. For some reason the ccnet web application was configured with two handlers vying for control over *.aspx. The real handler, from Thoughtworks, is set in the web.config file. However, when I opened the Handler Mappings section of the IIS7 control panel for the ccnet app I saw that there was another handler named AboMapperCustom-80778 already created and set to look for *.aspx. </p> <p>I right clicked the handler and selected "Remove". After that the ccnet app started running fine for me. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload