Well, I finally managed to install it...   but it wasn't easy....

The server I installed has W2K3 with a couple of instances of SQL 2000, IIS and a lot of other crap and old things no longer used. So, my first task was to make some cleanup.

I uninstalled almost everything, installed W2K3 SP1, Windows Update, Reboot, Defrag all disks.

After reading all installation documentation, I begin Team Foundation installation. First I installed SQL 2005 Standard Edition, then Sharepoint Services using the silent setup command found in the documentation, and all went smooth.

Finally, I started the Team Foundation setup, but...   there are allways a but....   here is where things go wrong. The setup failed and showed a little dialog saying something about a command named "ConfigureNTLM.exe" that failed execution. Damm!

Well, to make a long story short, after searching on the NET and found nothing related with this specific error applied to my conditions (there is a possibility that this error also accurs if port 8080 is in use before Team Foundation Setup, because the web site that is configured try to use this port), and then I uninstalled and reinstalled all a couple of times with the same result.

So, I found myself reading all installation logs to try to understand what happened....  and I found the culprit!

The setup try to configure the Team Foundation site to use NTLM as authentication, and also tries to configure the compression filters for the site. In a clean IIS environment this wouldn't be a problem, but in this particulary server (for whatever reason I don't know or can explain) the default compression filters aren't present. I think that the most likely cause for something as bizarre as this happens is metabase corruption, but I'm open to suggestions/comments here...

The solution?  There are two solutions for this.

The easy one: Uninstall IIS (and Sharepoint, and SQL, and Reporting Services, etc, etc)

The risky one: Touching the metabase by hand to manually add the missing filter configuration.

Well, I give a shot at the risky solution, and it worked like a charm!

After that, setup went smooth....  and I go home after another fun day...

The story here: if you have the "32000 - ConfigureNTLM" error, you can be sure it's IIS related. Check the 8080 port is not in use, and if not....   probably is better to reinstall the whole thing. The documentation states clearly that a clean server is a prerequisite....  so it must be true, don't you think?

Best Regards,

No Comments