TFS2012.2 – Issue: Object not set to instance of object with TF400898, TF53010 & TF30065

You may get an exception when working with Areas or Teams in Team Foundation Server 2012.2 that results in an Object not set to instance of object with TF51011, TF400898, TF53010 & TF30065 errors.

It may affect only one collection or all of them.

TF51011: The specified area path does not exist
Figure: TF51011: The specified area path does not exist

As well as this error you may get many other errors doing other actions from both the web interface and Visual Studio around the interaction with and use of Areas and Iterations.

Applies to

  • Visual Studio Team Foundation Server 2012.2


I first encountered this error on TF Service where I could really access no event or exception information. I raised it with the Product Team and they fixed it in place. I have however now encountered this error on an on premises server running Visual Studio Team Foundation Server 2012.2 and this has been identified as a know bug with Update 2.

The two main error number you will see in the event log really give us very little information. There is the TF400898 message that is thrown in the UI whenever there is a problem that can’t be identified. In addition the TF30065 number represents an unhandled internal exception. In either case you will need to do a little investigation to find the real cause. The TF51011 error shown above can happen if you have deleted an area and the UI has not caught up.

Note if at this point your are on TF Service then you need to raise it on the Team Foundation Service forum for the product team to investigate.

If you look in your event log and you see a whole bunch of TF30065 exceptions, that catch all number I mentioned, we need to take a look at the details. In this case there were many “Object reference not set to an instance of an object” references for the same method.

The “Microsoft.TeamFoundation.WorkItemTracking.Server.DataAccessLayerImpl.SyncTree” method is to do with the Area and Iteration trees and Sync’ing them with work item tracking. Something is not right here.

TF400898: An Internal Error Occurred
Figure: TF400898: An Internal Error Occurred

Again the catch all web error, but this time it is for creating a new Team. This is due to Team and Area being tied together by default. You may be able to bypass the error by un-ticking the “Create an area with the name of the team” option, but this does not fix the underlying issue.

You may also experience the list of Areas or Iterations that are listed on a Work Item not matching up with what it says in the Tree. This is again due to that “Sync” method failing.

Operational Interface job status graph
Figure: Operational Interface job status graph

If you load operational interface from the http://mytfsserver:8080/tfs/_oi (yes you just put “_oi” after the URL for your TFS server.) Then you should see a graph of all of the running jobs and their status. If the “Work Item Tracking Integration Synchronisation” job is failing and the other characteristics above are also true then you might be hitting a known bug:

“◦When you create a new area path, and then you move an existing area path under the newly-created one, the “Work Item Tracking Integration Synchronization” job may fail with a “System.NullReferenceException” exception.”KB2835600 Visual Studio 2012 Update 3 RC 1


It looks like this is a known bug in Update 2 that has been fixed in Update 3. As luck would have it the product team just put Update 3 RC1 live and are providing a go-live licence.

Note Go-live refers to a type of licence that allows you to use pre-release software in production in a fully supported manor. These tend to be more tested than hotfixes but less than a ‘released’ product. The TFS team has been using go-live as a medium to allow their product or update to be tested in production before they stick that RTM label on it. As most bugs that are not caught in development are caught by early adopters in the first few weeks of a release this is incredibly valuable for the team.

As I had encountered this error before I knew there was a fix so I asked around and got this response:

I’m really sorry but your customers are running into a known bug in Update 2 with the sync between CSS system and WIT system. The bug is fixed in the QU3 RC release that went out today and ideally the customer should upgrade to that to take the fix.

I have absolutely no problems recommending that my customer install Visual Studio 2012 Update 3 RC 1 (KB2835600). I have been using the go-live licence with customers for many years with few, but not no, issues. In fact I would say that I have had fewer issues with a TFS go-live version than with most other RTM’ed products.

If you are installing the Visual Studio 2012.3 (Update 3) “go-live” CTP then you just want to make sure that you test it first on a pre-production system and that you install the RTM upgrade as soon as it is available.