错误TF400909：没有团队上下文。 （迁移变坏了吗？） [英] Error TF400909: There is no team context. (Migration gone bad?)

问题描述

您好，

我们刚刚将TFS 2012 U2 Express迁移到2013 Express。不幸的是，我们在这样做时遇到了很多问题，包括完全重新安装TFS。

we've just migrated our TFS 2012 U2 Express to 2013 Express. Unfortunately we faced a lot of problems while doing so including a complete reinstall of the TFS.

然后我们想要附上我们的旧2012系列，这只有在2012年临时修复之后才有可能实例通过tfsconfig / recover（在对话框中找不到数据库，2013年不再提供/ recover选项）。

We then wanted to attach our old 2012 Collection which was only possible after repairing the collection with a temporary 2012 instance via tfsconfig /recover (database wasn't found in the dialogue, /recover option isn't available anymore in 2013).

经过几个小时的工作，我们终于可以了 - 将集合附加到新的TFS 2013.从那时起，我们不再使用Web界面来重新附加集合。引发以下错误：

After a few hours of work we were able to finally re-attach the collection to the new TFS 2013. Since then we can't use the webinterface anymore for the re-attached collection. The following error get's thrown:

我们创建了一个新系列，一切都像魅力一样。

We've created a new collection and everything works like a charm.

似乎TFS2013没有升级旧版2012集合的数据库方案，因为缺少某些表，如tbl_Group，tbl_GroupMembership和tbl_GroupScope。

It seems the TFS2013 didn't upgrade the database scheme of the old 2012 collection, as some tables like tbl_Group, tbl_GroupMembership and tbl_GroupScope are missing.

有没有选项可以手动升级数据库？似乎也没有将现有项目复制/迁移到新集合的选项，因此我们需要在新集合中检查这些项目，但当然我们将完全签入
历史记录。

Is there any option to manually upgrade the database? It seems like there is also not an option to copy/migrate existing projects to a new collection so we need to check those projects in in a new collection but of course we will loose the complete check-in history.

亲切的问候，

Sven

Kind regards,
Sven

推荐答案

您好

我假设您进行了新的TFS 2013安装，然后尝试附加Team Project Collection。您必须使用tfsconfig / recover命令的原因是您在将项目集合移至TFS 2013之前未分离团队项目集合。

I assume you did a new installation of TFS 2013 and then tried to attach the Team Project Collection. The reason why you had to use the tfsconfig /recover command is that you did not detach the Team Project Collection before you moved it to TFS 2013.

我的建议是删除迁移的集合，即您使用tfsconfig / recover的那个。完成此操作后，在TFS 2012上打开Team Foundation Server管理控制台并分离集合。分离后，创建相应数据库的备份
并在TFS 2013上将其还原。然后在TFS 2013上打开Team Foundation Server管理控制台并附加该集合。因为它已被分离，所以它应该在那里可见。这将自动将
集合转换为TFS 2013数据库模式。如果你这样做，你根本不必使用tfsconfig。

My advise is that you drop the migrated collection, i.e. the one where you used tfsconfig /recover. Once you did this open the Team Foundation Server Administration Console on your TFS 2012 and detach the Collection. After it is detached, create a backup of the corresponding database and restore it on the TFS 2013. Then open Team Foundation Server Administration Console on your TFS 2013 and attach the collection. Because it has been detached it should be visible there. This will automatically convert the collection to the TFS 2013 database schema. If you do it that way you should not have to use tfsconfig at all.

分离集合是必要的，因为此操作从Tfs_Configuration数据库中提取信息并将其插入到Tfs_< CollectionName>中。数据库。没有它就不可能在具有不同
Tfs_Configration数据库的服务器上附加集合（因此你必须使用tfsconfig / recover）。

Detaching a collection is necessary because this operation extracts information from the Tfs_Configuration database and inserts it into the Tfs_<CollectionName> database. Without it will not be possible to attach the collection on a server with a different Tfs_Configration database (hence you had to use tfsconfig /recover).

但是，下次你做升级后，您可以先将所有数据库迁移到新环境，然后使用"升级"按钮。您的TFS配置中心中的选项，而不是使用"高级"。这是因为Tfs_Configuration和Tfs_< CollectionName>
合在一起，即Tfs_Configuration已经知道Tfs_< CollectionName>。

However, next time you do an upgrade you can first migrate all databases to the new environment and then use the "Upgrade" option in your TFS Configuration Center instead of using "Advanced". This works because Tfs_Configuration and Tfs_<CollectionName> fit together, i.e. Tfs_Configuration already knows about Tfs_<CollectionName>.

这篇关于错误TF400909：没有团队上下文。 （迁移变坏了吗？）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！