Why you should host your TFS on a FQDN, I don't have to explain anymore. If you want to know how to configure this, read the following blog posts very carefully.
- Hosting Reporting Services on a fully qualified domain name (FQDN)
- Hosting SharePoint on a fully qualified domain name (FQDN)
- Hosting Team Foundation Server on a fully qualified domain name (FQDN)
One thing I completely forgot to mention in the last post is the Windows Services of TFS.
These services are very important for Data Warehousing, its reports and for Code Coverage Analysis. If you configured your TFS as I described in the FQDN posts, there is still one thing left.
Check your portal reports and look if the last Warehouse update was recently done. A regular report will contain a sentence like this.
Probably it is out of sync for quiet some time now. Most of the more experienced users of TFS updated their warehouse themselves by using the Warehouse Controller web service, which can be found at http://<SERVER>/Warehouse/v1.0/warehousecontroller.asmx. Just select Run and invoke its method. To get the current status of the web service select GetWareHouseStatus.
Another thing on which you can see your Windows services don't work the way their supposed too, is by starting the Code Coverage Analysis service. When this service is incorrectly configured it will display an error in the event log. The event log window will display an error like below.
Open the configuration files of the TFS Server Scheduler and Code Coverage Analysis. Both can be found at
%Program Files%Microsoft Visual Studio 2005 Team Foundation ServerTFSServerSchedulerTFSServerScheduler.exe.config
%Program Files%Microsoft Visual Studio 2005 Team Foundation ServerCoverAnCoverAn.exe.config
Replace the URL key of the appsettings (Note: BisDomainURL can be replaced too, because it became obsolete in SP1. Now all configurations of TFS uses TFSNameUrl) .
<add key="TFSNameUrl" value="http://tfs.mikeglaser.com:8080" />
Restart your services (Code Coverage Analysis, TFSServerScheduler) and at next interval the Data Warehouse will be updated again. The error shown above will also not occur again.
I apologize for leaving this out in my guides in the first place, but I hope all errors left are now solved as well. My next post will be about setting up TFS to run over SSL and off course about WSS 3.0 the MS way.