Unable to load Common Structure for Target

[kimi0112]

[07:19:16 FTL] [16.0.4] An error occurred in the Migration Tools causing it to stop! This is likley due to a configuration issue and is not being logged remotely. You can always ask on https://github.com/nkdAgility/azure-devops-migration-tools/discussions
MigrationTools.Exceptions.MigrationToolsException: Unable to load Common Structure for Target.This is usually due to TFS having a different installed langauge version than was expected.. Validate that 'Area' is the correct name in your version. This would be something like 'Fläche' or 'Aire'. If you open the area tree in Visual Studio, or web access, you should see the name your langauage uses for 'Area' or 'Iteration. Do not try to add a specific area or iteration path to this field. Check the defaults on https://nkdagility.com/learn/azure-devops-migration-tools/Reference/Endpoints/TfsTeamProjectEndpoint/ for an example fro English.
at MigrationTools.Tools.TfsNodeStructureTool.ProcessCommonStructure(String treeTypeSource, String localizedTreeTypeName, String projectTarget, TfsNodeStructureType nodeStructureType) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsNodeStructureTool.cs:line 464
at MigrationTools.Tools.TfsNodeStructureTool.MigrateAllNodeStructures() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsNodeStructureTool.cs:line 408
at MigrationTools.Tools.TfsNodeStructureTool.ProcessorExecutionBegin(TfsProcessor processor) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsNodeStructureTool.cs:line 285
at MigrationTools.Processors.TfsWorkItemMigrationProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 103
at MigrationTools.Processors.Infrastructure.Processor.Execute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 99
[07:19:16 INF] [16.0.4] TfsWorkItemMigrationProcessor completed in 00:00:00
[07:19:16 ERR] [16.0.4] TfsWorkItemMigrationProcessor The Processor MigrationEngine entered the failed state...stopping run

When I run the tools, it fails, it seems the "Area" name is not correct, Where can I find the "AreaPath" and "IterationPath" name in Azure devops, thank you.

[MrHinsh]

It's based on your on-prem language version.

It can also be due to your collection URL being wrong.

[MrHinsh]

You need to ensure that all work items that are to be migrated to the target have the ReflectedWorkItemId field added.

https://nkdagility.com/learn/azure-devops-migration-tools/setup/reflectedworkitemid/

[kimi0112]

thanks a lot, I have solved the above issue, but it shows another error again. The error is as below. How do I fix this error, thank you
[05:32:17 ERR] [16.0.4] Missing Iterations in Target preventing progress, check log for list. To continue you MUST configure IterationMaps or AreaMaps that matches the missing paths..

[MrHinsh]

@kimi0112 there is a link to the documentation to resolve this in the error message. Have you read that page? What have you tried?

[kimi0112]

the link page "https://nkdagility.com/learn/azure-devops-migration-tools//Reference/v2/ProcessorEnrichers/TfsNodeStructureTool/#iteration-maps-and-area-maps", right? but it shows The page can’t be found

[MrHinsh]

There are only links in the copy. Happy to take a PR to fix...

The left navigation has the correct link.

• That one is pinned to the top of the discussion forums.