Some of my colleagues in New York have been working on deploying Team Foundation Server as a change management system and they ran into a little error while installing to the QA (UAT) environment.
Log file excerpt:
08/08/07 10:59:33 DDSet_Status: Process returned 2336
08/08/07 10:59:33 DDSet_Status: Found the matching error code for return value '2336' and it is: '28936'
08/08/07 10:59:33 DDSet_Error: 2336
MSI (s) (E8!88) [11:19:18:364]: Product: Microsoft Visual Studio 2005 Team Foundation Server (services) - ENU -- Error 28936.TFServerStatusValidator: the Team Foundation Server ServerStatus Web service failed with 404 HTTP NotFound status. Verify that Internet Information Services, Windows SharePoint Services, and ASP.NET are configured correctly and that ASP. NET v2.0 Web Service Extensions are allowed . For more information on troubleshooting this error, see the Microsoft Help and Support Center.
TFS installed to a point and then through a "28936" error along with a "404 page not found" (I had these symptoms before but a different cause). This occurred when TFS runs some checks after installing the web services. It try's to call http://server:8080/Services/v1.0/ServerStatus.asmx and can't get access to the URL. There was access to http://server:8080/services/ but when you try to access http://server:8080/services/v1.0 we got the 404.
I tried reinstalling ASP.NET, I checked permissions on folders, I tested asp.net and html from the services physical folder (\Program Files\Microsoft Team Foundation Server/Web Services/Services/). I pulled my hair out...
Then I asked the 6 million dollar question, "Has an IIS lockdown been performed"...
As it turns out the default company server build (sadly we buy source code for windows and cripple change things before deployment) contains an ISAPI filter on IIS called "URLScan" that does some sort of URL jiggery pokery that ultimately stops TFS from working.
Remove this, and the error goes away!
This is from memory, I will fix any memory lapses tomorrow...Fixed