Hi,

I'm working on an install of TFS on a an exisiting server where we've moved the default web site (along with Reporting Services and SharePoint) away from port 80. Is there an easy way to get the TFS install to work in this situation, or would it be simpler to move these sites back to port 80 for the install then reconfigure everything afterwards? I've found some references on the internet to doing the latter, although these were mostly on the personal weblogs of sysadmins - so far I've not found any "official" documentation or guidance on doing any of this.

Any pointers or advice gratefully received. I'll be experiementing in the meantime so if I come up with a working solution I'll post it in this thread.

Thanks,

Sam Pearson

It's not officially supported AFAIK, but Bill Essary told me (thanks Bill!) the steps you would need to go through for this.

1. Copy all the setup files off the install media to a local folder (we need to edit one of the files for this)
2. In the on-disk copy, edit the msiproperty.ini file
3. One of the properties in that file is VSTF_WSSSQL_PORT=80 - this is the port that WSS (Sharepoint) and SQL (SQL Reporting Services) are accessible at. Change this to the correct port that those 2 can now be found at.

James,

Thanks for the tip - I'd been looking at that variable myself and thinking along similar lines. However, having tried this, the installation still failed with the following error:

Error 28804. Setup cannot connect to the SQL Server 2005 Reporting Services report server. Verify that SQL Server 2005 Reporting Services is installed and running, and that you have sufficient privilages to access it. For more information, see the setup logs.

Viewing the VSMsiLog2AC1.txt I can see the same error I was seeing before in response to the call to createeds.exe - the URL in the /install parameter is still set as http://SERVER/ReportServer/ReportService.asmx.

I have copied the contents of the install CD onto a machine and editied msiproperties.ini in the at, dt and atdt subdirectories to reflect the non-standard port. I am running the install over the network from this PC via a UNC share rather than a mapped drive. I am logged into the server as domain user TFSSetup, who is a local admin. I'm using domain users TFSService and TFSReports as per the install instructions, neither of which are local admins on the server but both of which can log on locally and as a service. I can open a browser and browse to http://SERVER:8000/Reports and view the Report Server page fine. I'm afraid I neglected to check http://server:8000 before starting but following the abortive install there is a sharepoint site here with an entry posted by TFSService so it looks like the TFS install is talking with SharePoint fine.

The only other thing that I can think of that may be affecting the install is the Service account and authentication mode used for SQL 2005. The service account is not Local System but a domain account, and the authentication mode is set to mixed. This is a requirement for us as the SQL server is not going to be exclusively used for TFS.

Any further pointers would be appreciated. My next test will be to temporarily move the defaul website onto port 80 for the sharepoint and TFS installs, then try moving it afterwards and reconfiguring TFS, which I believe should be possible based on some of the research I've done.

Thanks,

Sam

I've just discovered this KB article:

http://support.microsoft.com/kb/921311/en-us

Which says that as well as the VSTF_WSSSQL_PORT variable you also need to adjust the VSTF_ROSETTA_SERVER variable to [ComputerName]:<port_number>, so that's what I'm going to do next.

I will post an update to this thread.

Sam