Error processing Work Item Tracking Warehouse Sync job, data conflicts with deleted Team Project Collection

Question

I had deleted a Team Project Collection named TEST. I have a valid Team Project Collection remaining named HWDProjectCollection, I noticed the Warehouse is not getting the CompletedWork,RemainingWork and OriginalEstimate, they are NULL. I am using TFS 2010 retail. This is the error message on the 'Work Item Tracking Warehouse Sync" job. It looks to me like the TEST team project collection somewhere is not really deleted and that is why this job is failing? I had not modified those fields in either Team Project Collection.

</Job><job JobProcessingStatus="Idle" Name="Work Item Tracking Warehouse Sync"><Job JobProcessingStatus="Idle" Name="Work Item Tracking Warehouse Sync"><lastrun EndTimeUtc="2012-05-17T20:46:55.733Z" ExecutionStartTimeUtc="2012-05-17T20:46:54.86Z" QueueTimeUtc="2012-05-17T20:46:54.557Z" Result="Blocked"><LastRun Result="Blocked" EndTimeUtc="2012-05-17T20:46:55.733Z" ExecutionStartTimeUtc="2012-05-17T20:46:54.86Z" QueueTimeUtc="2012-05-17T20:46:54.557Z"><resultmessage><ResultMessage>[Work Item Tracking Warehouse Sync]:  ---> TF293000: The data warehouse has detected data conflicts for the following work item fields: System.Title<->System.Title ({Deleted} TEST (093E9483-C88D-4AC5-9EA1-E1140CDF3D91)); Microsoft.VSTS.Common.ActivatedDate<->Microsoft.VSTS.Common.ActivatedDate ({Deleted} TEST (093E9483-C88D-4AC5-9EA1-E1140CDF3D91)); Microsoft.VSTS.Scheduling.RemainingWork<->Microsoft.VSTS.Scheduling.RemainingWork ({Deleted} TEST (093E9483-C88D-4AC5-9EA1-E1140CDF3D91)); Microsoft.VSTS.Scheduling.OriginalEstimate<->Microsoft.VSTS.Scheduling.OriginalEstimate ({Deleted} TEST (093E9483-C88D-4AC5-9EA1-E1140CDF3D91)); Microsoft.VSTS.Scheduling.CompletedWork<->Microsoft.VSTS.Scheduling.CompletedWork ({Deleted} TEST (093E9483-C88D-4AC5-9EA1-E1140CDF3D91)). The conflicts occur because there are differences in the attributes set for reportable fields that are defined across team project collections. Updates to the data warehouse will continue for project collection HWDProjectCollection. However, updates to the data for the conflicting fields are suspended until the conflicts are resolved.  You can resolve these conflicts by making the definitions of the field the same in all project collections, or by marking the field as non-reportable in project collection HWDProjectCollection. For more information, see the following Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=160807.</ResultMessage></resultmessage></lastrun></job>

Answer 1

Hi AaronBrock, 

Thanks for your post.

How did you delete your Team Project Collection? To delete Team Project Collection, we should Detach this Team Project Collection first, then delete the Collection database from SQL Server. Please refer to the detailed steps in this document: http://msdn.microsoft.com/en-us/library/dd312130.aspx.      

As those fields all are default field and you had not modified them. I think you can try to delete the TFS_Warehouse database and recreate it using TFS Admin Console, then rebuild the Warehouse and Cube.

To delete the Tfs_warehouse database, you can connect to SQL Server using Microsoft SQL Server Management Studio, expand the Databases node, and delete the Tfs_warehouse database.  

To recreate the Tfs_warehouse database, please refer to the following steps:

1        Launch TFS Admin Console>>Application Tier>>Reporting, in the right panel, click Edit to open the Reporting windows.

2        Under the Warehouse tab, input the Tfs_warehouse under Database textbox.

3        Click Ok to generate the Tfs_warehouse database in SQL Server.

4        Click Start Jobs and Start Rebuild to rebuild warehouse and the Analysis Services database.

Manually processing the TFS 2010 Data Warehouse and Analysis Services Database, please refer to the detailed steps in this blog: http://blog.accentient.com/2010/04/08/ManuallyProcessingTheTeamFoundationServer2010DataWarehouseAndAnalysisServicesDatabase.aspx

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Ok Thanks for your response, I deleted the TFS Warehouse database. When I start the Jobs and then attempt to Start Rebuild it says Installation Parameters specify use an existing Database. How do i change those paramenters so it will create a new TFS warehouse database?

