TF400898: An Internal Error Occurred when accessing the Product Backlog

When I try to access one of my teams product backlogs, I receive the following error:


The page you are looking for is currently unavailable.

TF400898: An Internal Error Occurred.

 More information about this error


We are on Urban Turtle 2012 version

Microsoft Visual Studio Team Foundation Server Version 11.0.60610.1



  • This is only for the Product Backlog board and only for one team. I can access this board for other teams.
  • I have not seen any issues with the Sprint Backlog
  • Other people on my team, with identical permissions, can access the backlog


This is what I’ve tried so far to no avail:

  • Different browsers
  • Creating a new Team in TFS and putting myself in it
  • Accessing from different machines


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • 0
    Permanently deleted user

    Hi Robert,

    If you allow all the iterations and areas in the project to be visible to the team you are in, does the error occur again? You can make all the iteration visible by clicking on the gear, clicking on the iteration tab and selecting all the iterations at the first level. The same applies for areas.

    Is it possible to send us the stack trace that was logged when the error occurred? The stack trace can be found in the Windows Event logger on the TFS server. You can ask your TFS administrator for it. 


  • 0
    Robert L.

    Hi Francis. We were able to resolve the issue. Once we got the error log we were able to see that there was an overflow error. One of the backlog priorities was set to too large of a number. By creating a query in TFS we were able to find the item, change the number, and resolve the problem.


    We had similar issues when we last upgraded UT. This time, however, I’m pretty sure UT set that number itself. You, of course, would have more insight as to how the priority numbers are automatically sent.


    Anyway, hope this helps with any current or future issues.



  • 0
    Permanently deleted user

    Hi Rob,

    We have never seen that kind of error in Urban Turtle 4.10. I will consider the issue solved but if the problems occurs again, do not hesitate to contact us at and we will try to find what is the cause of  the error.


Please sign in to leave a comment.