Fully Qualified Domain name and TF30162

 

TF30162: Task "SharePointPortal" from Group "Portal" failed

Allright..this is a familiar error message you get when you try to create a team project in TFS 2008 using Visual Studio Team Explorer 2005.There is a hotfix that's available that Brian Harry has blogged about. But I was trying to create a Team project on TFS 2008 using Visual Studio Team Explorer 2008. Why did I get this message?

Usually, I am not able to access my TFS Server with the netbios name. I will be able to access the server  only with the FQDN(Fully Qualified Domain Name).So, the project creation wizard fails when I try to create a project because its unable to resolve the server name. However, I am able to create a  team project from the server by RDPing into the server. So, I figured it was a name resolution issue and it turned out to be right. This also fixes the regproxy issue that wrote about in my last post

I did "the following ..." and I was able to create my team project successfully.

"the following"

From Buck Hodges blog post

"Configuring Team Foundation Server to use fully-qualified domain names

This week the following question came up.  I've seen this come up before, and there are probably forum threads on it, but I figured I'd post it here.  Bill Essary provided the answer to the question.  As always, keep notes on what you do so that you can undo it if necessary.

Question

Is there a way to configure TFS to use fully-qualified domain names (FQDN, e.g., tfsserver.mycompany.com) for TFS, WSS, and Reporting Services?

Answer

1) Run "tfsadminutil activateat <FullyQualifiedDomainName>"

2) Update the following registry key with the FQDN: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\TeamFoundation\ReportServer

3) To force FQDN references in e-mail notifications, set TFSUrlPublic in the TFS root web.config file to http://<FQDN>:8080.

There are a handful of other places where the TFS URL is stored, but they typically wouldn't matter if the goal is to ensure that all public access to the server is done via FQDN.  The ones that are missed govern communication local to the TFS AT (ex: TFS scheduler prodding TFS warehouse).  If you want to get them all, use the SSL-only configuration topic for TFS as a guide.
4) Add the domain to the Intranet Zone or Trusted Sites list in IE for all clients (see KB 303650)

If you are using TFS 2008 with SharePoint 3.0 (or Microsoft Office SharePoint Services 2007), you will need to do the following as well.

After following the steps above with TFS2008 + WSS 3.0 you will observe that when you try to access the team portal using http://FQDN/sites/TeamProjectName you will be automatically redirected to http://NETBIOSNAME/sites/TeamProjectName.

This behavior is by design and is caused by alternate access mapping. In order to avoid this you will have to create a custom alternate access mapping which has the FQDN as the internal URL and as the public URL.

1. Open WSS3.0 Central Administration
2. Click on Operations tab
3. Click on Alternate access mapping
4. Click the Add Internal URLs button
5. In the dropdown select the default website (port 80)
6. Enter the FQDN in the textbox
7. Set the Zone to Custom"