TFS: How to fix the Red X of Death on the Report Folder in Team Explorer
Awhile back, I upgraded our Team Foundation Server to 2008 SP1 and our SQL 2005 server to 2008. It took a bit of finagling to get everything working right. Google was my friend and I was able to solve all but one nagging issue. Have you ever seen the little red “x” on your Report folder in Team Explorer? He and I have been fighting for a few weeks.
I came across several forum posts that all seemed logical. Here are the steps I took to get it fixed:
- Configure registry to use FQDN -> Edit each of the following registry keys accordingly:
- HKLM\Software\Microsoft\VisualStudio\9.0\TeamFoundation\ReportServer\443\Sites\BaseReportsUrl
- HKLM\Software\Microsoft\VisualStudio\9.0\TeamFoundation\ReportServer\443\<ProjectName>\ReportsService
- HKLM\Software\Microsoft\VisualStudio\9.0\TeamFoundation\ReportServer\80\Sites\BaseReportsUrl
- HKLM\Software\Microsoft\VisualStudio\9.0\TeamFoundation\ReportServer\80\<ProjectName>\ReportsService
- Configure connections in TFS
- Option 1:
- Browse to C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools
- Run TfsAdminUtil.exe configureconnections /view
- Ensure that ReportsUri is set to http://<ReportServerUrl>/Reports (or https for SSL)
SET: TfsAdminUtil.exe configureconnections /reportsuri:http://<ReportServerUrl>/Reports - Ensure that ReportServerUri is set to http://<ReportServerUrl>/ReportServer/ReportService.asmx (or https for SSL)
SET: TfsAdminUtil.exe configureconnections /reportserveruri:http://<ReportServerUrl>/ReportServer/ReportService.asmx
- Option 2 (easier IMHO):
- Use SQL Management Studio to connect to your TFS SQL Server
- Run this query against the TfsIntegration database: SELECT * FROM dbo.tbl_service_interface
- Look for 2 records that look like these and make sure they’re accurate:
ReportsService http://<ReportServerUrl>/ReportServer/ReportService.asmx
BaseReportsUrl http://<ReportServerUrl>/Reports
- Option 1:
At this point, I thought I was done. The red x stared smugly into my eyes. Alright, it must be server cache. Reboot the server and restart VS. He’s still there. He’s laughing at me at this point. I finally realized that the properties of that folder (in Team Explorer) still had the wrong url. The cache was client side. DIRTY!
You can clear you client cache like this:
- Close Visual Studio
- Browse to c:\users\%username%\appdata\local\microsoft\team foundation\2.0
- Delete the cache folder
Now launch Visual Studio and rejoice!






