{"id":113,"date":"2013-11-08T14:29:22","date_gmt":"2013-11-08T14:29:22","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/buckh\/2013\/11\/08\/updated-team-foundation-server-2013-download-addressing-web-and-installation-path-issues\/"},"modified":"2013-11-08T14:29:22","modified_gmt":"2013-11-08T14:29:22","slug":"updated-team-foundation-server-2013-download-addressing-web-and-installation-path-issues","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/buckh\/updated-team-foundation-server-2013-download-addressing-web-and-installation-path-issues\/","title":{"rendered":"Updated Team Foundation Server 2013 download addressing web and installation path issues"},"content":{"rendered":"

Today we have updated the TFS 2013 installation packages both on the web download page<\/strong><\/a> <\/strong>and in MSDN subscriber downloads<\/a>. The reason is that we found two bugs that we wanted to address broadly. We\u2019ve made changes to be able to catch these types of issues in the future.<\/p>\n

Here are details on the two fixes.<\/p>\n

Fixed: Red error box when using Code (version control) in the web UI<\/strong><\/p>\n

In the case of upgrading from a prior version of TFS to TFS 2013 RTM, you will see a big error box that says \u201cError in the application\u201d when using the Code section in the web UI (for example, viewing History). The reason is that we had a bug that was introduced shortly before RTM where the version number for the discussion service, which is the back end for the code review feature, is not set correctly (it was left as a 5 and should have been a 6). As a result, what was returned by the server was InvalidServiceVersionException. Users had reported this in a couple of forum threads (here<\/a> and here<\/a>) where we had provided a simple SQL script to fix the issue until this updated download was available.<\/p>\n

\"clip_image001\"<\/a><\/p>\n

For anyone who has the original RTM <\/strong>installed (not the new release mentioned above) and has this issue, the fix from Vladimir will correctly address the issue, or you can contact customer support who will be able to help you. You would need to run this SQL script on each collection database. Please do not modify this SQL script or make any other changes to the TFS databases.<\/p>\n

\n

IF EXISTS ( SELECT *
            FROM    sys.extended_properties
            WHERE   name = ‘TFS_SERVICE_LEVEL’
                    AND value = ‘Dev12.M53’)
   AND
   EXISTS ( SELECT *
            FROM    sys.extended_properties
            WHERE   name = ‘TFS_DATABASE_TYPE’
                    AND value = ‘Collection’)
BEGIN
    EXEC prc_SetServiceVersion ‘Discussion’, 6
END<\/p>\n<\/blockquote>\n

Fixed: Unable to install into a custom path<\/strong><\/p>\n

When you install TFS 2013, you do not have to uninstall TFS 2012 \u2013 the installer will take care of it for you and preserve your settings and provides a much better experience for upgrading databases compared to a patch. This was a feature we introduced with TFS 2012 specifically for easy installation of the updates for TFS 2012. There was a bug in the original TFS 2013 RTM release where if your installation for your TFS 2012 installation did not have \u201c11\u201d in the path (for example, d:\\tfs) that you would not be able to change path and the installation would leave your TFS inoperable if you went forward with the installation (if this has happened to you, contact customer support, and we\u2019ll get it fixed for you).<\/p>\n

For both of these issues, we have learned from them and now have checks in place to catch them in the future.<\/p>\n

Follow me on Twitter at twitter.com\/tfsbuck<\/a><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Today we have updated the TFS 2013 installation packages both on the web download page and in MSDN subscriber downloads. The reason is that we found two bugs that we wanted to address broadly. We\u2019ve made changes to be able to catch these types of issues in the future. Here are details on the two fixes. […]<\/p>\n","protected":false},"author":94,"featured_media":10268,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[8,13],"class_list":["post-113","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-team-foundation","tag-tfs-2013"],"acf":[],"blog_post_summary":"

Today we have updated the TFS 2013 installation packages both on the web download page and in MSDN subscriber downloads. The reason is that we found two bugs that we wanted to address broadly. We\u2019ve made changes to be able to catch these types of issues in the future. Here are details on the two fixes. […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/posts\/113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/users\/94"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/comments?post=113"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/posts\/113\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/media\/10268"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/media?parent=113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/categories?post=113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/tags?post=113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}