Ok, this is how I did it. I downloaded the latest documentation for the TFS 2005. Then I read the installation requirements and I follow up the check list but with some things different.
1. After installing MS SQL 2005, I installed the SP2 for MS SQL 2005. There is a requirement for SQL 2005. The documentation indicates that you should install SQL 2005 and then install the Hot Fix AS2005-KB914595-x86-ENU.exe that it's included inside the TFS media. I did not do this. Instead I installed the SP2 for MS SQL 2005. You cannot install this hot fix on a MS SQL 2005 with SP2 on it.
What I found is that this hot fix is included inside SP1 for MS SQL 2005 (http://support.microsoft.com/kb/913090/en-us).
914595 (http://support.microsoft.com/kb/914595/)
FIX: Dimension processing may fail, and you may receive an error message in SQL Server 2005 Analysis Services.
And in a closer look to this article we will find the following sentence:
"Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release."
2. There is another requirement for the .NET Framework 2.0. The documentation indicates that you have to install a Hot Fix. The hot fix KB913393 for Microsoft .NET Framework 2.0 fixes the following issues:
- Ability to Transmit files for fileSize > 2GB
- Fix the memory allocation issue related to HttpResponse.Flush()
I did not do this. Instead, I applied the SP1 for .NET Framework 2.0. What I now is that the SP1 for .NET Framework 2.0 fixes this problem. You will find the information in Microsoft's support article "Problems that are fixed in the .NET Framework 2.0 Service Pack 1" (http://support.microsoft.com/kb/945757).
926776 (http://support.microsoft.com/kb/926776/) A hotfix rollup package is available that resolves the problems that are described in KB articles 913297, 913393, 918995, and 924895
3. Installing the TFS. I got a warning related that the CPU power was not enough for TFS. Current CPU is 1.87Ghz. Requirement is 2.20Ghz. Let's see if this is a really show stopper. We have created only 2 service accounts for TFS installation: TFSService and TFSReports. The TFSSetup account is for installing all the software (required and TFS itself), but this account could be any domain account with Administration role over the server. So my account is an administrator of this machine. In a "nice to have" scenario it would be beneficial to have a TFSSetup account because in that way, if nay modification is needed over the TFS, we won't have to rely in a specific person. Instead of that we will only need the TFSSetup password or someone who knows it.
4. Next step, Install TFS SP1. After installing TFS, I found some articles that describe some workarounds for some issues you may find when trying to install TFS SP1. Before installing SP1 we will need to install a hotfix (KB919156) to avoid database corruption when trying to install TFS SP1 because of concurrent access from users and MS SQL itself when installing this SP1. So, this hotfix is a MUST. You can get that hotfix here: http://support.microsoft.com/kb/919156.
Further reading...
This article http://blogs.msdn.com/dglover/archive/2006/12/18/upgrading-to-team-foundation-server-sp1-workgroup-version-and-a-gotcha.aspx describe the "28002 Error Unknown". This happens when you have all 5 users capped on your TFS Workgroup and you are trying to install the hotfix KB919156.
This post at MSDN forums discuss working on a client with VS2005 with SP1 on a TFS with no SP1 (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1035910&SiteID=1). It should work without problems.... but play it safe and upgrade your TSF to SP1 in proper order.
Enjoy!
