|
|
Scrum for Team System - v1.x Support
Started by Holdom at 11-24-2007 1:39 AM. Topic has 5 replies.
  
|
|
Sort Posts:
|
|
|
|
 11-24-2007, 1:39 AM
|
Holdom
Joined on 11-24-2007
Posts 7
|
Sprint burndown chart returns exceptions
|
|
|
|
|
Hello,
We are having problems with viewing Sprint Burndown chart for our new iteration, 'Iteration 4'. At the same time we can still view the burndown charts from previous iterations. Actually, none of the charts for this new iteration is working. We have entered this iteration for about a week so there are data in the data warehouse. The errors returned when we try to view the chart are as follows:
. An error has occurred during report processing.
. Query execution failed for data set 'ChartData'.
. The statement terminated. The maximum recursion 100 has been exhausted before statement completion.
Does anyone have a clue about what have caused these errors? I have tried updating the datawarehouse but it won't help at all.
thanks,
Holdom
|
|
|
|
|
Report
|
|
|
|
|
11-27-2007, 3:56 PM
|
Stuart Preston
Joined on 03-25-2006
Posts 178
|
Re: Sprint burndown chart returns exceptions
|
|
|
|
|
|
What version of Scrum for Team System are you running?
|
|
|
|
|
Report
|
|
|
|
|
11-27-2007, 7:18 PM
|
Holdom
Joined on 11-24-2007
Posts 7
|
Re: Sprint burndown chart returns exceptions
|
|
|
|
|
|
Hi Stuart,
v1.2.13591.002 is the version we are using.
thanks,
Holdom
|
|
|
|
|
Report
|
|
|
|
|
12-12-2007, 10:56 PM
|
Stuart Preston
Joined on 03-25-2006
Posts 178
|
Re: Sprint burndown chart returns exceptions
|
|
|
|
|
|
I've been looking into the possibilities that one of the T-SQL common table expressions (CTEs) in the report is hitting the default limit of 100 recursions.
Do you have a large number of sprints or deleted Sprint Backlog Items in your project?
|
|
|
|
|
Report
|
|
|
|
|
04-03-2008, 5:58 AM
|
harygoldie
Joined on 02-25-2008
Posts 2
|
Re: Sprint burndown chart returns exceptions
|
|
|
|
|
|
- I am getting this error while using Sprint Burn Down chart report.
- An
error has occurred during report processing. (rsProcessingAborted)
- Query
execution failed for data set 'ChartData'. (rsErrorExecutingCommand)
- For
more information about this error navigate to the report server on the local
server machine, or enable remote errors
- We are using version 1.2.13591.002 of the software.
I have two projects created using the template. On one project I have four sprints and all is working very well. The problem project is newly created and has 36 sprint backlog items which are linked to 8 product backlog items. I have no clue what is happening here. The ware house is updated, I checked this by running the query
- SELECT TOP 1 __LastUpdatedTime
FROM dbo.[Work Item History] WITH (nolock)
ORDER BY __LastUpdatedTime DESC
SELECT *
FROM _WarehouseConfig
Any ideas for resolving the problem will be very helpful
|
|
|
|
|
Report
|
|
|
|
|
04-15-2008, 3:54 AM
|
gstib
Joined on 02-14-2008
Posts 2
|
Re: Sprint burndown chart returns exceptions
|
|
|
|
|
|
I had a similar problem occur when our third sprint was created. I proceeded to look for the cause by having a look at the detailed errors on the report server.
The error I would recieve was
The statement terminated. The maximum recursion 100 has been exhausted before statement completion.
This can be fixed by placing an OPTION(MAXRECURSION 10000) statement under the line of sql causing the error
E.G.
----------------------------------------------------------
--
-- Get a range of date records
--
----------------------------------------------------------
SELECT Date,
CAST(DAY(Date) AS varchar(2)) + '/' +CAST(MONTH(Date) AS varchar(2)) AS DateStr,
CAST(MONTH(Date) AS varchar(2)) + '-' +CAST(DAY(Date) AS varchar(2)) AS DateStrUS
INTO #CTE10
FROM CTEDATEc As d
INNER JOIN #CTE7 AS s
ON (d.Date BETWEEN s.SprintStart AND s.SprintEnd)
AND (@vWeekends = 'Included' OR DATEDIFF(day, @earlyDate, d.Date) % 7 > 1)
OPTION(MAXRECURSION 10000)
Interestingly once I had got the reports to work (and was able to view it) I noticed that the sprint seemed rather large.
The underlying cause of the error was my project manager had created a sprint that was six months long. (Which I'm assuming was never tested for)
|
|
|
|
|
Report
|
|
|
|
|
Scrum for Team ... » Version 1.2 - T... » Scrum for Team ... » Sprint burndown chart returns exceptions
|
|
|
|