Answer 3

Hi AaronBrock, 

Thanks for your reply.

How did you delete the Tfs_Warehouse database? Deleted it from which SQL instance? 

What’s the detailed message you received when you start to build? 

When you type the Tfs_Warehouse in Database textbox(under Warehouse tab), please click the Test Connection button, what message you will receive?  

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us

Answer 4

Ok got past that last error now back to attempting to rebuild the Analysis services database. Getting an error in Event Viewer. I dont see Microsoft_VSTS_Build_FoundIn field in any Work Items. I did have a Bug work item but i have since deleted that Work Item from our Team Projects it wont be needed at this time. Why does the rebuild reference that field yet? What should i do now? Thanks for any help.

TF53010: The following error has occurred in a Team Foundation component or extension:

Date (UTC): 5/21/2012 8:49:45 PM

Machine: TFS

Application Domain: TfsJobAgent.exe

Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727

Service Host:

Process Details:

  Process Name: TFSJobAgent

  Process Id: 1852

  Thread Id: 1988

  Account name: 2BEHURD\TFSService1

Detailed Message: Failed to create or update dimension attribute for the Microsoft_VSTS_Build_FoundIn warehouse field in dimension Work Item.

Exception Message: Object reference not set to an instance of an object. (type NullReferenceException)

Exception Stack Trace:    at Microsoft.TeamFoundation.Warehouse.OlapCreator.AddOrUpdateDimensionAttribute(WarehouseConfig warehouseConfig, DataTable dataSource, Dimension dimension, Field field, Boolean createRelationshipToKey)

　

Answer 5

Hi AaronBrock,   

Thanks for your reply.

You can use the similar way to recreate Tfs_Analysis database, please refer the steps in this post: http://social.msdn.microsoft.com/Forums/pl-PL/tfsadmin/thread/9d806e2b-5442-478c-839e-531ff205521a.

If you want to processing Tfs_Warehouse and Tfs_Analysis database, Microsoft support is strongly recommending using this method to instead of manually doing it through SQL Management Studio.  

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us

Answer 6

Thank you for that Link I have been recreating the TFS Warehouse and TFS Analysis database as MS recommends through TFS Admin Console. I keep getting the same error when Processing the Analysis Database. For some reason it thinks that the

Microsoft_VSTS_Common_Severity  Is being used. I dont have any work items that are using that field in any Team Projects. In the TFSWarehouse dimWorkItem there is no Severity Field, it has been deleted. Where is the Analysis database rebuild finding Severity that it thinks it needs to have an attribute on dimWorkItem called Severity??

I have verified that I do not have an Active field called Severity, nor is it used in any of our current work items under any Team Project.

I cannot process the Cube with this error. Please help! Thanks!

Answer 7

Hi AaronBrock, 

Thanks for your reply. 

I’m currently looking this issue and will provide the response as soon as possible. I noted that you create new post for this issue, please tracking ours reply in this new post. 

If you have any further research of this issue, please share your experience there.  

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us

Answer 8

Issue has been resolved, Found a posting that a TFS 2010 Team Project Collection Cache should be deleted and an IISRESET completed. So I purged this folder C:\ProgramData\Microsoft\Team Foundation\Web Access\ I deleted the Files under both Cache folders. Reset IIS using IISRESET via command prompt, the did a full Delete, Rebuild and Process of the TFS Warehouse and the TFS Analysis Cube. And after the Full Process Analysis succeeded we are up and running!! Lesson learned... Check the Cache for TFS and delete it if needed.

---

Aaron Brockhaus

Answer 9

Hi AaronBrock, 

Thanks for your reply.

I’m glad to hear that you got it to work and thank you for sharing your experience here.

To clean the Cache manually, we can follow the below steps:

1.        Clean the Cache folder on client computer. The folder path is: C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\3.0\Cache(os: Windows Server 2008 R2)
2. Clean the Cache folder on Server machine. The folder path is: C:\Users\username(Web access user name)\AppData\Local\Microsoft\Team Foundation\3.0\Cache(os: Windows Server 2008 R2)
3. After cleaned, on Server machine, click Start and select Run… to open the dialog box, then input iisreset.exe and click OK, wait it run completely.

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us