Recurring TFS errors in event log

Question

Starting about 60 hours ago, the System Log began showing this series of error, sourced from TFS, recurring continuously about every 2 minutes:

> eDT: Field CategoryId is missing for fact Result; no default value defined for type NChar.

Followed by:
> eDT: Adding fact Result got exception System.ArgumentOutOfRangeException: Specified
> argument was out of the range of valid values.
>
> Parameter name: Missing field value for: CategoryId.CategoryId

Followed by:
> eDT: Got exception at stage getting result {e09d67f0-0e82-4f31-806c-62cc9784ad47} for run
> f4b5554e-098b-489f-9080-c91d4ef08045: System.ArgumentOutOfRangeException: Specified
> argument was out of the range of valid values.
>
> Parameter name: Missing field value for: CategoryId.CategoryId

The sequence repeats one second later, then, after a lapse of 90-120 seconds, the whole sequence of six events occurs again. As mentioned, this was occurring for a while last week (a few hours) stopped, and began again Monday @4pm, and has been repeating like clockwork ever since. We're not aware of any activity that occurred, or began, about that time to account for it. Also the server HAS been rebooted during this time. The error sequence begins again following the reboot.

Can anyone cast any light on what may be going on here?

daniel

Answer 1

Hi Milo,

Thanks for posting this.  The issue is known by our team and they will fix it in RTM.

Thanks

Bruce

Answer 2

Hi Bruce;

Thanks for the quick response. Do you have any info whether this ongoing situation has any impact on the performance or stability of the server?

daniel
Olenick & Associates

Answer 3

The frequency of the event log errors is due to the fact that the warehouse kicks in every two minutes in the beta release.  See this blog post to change it.

http://blogs.msdn.com/buckh/archive/2005/04/19/409886.aspx

Buck

Answer 4

I've experimented with this. Somewhat against my expectation, manually triggering the warehouse refresh, as described in the blog entry, did NOT generate the error (a "Success Audit" was logged by MSSQLSERVER instead). Changing the interval to 600 seconds (10 minutes), as expected, has reduced the frequency of the error loggings to the same interval. As an apparent side-effect, the number of "Success Audit" messages logged by MSSQLSERVER, recurring at approximately the same interval, has increased. I wonder if the error is due to recurring scheduled activities tramping on each other?

daniel
Olenick & Associates.