Configure TFS V1 to use Reporting Server on WSS 3.0

Since almost everyone wanted to upgrade TFS V1 to use WSS 3.0, Microsoft added two guides to MSDN in which they explain how to update. In this guide I'll explain how to update your Reporting Services to your WSS 3.0 site as well. This will give you the ability to completely shut down the old TFS Web Site. Only I can of emergency or an update you can restart it temporarily again.

To take advantage of one site instead of two you can configure SSRS on the WSS 3.0 site.

  1. Configure SSRS using the Reporting Services Configuration Manager. You can find this by clicking Start, pointing to All Programs, pointing to Microsoft SQL Server 2005 -> Configuration Tools, and clicking Reporting Services Configuration

  2. Create and Configure Virtual Directories
    The report server and Report Manager are ASP.NET applications accessed through URLs. Each URL includes a virtual directory that you specify in the Reporting Services Configuration tool.

    Select Report Server Virtual Directory and click New..

    • For Website Select SharePoint v3
    • For Virtual Directory leave the suggested name
    • Click Ok

      Select Reports Virtual Directory and click New..

    • For Website Select SharePoint v3
    • For Virtual Directory leave the suggested name
    • Click Ok
  3. Change the Web Service Identity
    Select ReportServer application Pool for both Virtual Web Servers

  4. Click Apply and OK
  5. Change the permissions of your SharePoint v3 Web site.
    e.g. C:InetpubwwwrootwssVirtualDirectories81
    NETWORK SERVICE Account(Read & Execute)
  6. To update the registry key for SQL Report Server
    • On the Team Foundation application-tier server, click Start, click Run, type regedit, and then click OK. Registry Editor opens.
    • In Registry Editor, expand HKEY_LOCAL_MACHINE, expand Software, expand Microsoft, expand Visual Studio, expand 8.0, expand Team Foundation, and then click ReportServer.
    • Right-click Key and then click Modify.
    • In the Edit String dialog box, in Value data, change the value to reflect the https address of your Team Foundation application-tier server, and then click OK. For example, if the name of your application-tier server is Contoso1, you would change the value of the data from:




    • Close Registry Editor.
  7. Modify the sample XML below, substituting the entries for [protocol], [WSS Server 3.0], [port] with those of the new WSS 3.0 instance. Typically protocol will refer to http or https, whereas the port number will be the port number you specified for the new Web application during previous steps.

                    <Url>[protocol]://[WSS Server 3.0]:[WSS 3.0 admin port]/ ReportServer/ReportService.asmx
                    <Name> BaseReportsUrl</Name>
                    <Url>[protocol]://[ WSS Server 3.0]:[port]/Reports</Url>

  8. Save your changes to the sample as SSRS_registration.xml making sure that the file can be accessed by the Team Foundation Server application tier computer.
  9. Open a Command Prompt window on the Team Foundation Server application tier computer and execute the following commands (substituting your Team Foundation Server data tier machine name for myDTserver in the TFSReg.exe command here):

    iisreset /stop

    cd “%programfiles% Microsoft Visual Studio 2005 Team Foundation ServerTools”

    TFSReg.exe SRSS_registration.xml myDTserver

    iisreset /start

  10. Confirm that the changes have been made successfully. To do this, follow these steps:

    Check that the service interface changes that you made through running TfsReg.exe are present in the resulting XML.

  11. Team Explorer cache. Team Explorer, which is the add-in within Visual Studio 2005 which provides integration with Team Foundation Server functionality, receives the WSS URL from Team Foundation Server. This value is cached with a default cache timeout of 7200 seconds (two hours). If you are performing this update with sufficient downtime before clients will begin connecting again, then no further action is required. However, if clients will need to connect to the team project portals before the cache time has expired, then you may wish to manually invalidate the cache. To do so, each client should close all open instances of Visual Studio 2005 then delete the following folder: ““%USERPROFILE%Local SettingsApplication DataMicrosoftTeam Foundation1.0”

Again you're just a few clicks a way for creating a single web site which contains WSS 3.0 and Reporting Services.


2 thoughts on “Configure TFS V1 to use Reporting Server on WSS 3.0

  1. I think that I will need to try this with my current deployment. Not just because it is new, but because I was talking about it today with John, our Reporting Services guru. He wants to try these capabilities with our Sharepoint 2007 deployment. I am glad to hear that it can be done with TFS as well.

    I am still unhappy with the integration with Sharepoint in TFS as all I want to be able to do is create sub-sites (full explanation on my blog) which would require me not only to create a new web services for SHarepoint, but to write and deploy a custom project creation wizard part to replace the default one in TFS.

    This is something I may have to do for my current Aggreko TFS deployment. 🙂


  2. Martin,

    I'm still looking for a solution where you can enable the Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies.

    When you enable this is WSS 3.0 the Team Explorer can't find any reports anymore. I'm thinking about rewriting the Reporting Services web service and use url redirecting, so the Team Explorer will display all your reports.

    This way your reports will be fully integrated in SharePoint instead of Reporting Services.

    Keep me posted.



Leave a Reply

Your email address will not be published. Required fields are marked *