An administrator must log in and run the ProGet.Service.exe executable and reserve the URLs you are using, which will also require a system restart before it takes effect.

Hi Riko Was this issue resolved for you I am facing similar issues with ldap in my company.

Tod's answer gave me something to look for. The IIS 7.5 did not have ISAPI enabled so after doing that the proget site worked as a charm. Definitely something that is missing in the documentation! For further reference see below: To enable ISAPI in the IIS look here: http://www.iis.net/configreference/system.webserver/security/isapicgirestriction at the part Setup The <isapiCgiRestriction> collection is available only after you install the CGI or ISAPI Extensions modules on your IIS 7 server. You cannot install it independent of those features. WINDOWS SERVER 2008 OR WINDOWS SERVER 2008 R2 On the taskbar, click Start, point to Administrative Tools, and then click Server Manager. In the Server Manager hierarchy pane, expand Roles, and then click Web Server (IIS). In the Web Server (IIS) pane, scroll to the Role Services section, and then click Add Role Services. On the Select Role Services page of the Add Role Services Wizard, select CGI or ISAPI Extensions. If the Add role services dialog appears, click Add Required Role Services. (This page appears only if you have not already installed any prerequisite role services on your server.) On the Select Role Services page, click Next. On the Confirm Installation Selections page, click Install. On the Results page, click Close. After doing that i restarted and did not have to any further setup. Loading the site just worked. Inedo should make it much clearer in the documentation that this must be installed in the IIS for proget to work. Just setting the App Pool to Classic is not enough. Thomas

Yes. Things appear to be working now.

what if we try it on a sub website i mean a subdomain? it will work or not?

The second issues I posted, has got fixed when I changed the regional settings to UK and now I am able to set a date in the datepicker control! Please fix this issue in next release guys. The first issue might well be because of the web site settings. Weird thing is the BuildMaster website was in 2.0 but the root websites setting was in 4.0. I ran aspnet_regiis -sn WSVC/ on all the paths and changed everything to 2.0. Did a IISreset but still didnt work ! But after doing that,I uninstalled and reinstalled the BM and it is working now ! Thanks for the help but please investigate the issue and would help if you can publish the corrrect IIS settings in deployment guide.

Hi Alex, After reading your (Alex') reply I concluded that given the fact that I'm using a WinXP machine as a build server, using IIS is no option for me. I had already tried the instructions you gave me. I tried them again an to no avail. I did noticed that although I did provide a valid username and password the service was still being registered under the local service user. That was odd. I guessed the settings for the webserver would be stored in the database (as I couldn't find them in the config file). I added the IntegratedWebServer_Prefixes (which I remembered from the settings screen) and added a binding. -> Works like a charm. However, I still wondered why registering the service as described in the knowledgebase article didn't work. So I took a peek inside bmservice.exe. I found the answer in the construcor of the Arguments class. The knowledgebase article is wrong! The command to execute isn't "bmservice /iws /user=[SERVICE_USER] /password=[SERVICE_USER_PASSWORD] /prefixes=[HOST_NAMES]", it's bmservice /iws /user [SERVICE_USER] /password [SERVICE_USER_PASSWORD] /prefixes [HOST_NAMES]". Also, the hostnames aren't sparated by semicolons, but by regular colons. Maybe you could fix this in the knowledgebase? Thanks, // Vincent.