Exception on Warehouse update on specific changeset

Question

Hi

After having first deleted and then destroyed a large number of items in source control, an exception is showing up in the application eventlog on the AT server. This event refers to a specific changeset.

We're running TFS 2008 SP1.

It's pretty much the same event as I've seen earlier in TFS 2005 where there was a hotfix for the issue. But I have not been able to find anything on this specific issue for TFS 2008 SP1.

If I display the changeset it appears as expected, showing no items as they are destroyed, and no exceptions occur in the eventlog on this occasion. A lot of other changesets were of course in scope for the deleting and destroying actions, but only this one triggers an exception (or is it just the first one...?)

The data warehouse update seems to run ok for everything else.

The destroy commands were run with the /startcleanup parameter

Any feedback on this would be appreciated.

The eventlog entry that repeats every hour on the scheduled update goes like this:

Event Type: Error
Event Source: TFS Warehouse
Event Category: None
Event ID: 3000
Date:  22-10-2009
Time:  08:19:53
User:  N/A
Computer: Wxxxxx
Description:
TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 22-10-2009 06:19:53
Machine: W92163
Application Domain: /LM/W3SVC/1752970902/Root/Warehouse-5-129005831606493544
Assembly: Microsoft.TeamFoundation.Warehouse, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
  Process Name: w3wp
  Process Id: 4292
  Thread Id: 6080
  Account name: NT0001\Cxxxxxx

Detailed Message: Microsoft.TeamFoundation.VersionControl.Adapter: An error occurred while processing changeset 90874, unexpected exception:
Exception Message: Object reference not set to an instance of an object. (type NullReferenceException)

Exception Stack Trace:    at Microsoft.TeamFoundation.VersionControl.Client.Item.get_IsContentDestroyed()
   at Microsoft.TeamFoundation.VersionControl.Adapter.Hatteras.calculateDifferences(Item previous, Item current)
   at Microsoft.TeamFoundation.VersionControl.Adapter.Hatteras.calculateChurnForFilePair(FilePair filePair)
   at Microsoft.TeamFoundation.VersionControl.Adapter.VCAdapter.processChangesets() 

Kind regards,
Carsten-S

Answer 1

Hi again.

Cancelling the alert...

For some reason, the exception has gone away this afternoon. Right now I'm not aware of any spcecial activity that could have caused this change in behaviour. Could it have something to do with the cleanup job??

Well, nice to look at a clean eventlog again...

Kind regards,
Carsten-S