[Bug] DeniedOrNotExistException: TF26192: The team project specified by the ID 2 does not exist

[MicE44]

[16:20:35 ERR] [v14.3.7] Microsoft.TeamFoundation.WorkItemTracking.Client.DeniedOrNotExistException: TF26192: The team project specified by the ID 2 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 672

What happened?

Problem: The business moved 4 WI to the new project and deleted the old project.
The tool skipped this 4 WI now.
Is it possible to map the project ID?
Or can I skip this revision?

---

HELP NEEDED - We are unable to replicate this! But it does happen!

Can someone with this error please run a specific work item that they find has this issue through the tool and do one of the following:

Option 1: Generate and attach Log - if you are non-technical this is your option. It might provide us with enough info to diagnose, but may only result in more asks.

1. In the Config file change LogLevel to Debug.
2. Find a work item ID that has this issue, and craft a query that only selects this work item.
3. Delete any target copy of that work item.
4. Then run the migration
5. Comment here with the full Log attached

Option 2: Debug in Visual Studio - This option is best but requires some developer experience.

1. Fork the Repo and Clone it to your local computer
2. Open the Solution in Visual Studio (we use 2022) and do a Full Rebuild
3. Edit the Launch Profile to point to your config.
   
4. Craft the query to only load the work item with the issue
5. Add the breakpoints detailed above
6. "Play" the Launch Profile that you created and

Create a comment below with the results of your investigation!

[MicE44]

I could help me with this
MaxRevisions": 5,

But maybe you have a better solution?

[MrHinsh]

I don't have a better solution. It looks like the error is internal to the Azure DevOps API!

We should detect this issue and skip the revision.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days