TF26192: The team project specified by ID XX does not exist. Check the team project ID and try again

[johnmuff]

I've done a couple of test migrations from one Azure DevOps to another organisation DevOps having already migrated the Process. Everything transfers as expected except work items that USED to belong in a now deleted project.

Some work items in my source once belonged to another project that has since been deleted. They contain a history record of them moving from the old project.
These work items throw an error during the migration and are not migrated - the error is "TF26192: The team project specified by ID 17 does not exist. Check the team project ID and try again"
Have you seen this before and if so, is there a workaround?
Thanks

[stevns]

I'm facing the same issue.

[stevns]

@MrHinsh : Maybe we can use a replace filter?

[stevns]

Output from run:

[14:08:01 ERR] Microsoft.TeamFoundation.WorkItemTracking.Client.DeniedOrNotExistException: TF26192: The team project specified by the ID 37 does not exist. Check the team project ID and try again.
   at Microsoft.TeamFoundation.WorkItemTracking.Client.ProjectCollection.GetById(Int32 projectId)
   at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItem.CheckUpdateCachedData(Boolean projectChanged, Boolean typeChanged)
   at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItem.get_Type()
   at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemFieldData.Microsoft.TeamFoundation.WorkItemTracking.Internals.IWorkItemOpenFieldDataHelper.SetLatestData(Dictionary`2 latestData)
   at Microsoft.TeamFoundation.WorkItemTracking.Internals.WorkItemHelper.LoadWorkItemFieldData(IRowSetCollectionHelper tables, IWorkItemOpenFieldDataHelper helper)
   at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItem.LoadWorkItemFromRowSetInternal(Int32 rev, Nullable`1 asof, IWorkItemRowSets witem)
   at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItem..ctor(WorkItemStore store, Int32 id, Int32 revision)
   at MigrationTools.TfsExtensions.GetRevision(WorkItemData context, Int32 rev) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\TfsExtensions.cs:line 35
   at VstsSyncMigrator.Engine.WorkItemMigrationContext.ReplayRevisions(List`1 revisionsToMigrate, WorkItemData sourceWorkItem, WorkItemData targetWorkItem) in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 484

[Wollman19]

@MrHinsh - Any advice on this? I'm running into this issue as well. Except the project these work items that were migrated from still exist - but in a different org.

[Wollman19]

Hey all, I was using this tool to migrate a project from one org to another with one small caveat - about 200 work items had already been migrated from a project outside the organization I'm working in. Plus, the work items that had already been migrated once still existed in the old org. So although mine weren't from a project that had been deleted, I was getting the same error as @johnmuff . The work around for me was to alter the "maxrevisions" param to 1 (is defaulted to 0). Hope this helps!

[SensFanInBoston]

I am also getting this error. If anyone has any resolution or 'fix' that allows you to import these items (maybe without the history) I would appreciate it.

[MrHinsh]

You can turn off history and it will only import the latest.

The next easiest way to resolve this is for one of those with the error to debug and resolve it with a PR.

[voonxx]

Hi all, im facing the same issue with version 15.2. I try to put the "maxrevisions" param in but it seems like not recognising it, is there any changes for this version?

[MrHinsh]

This will not work. The ObjectModel API will not load a work item that has a project that has been deleted anywhere in its history! period...

There is nothing we can do for this one.

[gsadrija]

Are there any news on this topic? We are currently experiencing the same issue. We are unsure if the setting for "ReplayRevisions" could be sufficient to solve this.

[MrHinsh]

Ive converted this to a quersion and added an answer. But ultimatly you would ned to exclude this work item from the migration.

[MrHinsh]

Unresolvable Limitation: Affected Work Items Cannot Be Migrated

There is no viable workaround.

The TfsObjectModel cannot handle work items that were moved to another project when the original project has since been deleted. This results in a hard, internal exception within Microsoft’s implementation.

These work items cannot be loaded, accessed, or processed by any available code path in the TFS Object Model.

---

Impact:
Any work item in this state is non-recoverable through the TfsObjectModel and cannot be included in the migration.

---

Required Action:
These work items must be explicitly excluded from all queries and migration scope.

---

A future version of the tooling, based on the REST API rather than the TfsObjectModel, is in development and is expected to avoid this limitation.