Habitually Good

There are many reasons for why the TFS31002 error comes up. Usually its related to permissions configured for accessing TFS, firewalls blocking ports, wrong versions between Team Explorer and TFS, etc. This is what most of the posts tell you when you search for this error on Google, Live, or Yahoo.

We did not have any of these problems but something entirely different. We did a complete clean install of TFS 2005 where we followed the Installation guide to the letter. Installation was successful and without any errors.

Now when we fired up TFS Administration Tool (available at CodePlex) to configure the server, the only time it would let us access the server was if we used localhost as the server name. Even from the same computer on which TFS was installed, it did not allow us to use the IP address of the machine or the name of the server to access the TFS instance.

We of course managed to solve it eventually. The problem was with the security settings of TFS Website in IIS (and the same problem was seen in the SharePoint Services website). For some reason, the IP Address and Domain Name Restrictions settings (found under the Directory Security Tab of the Web Site Properties) had the following settings:

As can be seen, the site is configured to deny acccess to everyone other than localhost. We changed it to look like this:

And everything worked just fine after that.

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.