OpsHub:ERROR对象引用未设置为对象的实例

时间:2021-06-03 16:58:28

We're checking into the option of moving to Visual Studio Online from our on premises TFS. Running the migration tool, it shows this error during validation:

我们正在检查从我们的内部TFS迁移到Visual Studio Online的选项。运行迁移工具时,它会在验证期间显示此错误:

ERROR Object reference not set to an instance of an object.

错误对象引用未设置为对象的实例。

I'm trying to migrate to a new setup on Visual Studio Online from our TFS 2013 server using version 1.2.0 of the migration tool.

我正在尝试使用1.2.0版的迁移工具从我们的TFS 2013服务器迁移到Visual Studio Online上的新设置。

Here is the full log entry:

这是完整的日志条目:

2015-05-12 13:21:40,383 [1] ERROR Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
   at TFSMigrationUI.ViewModel.MigrationSummeryViewModel.worker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e) in e:\OVSMUBranch\TFSMigrationUI\ViewModel\MigrationSummeryViewModel.cs:line 928
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

Any help would be greatly appreciated.

任何帮助将不胜感激。

1 个解决方案

#1


The Migration Utility expects "Project Collection Service Accounts" to be present in the VSO account Groups which is created by default when you create your VSO account, but due to some unknown issue some accounts created between the specific date this group was created as "Team Foundation Service Accounts" as in your case, so the migration utility was not able to find the desired group which resulted in the issue you are facing, you can continue the migration by creating a VSO group "Project Collection Service Accounts", add the user in this group which was used for authentication of VSO account for migration utility and make sure the newly created VSO group is a member of "Team Foundation Administrators" so you won't encounter any permission related issue.

迁移实用程序期望“项目收集服务帐户”存在于创建VSO帐户时默认创建的VSO帐户组中,但由于某些未知问题,某些帐户在该组创建的特定日期之间创建为“团队”基础服务帐户“与您的情况一样,因此迁移实用程序无法找到导致您遇到问题的所需组,您可以通过创建VSO组”项目收集服务帐户“继续迁移,添加用户在此组中,用于对迁移实用程序的VSO帐户进行身份验证,并确保新创建的VSO组是“Team Foundation管理员”的成员,因此您不会遇到任何与权限相关的问题。

#1


The Migration Utility expects "Project Collection Service Accounts" to be present in the VSO account Groups which is created by default when you create your VSO account, but due to some unknown issue some accounts created between the specific date this group was created as "Team Foundation Service Accounts" as in your case, so the migration utility was not able to find the desired group which resulted in the issue you are facing, you can continue the migration by creating a VSO group "Project Collection Service Accounts", add the user in this group which was used for authentication of VSO account for migration utility and make sure the newly created VSO group is a member of "Team Foundation Administrators" so you won't encounter any permission related issue.

迁移实用程序期望“项目收集服务帐户”存在于创建VSO帐户时默认创建的VSO帐户组中,但由于某些未知问题,某些帐户在该组创建的特定日期之间创建为“团队”基础服务帐户“与您的情况一样,因此迁移实用程序无法找到导致您遇到问题的所需组,您可以通过创建VSO组”项目收集服务帐户“继续迁移,添加用户在此组中,用于对迁移实用程序的VSO帐户进行身份验证,并确保新创建的VSO组是“Team Foundation管理员”的成员,因此您不会遇到任何与权限相关的问题。