A user of TFS 2010 recently reported a problem when configuring it after the installed had laid down the bits. Seems they had installed SQL 2008 to a instance named “TFS_BETA”. They then ran the configuration wizard of TFS 2010 and selected the custom configuration. Almost immediately they were presented with this error:
------------------------------------- Team Foundation Server Configuration -------------------------------------
TF255186: The following class could not be found: MSReportServer_Instance. The Windows Management Instrumentation (WMI) namespace is: \\DEV-SER-11\root\Microsoft\SqlServer\ReportServer\TFS_BETA\v10. The instance of SQL Server Reporting Services is: TFS_BETA.
The issue here is that underscore is not a valid character for FQDN’s and as such cause issues with Web applications that use session cookies (such as Reporting Services). We have seen this with VSTSWA as well, and even documented it:
The fix in this case with TFS 2010 and SSRS was to create an instance without an underscore in the name.
What does the SQL Server instance name have to do with the machine name and FQDNs?
I know that this indeed the problem but I point this out because we were hit by this with TFS 2008 when we upgraded SQL 2005 to SQL 2008. Our SQL instance name has an underscore in it, and after upgrading to SQL 2008, TFS could no longer find reporting services. I inferred that this is because WMI url-encodes the instance name, which no longer matches the actual SQL instance name that TFS would have to connect to.
I had to create a new default RS instance and point it to the existing reports database, and this mismatch between the RS name and the database names causes no end of problems.
It sure would be nice if this were prohibited or warned against instead of blindly proceeding and wrecking everything later on, especially when the SQL instance name documentation explicitly says the underscore is allowed: http://msdn.microsoft.com/en-us/library/ms143531.aspx
Thanks for the comments. We have actually seen further discussion on this issue and your inference is correct. We have logged a bug on this for TFS 2010 and will fully investigate the issue before RTM to see what can be done.
MichaelMa on Version Control API changes in TFS 2010 – Part 1 The VSTS Quality Tools Blog on 10-4 Episode
Thanks for clearing it up for me. Incidentally, my snark is directed not at TFS but at the SQL server team!