Submit My Question - Recent Questions - Recent Answer
Msdn Tech >> Visual Studio Team System >> Team Foundation Server - Administration

TF53010: An unexpected condition has occurred in a Team Foundation component.

Hi,

I got the following warning log:

Event Type: Warning
Event Source: TFS Warehouse
Event Category: None
Event ID: 3000
Date: 4/25/2006
Time: 5:49:05 PM
User: N/A
Computer: TFS
Description:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 4/25/2006 3:49:05 PM
Machine: TFS
Application Domain: /LM/W3SVC/3/Root/Warehouse-1-127904354962833518
Assembly: Microsoft.TeamFoundation.Warehouse, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 4700
Thread Id: 1692
Account name: PEXIMBG\tfsservice

Detailed Message: Microsoft.TeamFoundation.WorkItemTracking.Adapter: Unable to determine from build name Prb_1.1.1.7 the correctly mapped build identifier since it is mapped to multiple build identifiers in the Work Item Tracking database. Work Items associated with this build will be mapped to Unknown.

Can anyone help me?

Thanks

[1190 byte] By [janko] at [2008-3-7]
«« Error using Code Coverage
»» GetService gives null for my DTE request
# 1

Hi Janko,

You would see this warning if you have more than 1 entries for any <project, build> pair in the BuildUri table of the TfsWorkItemTracking database. What happend was if you perform a build, delete the build and create a new build in the same project the same day, the build number from the deleted build will be reused. And the WIT erronously creates a new entry for the same build name. The warehouse adapter warns when it tries to resolve build names to build URIs because it sees the same build name pointing to multiple URIs.

This is a bug that was fixed in RTM. If you have RTM installed, new data will not have this issue. However it seems your database contains data from before that. You could take a look at [TfsWorkItemTracking].[dbo].[BuildUri] to identify <project, build> pairs with duplicated entries. You can also look at [TfsBuild].[dbo].[Builds] to see which URIs are valid in the system.

The side affect of this bug is if you have a work item pointing to one of these builds as IntegrationBuild or FoundInBuild, they will show up as Unknown in your reports.

Hope this helps!

-Jim

JimmyLi-MSFT at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Administration...
Visual Studio Team System
Team Foundation Server - Administration

Visual Studio Team System Hot Topic

Visual Studio Team System New Topic

Visual Studio Team System

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech

Site Classified