MigrationTools.FieldMaps.NodePathNotAnchoredException: This path is not anchored in the source project name

[raczluk]

hi, could you please advise in this error?
is it related to iteration or area?

this is my config file

{
  "Serilog": {
    "MinimumLevel": "Information"
  },
  "MigrationTools": {
    "Version": "16.0",
    "Endpoints": {
      "Source": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "collectionURL",
        "Project": "Project_name",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "NetworkCredentials": {
            "Domain": "",
            "UserName": "",
            "Password": "** removed as a secret ***"
          },
          "AccessToken": "token"
        },
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        }
      },
      "Target": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "collectionURL",
        "Project": "Project_name",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "NetworkCredentials": {
            "Domain": "",
            "UserName": "",
            "Password": "** removed as a secret ***"
          },
          "AccessToken": "token"
        },
        "ReflectedWorkItemIdField": "ReflectedWorkItemId",
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        }
      }
    },
    "Processors": [
      {
        "ProcessorType": "TfsWorkItemMigrationProcessor",
        "Enabled": true,
        "UpdateCreatedDate": true,
        "UpdateCreatedBy": true,
        "WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan','Shared Steps','Shared Parameter','Feedback Request') ORDER BY [System.ChangedDate] desc",
        "FixHtmlAttachmentLinks": true,
        "WorkItemCreateRetryLimit": 5,
        "FilterWorkItemsThatAlreadyExistInTarget": false,
        "GenerateMigrationComment": true,
        "SourceName": "Source",
        "TargetName": "Target"
      }
    ],
    "CommonTools": {
      "FieldMappingTool": {
        "Enabled": true,
        "FieldMaps": []
      }
    }
  }
}

[MrHinsh]

It's not possible to see what the issue is as you have truncated the log.

Above the error it should tell you which area and/or iterations are the issue and you can use #1846 to map them.

[raczluk]

I have iterations and areas migrated from the source to target project, the issue is related with teams that were not migrated, could you please advise in this scenario?
Does the tool support teams migration or this should be done manually?
What you can see on the screenshot (Replicant) is the team name

here is the log

