{"id":313,"date":"2013-05-26T19:29:00","date_gmt":"2013-05-26T17:29:00","guid":{"rendered":"http:\/\/sunauskas.com\/blog\/?p=313"},"modified":"2013-05-30T18:55:08","modified_gmt":"2013-05-30T16:55:08","slug":"build-error-after-migrating-to-tfs-2012-from-tfs-2010","status":"publish","type":"post","link":"https:\/\/sunauskas.com\/blog\/build-error-after-migrating-to-tfs-2012-from-tfs-2010\/","title":{"rendered":"Build error after migrating to TFS 2012 from TFS 2010"},"content":{"rendered":"

After migrating to TFS 2012 I came across one annoying issue: builds failing (randomly, as seen at first). The build error is not so informative, but it looks like possible migration issue:<\/p>\n

“Specified argument was out of the range of valid values. Parameter name: column.”<\/p>\n

\"TFS<\/a>If looking at the build log you could get an indirect hint what is going wrong:<\/p>\n

Associate Changesets and Work Items<\/em>
\nAnalyzing labels Client_2013.05.26.3 and Client_2013.05.26.4.<\/em><\/p>\n

The hint: if checked-in code is associated with work item – build will fail.<\/span><\/p>\n

But I didn’t notice the hint at first and tried several unsuccessful fixes. After failing I looked at the internet and found the description of the same issue: Upgrading your build definitions from TFS2010 to TFS2012<\/a><\/p>\n

The suggested quick fix\u00a0in the article is:<\/p>\n

The only workaround in the mean time is to turn off the UpdateWorkItems flag on the AssociateChangesetsAndWorkItems activity. This will cause workitems not to be associated with the build.<\/em><\/p>\n

So to do that, you don’t necessary need to modify your build template, which maybe would fix with multiple builds using the same process template. Rather you can go to individual build definition – process tab and set “Associate Changesets and Work Items” to false as shown below:<\/p>\n

\"TFS<\/a>So far, after two days builds are doing fine. Hopefully this quick fix will help you while waiting for the real fix from TFS team.<\/p>\n

Updated 2013-05-30<\/strong><\/p>\n

Bug will be fixed in Team Foundation Server 2012.3 (Update 3). More details about the bug<\/a>:<\/p>\n

In an environment that uses TFS 2012 and TFS Build Controller 2010, you check in a TFS 2010 build process template. When you queue a build that has associated work item and the work item has an associated changeset, the build fails with the following error message:<\/em><\/p>\n

\n
\n
Specified argument was out of the range of valid values. Parameter name: column<\/em><\/div>\n
<\/div>\n
<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

After migrating to TFS 2012 I came across one annoying issue: builds failing (randomly, as seen at first). The build error is not so informative, but it looks like possible migration issue: “Specified argument was out of the range of valid values. Parameter name: column.” If looking at the build log you could get an […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[38],"tags":[96,95,92,94,93],"class_list":["post-313","post","type-post","status-publish","format-standard","hentry","category-software-development","tag-net-4-0","tag-builds","tag-tfs","tag-tfs-2010","tag-tfs-2012"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t