This page documents difficults encountered during the installation procedure. Each section is scoped by deployment scenario.
Dual-server Deployment, Windows 2008 and SQL Server 2008
The second scenario attempted by the group is an AD domain-based deployment onto separate application tier and data tier servers. As per TFS installation guide, the servers were prepared with
- Domain controller - ICELAND
- Windows Server 2003, SP2
- domain icelava.local (NetBIOS name ICELAVA)
- App-tier - TFS2008APP
- Windows Server 2008 x86, SP1
- IIS 7.0
- SQL Server 2008
- Data-tier - TFS2008DATA
- Windows Server 2008 x64, SP1
- SQL Server 2008
- Database engine
- Analysis Services
The TFS 2008 installation package was from the MSDN TFS trial DVD slipstreamed with TFS 2008 SP1. The merging instructions are found in the TFS installation guide, "How to: Integrate the Installation of Team Foundation Server and Service Pack 1" section.
The first activity session was started deliberately with the database server in a blank slate; not everybody has installation experience of SQL Server 2008 yet, thus the importance to motion through the installation procedure. Unsurprisingly, a variety of subtle differences in Windows 2008/SQL Server 2008 brought forth a number of obstacles that were largely non-concerns in Windows 2003/SQL Server 2005. Below are some issues to note for such a setup.
MS Installer 4.5
SQL Server 2008 requires Windows to be updated with MS Installer 4.5.
Server collation
In the How to: Install SQL Server 2008 in a Dual-Server Deployment section of the TFS installation guide, the mention about Collation Setting Requirements for Team Foundation Server is missing. It is only documented in the How to: Install SQL Server 2005 in a Dual-Server Deployment section. This specific collation setting still very much applies to SQL Server 2008; it cannot be using the default collation Latin1_General_CI_AI. Make sure to use the Latin1_General_CI_AS collation, which is "hidden" in an optional tab in the new installation dialog wizard. The SQL Server 2005 installation wizard used to make collation setting an explicit step.
Windows Firewall and TCP ports
By default, SQL Server 2008 only installs with Shared Memory as the accessible protocol. In order for the app-tier server communicate properly with the data-tier database services, TCP/IP must be enabled for the SQL Server Network Configuration using the Sql Server Configuration Manager.
Additionally, Windows Firewall is activated natively in Windows 2008. It must be configured to allow the following port Exceptions
- SQL Server , TCP 1433
- SQL Browser, TCP 1434
- SQL Server Analysis Services, TCP 2383
SQL Server Analysis Services instance was unavailable
Despite the above settings, the Platform Scan's System Health Check rated the environment unsuitable for proceeding with installing TFS.
The System Health Check has detected a problem that will cause Setup to fail.
Description
The SQL Server Analysis Services instance was unavailable for querying instance information.
Workaround / Remedy
The SQL Server Analysis Services instance was unavailable for querying instance information. Please check to make sure the instance is running and available.
More information
For additional information and help please refer to: http://go.microsoft.com/fwlink/?LinkId=79226
The cause of this problem is actually based on a warning message in the same log file. It suggested that WMI is not accessible on the data-tier server. Therefore on top of the above TCP port exceptions stated above, Windows Firewall needs to allow Exception to Windows Management Instrumentation (WMI) so that the app-tier server may freely communicate and query the WMI interface of the data-tier server.