TFS 2010 migration to TFSOnline - OpsHub - Project template error

0
votes

I'm trying to migrate on-premises TFS 2010 projects to TFSOnline.

I'm getting "'<project name>' is missing in **********\DefaultCollection. Create a new project by the same name and with the 'Microsoft Visual Studio Scrum' template in your ********\DefaultCollection to continue."

Appreciate any help on this issue.

Here is a screenshot of the project in TFSOnline

Here is a screenshot of the OpsHub error

1
tfsmigrationopshubazure-devops
Did you try clicking "Refresh" button to refresh the projects? - Eddie Chen - MSFT
Access rights can be the issue. Through which user have you created the end point on OVSMU tool? Does he have rights to access that particular project in VSTS? - OpsHub Inc.
Thanks Eddie but refresh didn't work. Looks like an issue with user accounts. We had one account for admin tasks and one with the regular access. Once I logged out of the regular account and logged in with the admin account I'm not getting that error anymore. But after user mapping I'm running into "Permission needed for logged in user in destination" and "Template customization or Template mismatch error". When I expand on the Permission error it shows that I'm logged in as the regular account and not the admin account. In my VS2015 and also in the browser I'm logged in as the admin. - Nandha Murugesan
I don't see any user login option in OpsHub, how do I make OpsHub use the admin account? - Nandha Murugesan
Update at 02/01/16 1812: I was able to solve the "Permission needed..." error by following this article (stackoverflow.com/questions/26109932/…). However I'm still getting "Template customization or Template mismatch error". Source project is in TFS2010 and uses the Scrum template (I verified this by trying to create a new workitem and I got Bug, Product Backlog, Sprint etc.) and the new team project in TFSOnline also uses the Scrum template. - Nandha Murugesan

1 Answers

0
votes

Issue here mentioned in the description was because of the user is not having enough permission on that project. Changing to the administrator account or user having permissions on that project resolved the issue.

TF30042: The database is full. Contact your Team Foundation Server administrator.

The above is because of your source TFS instance database is full.