-
I am attempting to upgrade to use a version 16 config instead of a 15.2.. {"Timestamp":"2024-12-03T11:55:58.5226939-06:00","Level":"Fatal","MessageTemplate":"Error while running {MigrationContextname}","TraceId":"48645ea5c2ba2f8aef9da05e9c65865c","SpanId":"ae3134754740deec","Exception":"System.Web.Services.Protocols.SoapException: TF400493: A team iteration cannot be created for a tree node that is not an iteration node.\r\n at I see this in the log How can I make this NOT try to migrate the teams? I've got the teams configured in the target, and have area paths/iteration paths mapped so things land where I want them, I don't want this to do anything more than move the items I've selected in my query. I have configured a TfsWorkItemMigrationProcessor but have not configured a TfsTeamSettingsProcessorOptions so I am confused as to why it's trying to "Migrate all Teams". |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
The default behaviour is that the TfsTeamSettingsTool runs to migrate teams. All of the
|
Beta Was this translation helpful? Give feedback.
-
just to follow up, I was able to get this configured and running successfully. I did run in to a bug found in v16.0.8 (User map null bug) but it was fixed in 16.0.9 that was release today, so migration is executing! |
Beta Was this translation helpful? Give feedback.
The default behaviour is that the TfsTeamSettingsTool runs to migrate teams.
All of the
Tools
can be disabled with: