0

When migrating work item data I get the following error:

Configuration failed due to following reason(s). com.opshub.exceptions.DataVaIidationException: OpsHub-012017: Field mapping with name : 10.1.I.31XDefauItCoIIection to (vsaccount)_.visualstudio.com 1 10.1.I.31XDefauItCoIIection to (vsaccount)_.visualstudio.com II TFS Source 1411220907276 ALM TFS 1411220907277 _(project name)__. Test Suite already exists

I have not yet been able to migrate any of the team projects I have due to the error. Version control data works.

TechnoTim
  • 3,065
  • 1
  • 23
  • 28
  • Can you confirm that your local process template is identical to the VSO server? – MrHinsh - Martin Hinshelwood Sep 21 '14 at 07:14
  • Are you getting this error every time you are configuring migration? Or this has been captured once only. Can you please retry the full configuration process starting from selecting end points and projects, which may resolve this issue. – OpsHub Inc. Sep 22 '14 at 04:45
  • It happens every time, i have not yet once been able to migrate any work item data, source control data went fine. My templates local have not been modified, so they should match VSO. – TechnoTim Sep 22 '14 at 19:55
  • Can you please share all the log files from C:\Program Files\OpsHub Visual Studio Online Migration Utility\logs directory. Bundle all these files in zip and send it us on ovsmu@opshub.com, we will analyze logs and come back to you with resolution. – OpsHub Inc. Sep 23 '14 at 05:21
  • I have this exact problem as well. Any help would be great. – Steve Sep 24 '14 at 19:44
  • I sent the logs. Thank you – TechnoTim Sep 25 '14 at 00:45

1 Answers1

1

It seems to be a problem of the latest utility version (v1.0.0.6) when migrating projects from TFS 2013.3

I had the same problem but I've tryed to use an older version of the utility (v1.0) against TFS 2013.3 and it worked fine, I was able to migrate the data.

n3wt0n
  • 26
  • 1
  • Older version does not support sync of test suite, run, result entity. Which has been added in 1.0.0.5. This free utility is not supported with TFS2013.3. You can try it with TFS2013 (Not update 3). It should work as expected. – OpsHub Inc. Sep 26 '14 at 10:43
  • This solved my issue too. I have tried every version up until V1.0.005 and this was the first that successfully completed. – TechnoTim Jan 09 '15 at 01:39