TF51011: The node specified is not found in the classification hierarchy.

Question

 

I see the following error on my project home page instead of the burndown.

 

TF51011: The node specified is not found in the classification hierarchy. The error is caused by «'ProjectName\Release 2\Sprint 1'».

Has anyone else got this error? 

I renamed Release 2 to something else, and set it as the iteration backlog. Which produced the error. I then renamed the release back to "Release 2" as I've had problems with renaming sprints before, but it didn't fix it.

 

EDIT: I had some left over backlog items (From Release 1) that were were still in the committed state that I set to removed. Once I did this the problem vanished. As it was displayed in the area where the effort is shown, perhaps there is a bug in calculating hours that includes items from a previous iteration. 

Answer 1

I'm pretty sure this might have more to do with caching than editing any left over backlog items. We cache the team settings for performance. We had some bugs where the cache was not invalidated at the correct times, which may why you were seeing the error, then after a bit of time, it went away.

If, however, you can repro this consistently, please let us know and we'll investigate it.

Thanks

---

Gregg Boer - TFS Product Team

Answer 2

I am experiencing a similar problem.  I have cleared the cache several times and it has not solved the problem.  Has there been any more development on this problem?

I am creating a new iteration and i receive the error:  "TF51011: The node specified is not found in the classification hierarchy. The error is caused by «'PROJECTNAME\Iteration 5'»."

Thank you!

Answer 3

Hi,

I'm facing the same issue. I'm consistently getting this error while connecting to a particular project.

Can you tell me how can i resolve this?

And i don't know from where i should remove the cached items as you mentioned in your post.

NOTE: I'm getting this behavior even trying it out after few days.

Answer 4

Hi Sunil,

I've tried to reproduce this issue and have been unsuccessful so far. I have a few questions that may help me narrow down the issue.

1. Can you reproduce this issue with a new project, or only with the affected project?

2. Are you able to reproduce the issue with the affected project using different browsers?

3. Could you send screenshots of the error message you see when you connect to the project and also your iterations admin page to [e-mail]?

Thanks,

Kelly

Answer 5

I found this issue in projects created with Microsoft Visual Scrum 1.0. What I did was to edit each query where the error occured, changing the value for "Iteration Path" to <project-name> only.