WITImport problem in TFS 2008 - Validation pass but import fails on new field

Question

Hi,

 

When performing an import of a new work item type with the WITImport command I receive the following error:

 

"Work Item Type Import failed to make the requested field changes."

 

If I use the same command with the parameter /v (for validate), I receive "Work item type validation complete."

 

After some trial and error I found that adding any new field in any process template is giving me the problem. In addition, I'm able to import a process template that contains work item type with new fields in their definition successfully. However, if I tried to create a new Team Project from the new template it fails with the same error message "Work Item Type Import failed to make the requested field changes.".

 

The new field added is not conflicting with anything pre-existing. The field syntax is simple. Here is an example:

   <FIELD name="Test 20080226" refname="Incycle.Common.Test20080226" type="PlainText">
   </FIELD>

 

Any idea on what could be causing this error or how to further diagnose the problem?

 

Thank you for your help.

 

Martin Rajotte

Incycle Software

Answer 1

 

Did you find a solution for this?

Answer 2

 

Martin contacted customer support for this issue.

 

In Martin's particular case, the WITImport failed due to violation of an internal data integrity check in TFS2008. We have an internal check that all active fields must have active usages. Unfortunately, there is a known defect in TFS2005 that can cause this particular corruption. Martin hit this prior to upgrade.

 

In TFS2005, if one creates, deletes, and subsequently re-creates an Html or PlainText field, the Html/PlainText field may end up in partially active state. This was fixed in TFS2008.

 

To check for this condition:

SELECT *

FROM [TfsWorkItemTracking].[dbo].[Fields]

WHERE [fDeleted] = 0

AND [FldID] IN (SELECT u.[FldID] FROM [TfsWorkItemTracking].[dbo].[FieldUsages] WHERE [fDeleted] = 1)

 

To repair this condition, please contact customer support. The resolution is not as simple as flipping the bits.

Answer 3

 

In our case this returns these:

Name NewName fDeleted ReferenceName

Proposed Date Proposed Date 0 Microsoft.VSTS.CMMI.ProposedDate
Proposed By Proposed By 0 Microsoft.VSTS.CMMI.ProposedBy
How Found (Old CMMI) How Found (Old CMMI) 0 Microsoft.VSTS.Old.CMMI.HowFound
Impact on Architecture (Old CMMI) Impact on Architecture (Old CMMI) 0 Microsoft.VSTS.Old.CMMI.ImpactOnArchitecture
Impact on Test (Old CMMI) Impact on Test (Old CMMI) 0 Microsoft.VSTS.Old.CMMI.ImpactOnTest
Impact on Development (Old CMMI) Impact on Development (Old CMMI) 0 Microsoft.VSTS.Old.CMMI.ImpactOnDevelopment

 

So does this indicate this situation? When looking at the names, should these be found on some CMMI project? What if I just delete these projects as we do not currently have any CMMI projects active?

 

//Ilpo

Answer 4

 

Answering my own question:

- Deleting these projects did not help

 

But after looking into the sql above, I got it solved by changing the db directly for these fields that the sql found.

 

So now again everything is working, thanks for guiding for right direction.

 

//Ilpo