Hi,

I'm having problems getting passed the 1st hurdle in installing TFS.

This will be a dual server install - and it's the data tier that's giving me a bit of grief at present.

SQL 2005 (SP1) is installed on Win2003 (SP1). There are two instances of SQL Server on this server, one default instance and one named instance. Obviously, TFS will / should install to the default instance. My problem lies with the fact that the TFS install seems to think that Reporting Services is installed on this default instance. It was - but RS was then removed (I uninstalled it using the SQL Install from add/remove programs and then deleted the RS databases and RSExec roles etc from the SQL Server manually).

Reporting Services is installed on the named instance of SQL Server.

My question is, how does the TFS install determine if Reporting Services is installed or not Does it just check for Reporting Services being installed - whether on a named or default instance Is there anything else that is not removed when Reporting Services is uninstalled.

Thanks

Kevin

Kevin,

I would expect the install to look for the MSI product GUID for report services in order to determine if it has been installed.

I'm not sure I understand you problem. Are you unable to install the data tier Are you receiving some sort of error message during your installation. If so, can you post more detail about your problem

John

The data tier doesn't get further than the pre install checks. I'm using the latest install for TFS and following the install checklist religiously. After launching the setup, I'm selecting "Install Team Foundation Server", followed by "Dual Server Installation" and "Install the Team Foundation Databases Tier ONLY".

After accepting the licence agreement, Setup runs through the pre install/ System Health checks. It is at the end of these checks that I get the message that "Setup has detected one or more conditions that will cause setup to fail." On following the link, the following message is displayed.

Description
SQL Server 2005 Reporting Services service is installed

Workaround / Remedy
SQL Server 2005 Reporting Services service is installed on the data-tier computer. The service should instead be on the application-tier computer. Uninstall SQL Server 2005 Reporting Services service from the data-tier computer and run setup again.

Now I know Reporting Services is installed - but it is not installed for the default instance of SQL Server. It is only installed on the named instance. I'm assuming that TFS is only checking the default instance as that is the only place it can be installed to....unless someone can tell me otherwise....

I'm guessing that my problem may be down to the fact that Reporting Services was installed on the default instance but has since been removed - or is it that TFS will only install the data tier on a server without Reporting Services installed on any instance of SQL Server.

Kevin

The data tier should not have Reporting services installed, regardless of which instance it is installed on. Can you try removing the named instance reporting service

John

John,

I was hoping you wouldn't say this.

The Reporting Services that is installed on the named instance is being used in a live environment. We deliberately installed it to the named instance knowing that TFS had to be installed onto the default instance- which really is a bit of a pain....

Unless someone can come up with an alternative solution it looks as if I'm going to have to install onto a seperate server. More cost!!!

Thanks anyway

Kevin

OK. I think I have a way you can get past your issue. However, there are some concerns that you will need to be aware of.

First, the offical, supported setup scenario for TFS, both app tier and data tier, is that those machines will *only* be used for TFS. To be honest, this is being paranoid, but that's the official tagline.

Second, I'm not sure which license of SQL Server you are using, but if it's the license that comes with TFS, you need to be careful. That license does not allow the SQL Server to be used for any other purposes than TFS. And remember, SQL Server is licensed per machine and CPU, not per instance. So if you're using the TFS license for the data tier, your named instance is not legal if it's being used for non-TFS work. If you are using a full license (like an Enterprise license) for SQL Server, then you are OK.

Finally, in order to get past your pre-req issues on the data tier, you can uninstall the reporting services on your named instance. After successfully installing the data tier, you should then be able to re-install the reporting services on your named instance. Of course, you'd need to backup/restore any reports you have.

Hope this helps.

John

John,

I was thinking the same thing. The licensing issue is not a problem - we have the appropriate SQL Server Standard Licenses - not using the license for SQL that comes with TFS.

Can't understand why the server should "only" be used for TFS. We're only a small outfit and we obviously try to economise where possible on hardware. Having a seperate server for TFS only would be serious overkill from our point of view.

Looks like I'm going to have to spend a weekend trying this out.

Thanks for your help.

Kevin