I installed CruiseControl.net ( from the CruiseControl.NET-1.4-Setup.exe installer ) on my Vista x64 development machine. The server portion is running fine; however, the webdashboard piece is not working.
The first error message I saw when I tried to pull up http://localhost/ccnet squawked about not being able to run in integrated pipeline mode. Easily fixed. I opened up the IIS7 admin panel and changed the ccnet application to use the "Classic .NET App Pool" application pool.
However, I am now getting a persistent HTTP Error 500 when I try to connect. I set the NTFS permissions on the webdashboard folder wide open in the hopes that maybe it was a file permissions issue. No joy.
After a bit of digging and trial and error I found a set of steps which seems to fix the problem. I'll post a follow up answer right after this, but wanted to share this out on stackoverflow in the hopes that it might aid someone else down the line. Also, if there's a better configuration solution I'm all ears 🙂
Best Answer
Here's the top of the HTTP 500 error dump I was getting:
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.
I right clicked the handler and selected "Remove". After that the ccnet app started running fine for me.