Migrating from On-Premise TFS2012 to VSO TFS2013 with OpsHub

Question

I have been doing some mock migrations from our On-Premise TFS server up to VSO on-and-off for over a month now using TFS Integration Services, but it is full of quirks. Microsoft just announced a new tool that is free from OpsHub (Visual Studio Online Migration Utility). I'm trying it out but I'm receiving the following error which I never saw with the TFS Integration Tool:

OH-SCM-009: Error occurred while sync. No matching items found in $/Proj/Release/0.29/CodeSmith Templates on the server, or you do not have permission to access them. It seems changeset has items across team projects and all such projects are not selected in configuration. Please create new configuration selecting all such projects to allow processing of this changeset.

I can't find any information about this error code. Does anyone know what is causing this? Thank you.

I am only migrating source code, no work items.

I have tried "Retrying" a few times and when it starts it takes about 15 minutes before it fails again, but it made no progress. This particular changeset that it fails on was merging two branches.

Screenshots:

Any ideas?

EDIT 2014-05-14:

I am not able to choose a Project (below the Project Collection) for the source or destination - is this a bug? Oddly, when I do choose "Default Collection" for the destination, it only shows me the VSO hostname, but not the "\DefaultCollection" like the source does.

Not being able to choose the Project was a problem, because I wanted this to run against a "ProjectOpsHubTest" project, but instead it started appending changesets to my existing one that was successfully imported from TFS Integration Tools (fortunately we haven't made the final switch, so I've deleted it and started over). I still have the same problems with changeset 1550.

We have upgraded TFS several times since this checkin 1550 occured (I think 1550 was on TFS 2008, then we had 2010 I think, and now 2012), but I was able to do the migration just fine with TFS Integration Tools. I also don't think we've ever changed the Project name or ProjCollection names...

Answer 1

I have the same error, and message is not explicit I assume. Problem is that you do not have access to a specific Work item due to explicit permission. You could check wich file doesn't inherit permission using the following link. Personally, it save my day: https://blogs.msdn.microsoft.com/congyiw/2011/10/20/tfs-version-control-permissions-why-cant-i-branchrenamedelete-x/

Answer 2

From your description: "This particular changeset that it fails on was merging two branches."

If changeset has been merged from a different project that which is not selected while OpsHub Migration Utility then this issue may occur.

For example, you have two project source and branch. if you have changeset NNN which merge files from branch to source. And In OpsHub Migration Utility if you just select source project for migration Then you can get this error while processing NNN change set because OpsHub could not able to find from which changeset it is merged.

Another reason for this error is that the user configured to read the local TFS instance does not have admin privileges (and hence is not able to read the metadata details of this changeset). Please make sure that the user configured on the local TFS side (and also VSO side) has admin privileges.

You can delete project in VSO and create new configuration selecting all such projects to allow processing of dependent changeset.

Answer 3

This is usually due to nested branching issues. I do not believe that there is any way around it with the OpsHub tool limitations but you can get around it with the TFS Integration Tools.

If you cloak the problematic folder in the configuration file it will get past the error. Obviously though it has not added something to the server. You will, when it tries to branch from the cloaked folder, be asked to change the 'branch' to and 'add' to resolve the issue.