Troubleshooting Team Foundation Reporting
This topic lists the following common issues that occur when you work with Team Foundation Reporting:
Received an Error Message When You Ran a Report
Data is Missing from the Report
Running a Report Takes a Long Time
No Permission to Access a Report
If you cannot resolve a problem after reviewing these tips and those in the individual error message Help topic, see the Microsoft Technical Forums for Visual Studio Team System (https://go.microsoft.com/fwlink/?LinkId=54490). These forums provide searchable threads on a variety of troubleshooting topics and are monitored to provide quick responses to your questions.
Received an Error Message When You Ran a Report
When you run a report, you may receive an error message such as the following:
An error has occurred during report processing. (rsProcessingAborted).
Query execution failed for data set 'dsPriorityParam'. (rsErrorExecutingCommand) For more information about this error, locate the report server on the local server computer, or enable remote errors.
These error messages indicate that there is a problem with the data moving from the operational stores to the data warehouse and that the report may be missing information.
If the error indicates that there was a problem connecting to the data source, make sure that the data sources are configured correctly. See "Changing the Team Foundation Server Reporting Service Account" in How to: Assign a New Account to a Team Foundation Server Service for more information.
Because the cause of these errors is usually located in the data warehouse programs instead of in the reporting program itself, you must follow the troubleshooting procedures that are described in Troubleshooting the Data Warehouse.
Data is Missing from the Report
If you suspect that a report is missing information, you can confirm the omission using the following procedures.
To confirm that data is missing
Make one or more of the following changes:
Check in a changed file to source control.
Update a work item.
Publish a test result.
Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
In the Server Type list, in the Connect to Server dialog box, select Database Engine, and then click Connect.
Expand the Databases node, expand the servernameTFSWarehouse node, and then expand the Tables node.
Confirm that the change appears in the appropriate tables:
If you check in a changed file to source control, right-click the dbo.Changeset and dbo.Code Churn tables, click Open Table, and confirm that the change appears.
If you update a work item, right-click the dbo.Current Work Item and dbo.Work Item History tables, click Open Table, and confirm that the change appears.
If you publish a test result, right-click the dbo.Test Result table, click Open Table, and confirm that the change appears.
If you confirm that data is missing from the report because of a problem in the data warehouse, follow the troubleshooting procedures that are described in Troubleshooting the Data Warehouse.
Running a Report Takes a Long Time
The first time that you run or view a pre-built report, it may take Team Foundation a long time (tens of minutes) to assemble and process the data in the data warehouse. Wait for the processing to finish. If the report does not finish processing and appear after 30 minutes, contact your Team Foundation administrator.
No Permission to Access a Report
If you receive an error message that states that you do not have permission to access a report, contact your Team Foundation administrator or the administrator for the SQL Server Reporting Services server. For more information about the permissions that you need on your user account to access reports, see Team Foundation Server Contributor Permissions.
See Also
Concepts
Data Sources for Team Foundation Server Reporting
Other Resources
Using Reporting and Metrics for Team System
Troubleshooting Reporting Services