blocks|key|3040790|text|我怀疑更改集中的项以某种方式使用了两次相同的ID，因此第一次插入没有问题，但第二次插入会导致冲突。但是，因为它们在同一个事务中，所以第一次插入被回滚，之后您在tbl_PendingDelta中看不到任何东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3040791|有关此问题的另一个示例，请参阅http://connect.microsoft.com/VisualStudio/feedback/details/693450/tfs-2010-violation-of-primary-key-constraint-pk-tbl-pendingdelta。|offset|length|3040792|我觉得你应该跟Microsoft+Product+Support+Services说这事。|3040793|entityMap|0|LINK|mutability|MUTABLE|url|http://connect.microsoft.com/VisualStudio/feedback/details/693450/tfs-2010-violation-of-primary-key-constraint-pk-tbl-pendingdelta|1|http://support.microsoft.com/^0|0|F|3M|0|0|7|Y|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

I suspect that somehow the items in the change set use the same ID twice, so the first INSERT is fine but the second will cause the violation. However, since they're in the same transaction, the first INSERT is rolled back and you don't see anything in tbl_PendingDelta afterwards.

See <a href="http://connect.microsoft.com/VisualStudio/feedback/details/693450/tfs-2010-violation-of-primary-key-constraint-pk-tbl-pendingdelta" rel="nofollow">http://connect.microsoft.com/VisualStudio/feedback/details/693450/tfs-2010-violation-of-primary-key-constraint-pk-tbl-pendingdelta</a> for another example of this issue.

I think you should take this up with <a href="http://support.microsoft.com/" rel="nofollow">Microsoft Product Support Services</a>.

blocks|key|3040802|text|我的解决方案是排除罪魁祸首，并检查其余的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3040803|然后我检查了罪魁祸首。|3040804|(如果您有门控检入，则可能需要先将其关闭。)|3040805|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

My solution was to exclude the culprit and check in the rest. 
I then checked in the culprit. 

( If you have a gated checkin you might have to turn that off first. )

blocks|key|2828066|text|我也遇到过类似的事情。以前，我回滚了一些更改，并再次使用相同的名称在解决方案和项目文件中引入这些更改。我发现的问题是sql脚本重命名不在Sql.proj文件中，我需要添加它，然后关闭解决方案以接受对项目文件的更改。一旦我更正了重命名，确保它在项目文件中，然后我就可以将其签入。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2828067|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had something similar happen. Previously I had rolled back some changes and was reintroducing those changes in the solution and project files again with the same name. The problem that I found was a sql script rename was not in the Sql.proj file and I needed to add it and then close the solution to accept the changes to the proj file. Once I corrected the rename, made sure that it was in the project file, then I could check it in.

blocks|key|3040862|text|这似乎与工作空间有关。我在一个工作区中遇到了这个问题，但我能够在另一个工作区中执行触发错误的源代码控制操作(回滚，以前的回滚)，没有任何问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3040863|重新创建您的工作区可能是一个解决方案。|3040864|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

This seems to be related to the workspace. I had this problem on one workspace but was able to perform the source control operation that triggered the error (rollback a previous rollback) in a different workspace without any problems.

Recreating your workspace might be a solution.

blocks|key|198683|text|我重命名了我的工作区文件夹(顶层包含$tf)，然后在我想要的分支上执行了get+latest，然后unshelve起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|198684|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I renamed my workspace folder (the top level containing $tf) then did a get latest on the branch I wanted, then the unshelve worked.

blocks|key|198692|text|1.从“文件”菜单中，单击“源代码管理”，然后单击“工作区”。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|198693|2.在Manage++workspace+对话框的Name列下，突出显示要删除的工作区，然后单击Remove。|198694|3.在确认对话框中，单击OK。|198695|你的工作已经完成了。|198696|然后再次映射你的解决方案，然后你就可以正常工作了。|198697|entityMap^0|4|2|E|5|Q|3|0|A|B|1C|6|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|13|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|O|$]]

1.From the File menu, click Source Control, and then click Workspaces.

2.In Manage Workspaces dialog box, under the Name column, highlight the workspace that you want to remove, and then click Remove.

3.In the Confirmation dialog box, click OK.

your work is done.

And map your solution again then you can work properly.

I'm trying to check in a file, and one file (one and only one file) has a problem while being checked in. This file has been deleted many times and undeleted (due to a conflict in architecture and design) and now TFS throws this error:

<blockquote>
 TF246021: An error occurred while processing your request. Technical
 information (for administrator): SQL Server Error: 500200
</blockquote>

As we saw the log file of the Event Viewer, the problem is:

<blockquote>
 Violation of PRIMARY KEY constraint 'PK_tbl_PendingDelta'. Cannot
 insert duplicate key in object 'dbo.tbl_PendingDelta'.
</blockquote>

However, there is no pending changes in <code>dbo.tbl_PendingDelta</code>. In fact, this table is completely empty. What's wrong here? How can I solve this problem?

How to solve TFS error TF246021 and SQL Server error 500200 while checking in?

日志文件

SQL Server

我正在尝试签入文件，但有一个文件(且只有一个文件)在签入时出现问题。此文件已被多次删除且未删除(由于架构和设计中的冲突)，现在TFS抛出此错误： TF246021:处理您的请求时出错。技术信息(供管理员使用)：SQL Server错误: 500200正如我们看到的事件查看器的日志文件一样，问题是：违反主键约束'PK_t...

问如何解决签入时出现的TFS错误TF246021和SQL Server错误500200？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何解决签入时出现的TFS错误TF246021和SQL Server错误500200？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何解决签入时出现的TFS错误TF246021和SQL Server错误500200？
EN