MigrationTools.Exceptions.MigrationToolsException: Unable to load Common Structure for Target.

[yadwendrav]

I have a setup where TFS 2015 was configured and running. Now is a time when TFS 2015 is about to be shutdown and we need to migrate the project. I am trying to migrate the project on -in-premise Azure DevOps server 2022. I am getting the below error:

[23:27:09 INF] [16.1.0] Prompting for credentials
[23:27:13 INF] [16.1.0] Access granted to https://server/tfs/TFS01/ for user (domain\user)
[23:27:14 INF] [16.1.0] Prompting for credentials
[23:27:22 INF] [16.1.0] Access granted to http://target/TFS01 for User (Server\user)
[23:27:22 INF] [16.1.0] Migrating all Nodes before the Processor run.
[23:27:25 FTL] [16.1.0] 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 'Areas' 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 469
at MigrationTools.Tools.TfsNodeStructureTool.MigrateAllNodeStructures() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsNodeStructureTool.cs:line 413
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 287
at MigrationTools.Processors.TfsWorkItemMigrationProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 102
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
[23:27:25 INF] [16.1.0] TfsWorkItemMigrationProcessor completed in 00:00:00
[23:27:25 ERR] [16.1.0] TfsWorkItemMigrationProcessor The Processor MigrationEngine entered the failed state...stopping run
[23:27:25 INF] [16.1.0] Command ExecuteMigrationCommand completed in 00:00:24.0083282
[23:27:25 INF] [16.1.0] Check the logs for errors:

\logs\20250331232700

I have checked and found that in both the configuration language and Area is same.

[MrHinsh]

You should follow Move a project collection to move your TFS 2015 collection to your Azure DevOps 2022 server.

---

It looks like you have a non-english version of TFS 2015 installed.

This is usually due to TFS having a different installed langauge version than was expected.. Validate that 'Areas' 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.

[fabricegauvreau]

For my part, I saw this error when my account token for the target project had expired. This was resolved once the token was renewed.