Issues with TFS 2008 built-in reports using SQL Server Reporting Services 2008
George Archer and Jim Saunders bring us today’s update about problems with TFS 2008 reports when using SSRS 2008…
- Trevor
We are aware of issues affecting several built-in reports for TFS 2008 if the TFS Data Tier is using SQL Server 2008. Due to changes in SQL Reporting and Analysis Services 2008 the affected reports will fail with errors and not report data when executed. These errors are not indicative of installation failure, or other issues with the installation and functionality of your Team Foundation Server.
At time of writing we are working to provide a full, self-installing update package for these reports that will function properly with Reporting Services 2008. In the meantime however, we have fixed copies of these reports available. Please contact us at Microsoft support ( support.microsoft.com/oas/default.aspx?gprid=10453) and we will be glad to help you out with updated reports. We have also published a KB about this: support.microsoft.com/kb/968905 .
NOTE: Support for this is free (short of any phone charges you may incur, and you can open a web or e-mail based case to avoid those). If you call support, please ask them to view the “MICROSOFT INTERNAL SUPPORT INFORMATION” section of article 968905 for case handling guidelines.
UPDATE – 2009\06\01
We have published localized copies of all the reports fixed to address this issue. The download is available here:
There is mention of a new KB article (969210) on this site. At this time, that article is yet to be published, but it is coming soon. It will be essentially the same as the previous article – 968905 – only with links to the Code Gallery page for the fix.
Following is the list of known reports affected by this issue, listed by team project template along with the errors that may be generated when these reports are executed.
For Projects Based on the "MSF for Agile Software Development - v4.2" Template, the following reports are affected:
"Scenario Details" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'AllScenarios'.
Query (26, 3) The set must have a single hierarchy to be used with the complement operator.
or
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'AllScenarios'.
The function expects a tuple expression for the argument. A tuple set expression was used.
For Projects Based on the "MSF for CMMI Process Improvement - v4.2" Template, the following reports are affected:
"Issues and Blocked Work Items" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'dsWorkItemHistory'.
The function expects a tuple expression for the argument. A tuple set expression was used.
"Requirement Details" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'AllScenarios'.
The function expects a tuple expression for the argument. A tuple set expression was used.
"Requirements Test History and Overview" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'dsWorkItemHistory'.
The function expects a tuple expression for the argument. A tuple set expression was used.
"Triage" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'dsWorkItemHistory'.
The function expects a tuple expression for the argument. A tuple set expression was used.
The following Reports are common to both team project templates:
"Bugs by Priority" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'dsWorkItemHistory'.
The function expects a tuple expression for the argument. A tuple set expression was used
"Bugs Found Without Corresponding Tests" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'dsBugsWithoutTests'.
Query (7, 1) The Extract function was called with hierarchy 'System_Id' that does not exist in the set.
"Exit Criteria" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'dsCurrentWorkItem'.
The expression contains a function that cannot operate on a set with more than 4,294,967,296 tuples
"Issues List" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'dsCurrentWorkItem'.
The expression contains a function that cannot operate on a set with more than 4,294,967,296 tuples
"Load Test Summary" may generate errors similar to the following:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'dsResultParam'. (rsErrorExecutingCommand)
Incorrect syntax near ')'.
"Quality Indicators" may generate errors similar to the following:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'BuildParam'. (rsErrorExecutingCommand)
The function expects a tuple expression for the argument. A tuple set expression was used.
"Related Work Items" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'dsRelatedWorkItems'.
The function expects a tuple expression for the argument. A tuple set expression was used.
"Unplanned Work" may generate errors similar to the following:
An error occurred during client rendering.
An error has occurred during report processing.
Query execution failed for dataset 'dsWorkItemHistory'.
Query (43, 9) Two sets specified in the EXCEPT function have different dimensionality.
Technorati Tags: Team Foundation Server,SQL Server 2008,SQL Server Reporting Services
Comments
Anonymous
March 11, 2009
It would be great if you could give us a rought time frame you have in mind for the public fix for this. Like, if you plan to release it next week, I don't want to waste time going through the (very annoying) MS support channels. If on the other hand you plan to release only in six months, I would of course try to get the hotfix. Also, is there any chance that you release the hotfix just on the web, as a ctp, or beta or something? Most likely it will just be a collection of report files, right? There isn't that much harm one can do with that...Anonymous
March 13, 2009
Mohamed Mahmoud on Teamprise The Dynamic CBM Blog on TFS on 64bit.Did I hear a NO CAN DO? The DeveloperAnonymous
March 30, 2009
Hello Trevor, could you please tell me about when the update package will be available? Is it possible to get the hotfix without asking the support with costs? Thanks MichaelAnonymous
March 30, 2009
Hi Michael, As of now, you have to call us I'm afraid. The install is not difficult, but it is not a simple double-click a package, either. As such, we want to make sure it is done correctly and be there to help if needed. As for support costs, this is a bug so there is no cost to you, short of phone charges if you decide to call. You can even save those by opening a web-based or e-mail case: http://support.microsoft.com/oas/default.aspx?gprid=10453 TrevorAnonymous
March 30, 2009
The comment has been removedAnonymous
March 30, 2009
David, please e-mail me directly via the "email" link in the top-left of this BLOG and I will fix you up ASAP.Anonymous
May 05, 2009
I just called Microsoft Canada support and they said there is nothing in their hotfix database and the only way they are willing to look into it is if I "spend" one of my support calls. I have a number of them ,but it seems ridiculous to have to go through this process. Help!Anonymous
May 05, 2009
java_programmer, As I stated in an earlier comment, there is no charge for the support. One of your support calls is needed to open the issue, but when the case is closed it is returned to you. It is just a formality. TrevorHAnonymous
May 05, 2009
The comment has been removedAnonymous
May 05, 2009
It's a little difficult, yes; I'm sorry. We are working on that. For now everyone should feel free to ping me directly using the "EMAIL" link in the top-left of this page (as noted in the Monday, March 30, 2009 10:11 AM comment above). I've provided the HOTFIX to many customers via that avenue now. TrevorAnonymous
June 02, 2009
  http://code.msdn.microsoft.com/KB969210   As promised some time ago , we have now put thisAnonymous
June 08, 2009
Buenas, si eres el encargado de mantener "vivo" a tu servidor TFS 2008 SP1 y ultimamente no has aplicadoAnonymous
June 08, 2009
Buenas, si eres el encargado de mantener "vivo" a tu servidor TFS 2008 SP1 y ultimamente noAnonymous
June 08, 2009
Buenas, si eres el encargado de mantener "vivo" a tu servidor TFS 2008 SP1 y ultimamente noAnonymous
January 29, 2010
Excelent Post, i resolved this problem thank you for you help