[17:40:26 INF] [16.0.7] 16.0.7 
[17:40:26 INF] [16.0.7] naked Agility with Martin Hinshelwood  
[17:40:26 INF] [16.0.7] =============================================================================== 
[17:40:26 INF] [16.0.7] -------------------------------------- 
[17:40:26 INF] [16.0.7] Telemetry Note: 
[17:40:26 INF] [16.0.7]    We use Application Insights to collect usage and error information in order to improve the quality of the tools. 
[17:40:26 INF] [16.0.7]    Currently we collect the following anonymous data: 
[17:40:26 INF] [16.0.7]      -Event data: application version, client city/country, hosting type, item count, error count, warning count, elapsed time. 
[17:40:26 INF] [16.0.7]      -Exceptions: application errors and warnings. 
[17:40:26 INF] [16.0.7]      -Dependencies: REST/ObjectModel calls to Azure DevOps to help us understand performance issues. 
[17:40:26 INF] [16.0.7]    This data is tied to a session ID that is generated on each run of the application and shown in the logs. This can help with debugging. If you want to disable telemetry you can run the tool with '--disableTelemetry' on the command prompt. 
[17:40:26 INF] [16.0.7]    Note: Exception data cannot be 100% guaranteed to not leak production data 
[17:40:26 INF] [16.0.7] -------------------------------------- 
[17:40:26 INF] [16.0.7] Start Time: "2024-11-14T17:40:26.0714658+01:00" 
[17:40:26 INF] [16.0.7] Running with settings: {"ConfigFile":"C:\\Users\\user\\Desktop\\configuration.json","DisableTelemetry":false,"DebugTrace":false,"skipVersionCheck":false,"$type":"ExecuteMigrationCommandSettings"} 
[17:40:26 INF] [16.0.7] OSVersion: Microsoft Windows NT 6.2.9200.0 
[17:40:26 INF] [16.0.7] Version (Assembly): 16.0.7 
[17:40:26 INF] [16.0.7] Logpath: C:\Users\user\AppData\Local\Microsoft\WinGet\Packages\nkdAgility.AzureDevOpsMigrationTools_Microsoft.Winget.Source_8wekyb3d8bbwe\logs\20241114174023 
[17:40:33 INF] [16.0.7] Verion Info: 
[17:40:33 INF] [16.0.7]      Running: 16.0.7.0 
[17:40:33 INF] [16.0.7]      Installed: 16.0.7 
[17:40:33 INF] [16.0.7]      Available: 16.0.7 
[17:40:33 INF] [16.0.7] Creating Migration Engine 1abda047-3524-4bed-86fc-9bdb278140b4 
[17:40:33 INF] [16.0.7] ProcessorContainer: Of 1 configured Processors only 1 are enabled 
[17:40:33 INF] [16.0.7] ProcessorContainer: Adding Processor TfsWorkItemMigrationProcessor 
[17:40:33 INF] [16.0.7] Logging has been configured and is set to: unknown.  
[17:40:33 INF] [16.0.7]                               Max Logfile: Verbose.  
[17:40:33 INF] [16.0.7]                               Max Console: Debug.  
[17:40:33 INF] [16.0.7]                  Max Application Insights: Error.  
[17:40:33 INF] [16.0.7] The Max log levels above show where to go look for extra info. e.g. Even if you set the log level to Verbose you will only see that info in the Log File, however everything up to Debug will be in the Console. 
[17:40:33 INF] [16.0.7] Beginning run of 1 processors 
[17:40:33 INF] [16.0.7] Processor: TfsWorkItemMigrationProcessor 
[17:40:33 INF] [16.0.7] Migration Context Start: TfsWorkItemMigrationProcessor  
[17:40:34 INF] [16.0.7] Migrating all Nodes before the Processor run. 
[17:40:34 INF] [16.0.7] Connecting with AccessToken  
[17:40:35 INF] [16.0.7] Access granted to "https://Collection.Reducted.com/tfs/Collection/" for user 
[17:40:36 INF] [16.0.7] Connecting with AccessToken  
[17:40:37 INF] [16.0.7] Access granted to "https://dev.azure.com/MigrationTest/" for user
[17:40:39 INF] [16.0.7]  Processing Node: \Reducted\Area\z_[DO NOT USE THIS TREE] System 1 Next Gen (Application) [DO NOT USE THIS TREE], start date: null, finish date: null 
[17:40:39 INF] [16.0.7]  Processing Node: \Reducted\Area\z_[DO NOT USE THIS TREE] System 1 Next Gen (Application) [DO NOT USE THIS TREE]\REB, start date: null, finish date: null 
...
[17:48:45 INF] [16.0.7]  Processing Node: \Reducted\Iteration\Historical\STP\FW POC, start date: "2018-12-09T00:00:00.0000000", finish date: "2018-12-29T00:00:00.0000000" 
[17:48:45 INF] [16.0.7]  Processing Node: \Reducted\Iteration\Historical\STP\FW POC\FW POC Ready, start date: "2018-12-10T00:00:00.0000000", finish date: "2018-12-28T00:00:00.0000000" 
[17:48:46 INF] [16.0.7]  Processing Node: \Reducted\Iteration\2022, start date: "2022-01-01T00:00:00.0000000", finish date: "2022-12-31T00:00:00.0000000" 
[17:48:46 INF] [16.0.7]  Processing Node: \Reducted\Iteration\Retro Action Items Feb-23, start date: "2023-02-24T00:00:00.0000000", finish date: "2024-03-31T00:00:00.0000000" 
[17:48:47 INF] [16.0.7] Work Item Store connected to "https://dev.azure.com/MigrationTest/" with BypassRules set to true 
[17:48:48 INF] [16.0.7] ---------------------------------------------- 
[17:48:48 INF] [16.0.7] Migrating all Teams before the Processor run. 
[17:48:49 INF] [16.0.7] TfsTeamSettingsProcessor::InternalExecute: Found 266 teams in Source? 
[17:48:50 INF] [16.0.7] -> Settings found for team 'Replicant'.. 
[17:48:50 WRN] [16.0.7] NodeStructureEnricher.NodePathNotAnchoredException(Replicant, Area) 
[17:48:50 FTL] [16.0.7] Error while running TfsWorkItemMigrationProcessor 
MigrationTools.FieldMaps.NodePathNotAnchoredException: This path is not anchored in the source project name: Replicant
   at MigrationTools.Tools.TfsNodeStructureTool.GetNewNodeName(String sourceNodePath, TfsNodeStructureType nodeStructureType) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsNodeStructureTool.cs:line 140
   at MigrationTools.Tools.TfsTeamSettingsTool.MigrateTeamSettings() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsTeamSettingsTool.cs:line 157
   at MigrationTools.Tools.TfsTeamSettingsTool.ProcessorExecutionBegin(TfsProcessor processor) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsTeamSettingsTool.cs:line 80
   at MigrationTools.Processors.TfsWorkItemMigrationProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 106
   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
[17:48:52 INF] [16.0.7] TfsWorkItemMigrationProcessor completed in 00:00:00  
[17:48:52 ERR] [16.0.7] TfsWorkItemMigrationProcessor The Processor MigrationEngine entered the failed state...stopping run 
[17:48:52 INF] [16.0.7] Command ExecuteMigrationCommand completed in "00:08:26.8521395" 
[17:48:52 INF] [16.0.7] Check the logs for errors: C:\Users\user\AppData\Local\Microsoft\WinGet\Packages\nkdAgility.AzureDevOpsMigrationTools_Microsoft.Winget.Source_8wekyb3d8bbwe\logs\20241114174023 ```

[MrHinsh]

This error only usually occurs when Work Items are moved from one Project to another and we have Area or Iteration paths that don't exist in the target. I've not seen it for TFS.