microsoft / vsts-work-item-migrator

WiMigrator is a command line tool for migrating work items between VSTS/TFS projects
MIT License
148 stars 69 forks source link

Unable to read the migration query #65

Open iambernics opened 5 years ago

iambernics commented 5 years ago

Hi All,

I am migrating Work Items from TFS 2017 to Azure DevOps.

It is working properly with some projects but I am getting error on a project:

"Unable to read the migration query"

in the log:

[Error @07.22.29.275] Validation error: Common.Validation.ValidationException: Unable to read the migration query ---> Common.RetryPermanentException: Permanent error for 683c5b2c-649c-4dd1-9ca1-49c22ee052c0, not retrying ---> Microsoft.VisualStudio.Services.WebApi.VssServiceResponseException: Page not found.

I created the affected Query under the Shared Queries and all another settings are similar with the another projects.

The project name is contain slash "/ ", maybe the Migrator could not handle this character?

Regards, Gabor

iambernics commented 5 years ago

Sorry, it was my mistake: the project name was wrong.

After I fixed it, the validation passed but I got this result on the migration:

[Error @18.44.03.208] 4091 total work item(s) failed. [Error @18.44.03.209] 4014 work item(s) failed for this reason: BadRequest. [Error @18.44.03.216] 77 work item(s) failed for this reason: UnexpectedError.

There are lot of warnings and errors in the log, for example:

[Warning @18.43.05.390] Could not find corresponding AreaPath: GLC_GRPCOMPASS\GLC_GroupCompass_2016 on target. Assigning the AreaPath: GLC_GRPCOMPASS\missing area path on source work item with Id: 35081.

[Error @18.43.08.950] Status Code: 400. Work item 35081 failed during batch 1.{"count":1,"value":{"Message":"TF401347: Invalid tree name given for work item -1, field 'System.AreaPath'."}}

Have you any idea?

ruffrydery2000 commented 5 years ago

try creating 2 different access tokens. one for source and one for target

obvioussean commented 5 years ago

@iambernics did you figure out your issue? If you enable the verbose logging you should see what the field value of the area path it is failing on.