Updated Team Foundation Server 2013 download addressing web and installation path issues

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’ve made changes to be able to catch these types of issues in the future.

Here are details on the two fixes.

Fixed: Red error box when using Code (version control) in the web UI

In the case of upgrading from a prior version of TFS to TFS 2013 RTM, you will see a big error box that says “Error in the application” 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 and here) where we had provided a simple SQL script to fix the issue until this updated download was available.


For anyone who has the original RTM 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.

            FROM    sys.extended_properties
            WHERE   name = 'TFS_SERVICE_LEVEL'
                    AND value = 'Dev12.M53')
            FROM    sys.extended_properties
            WHERE   name = 'TFS_DATABASE_TYPE'
                    AND value = 'Collection')
    EXEC prc_SetServiceVersion 'Discussion', 6

Fixed: Unable to install into a custom path

When you install TFS 2013, you do not have to uninstall TFS 2012 – 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 “11” 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’ll get it fixed for you).

For both of these issues, we have learned from them and now have checks in place to catch them in the future.

Follow me on Twitter at twitter.com/tfsbuck

Comments (7)

  1. Mikael Nygaard says:

    Saved me alot of time trying to figure out this problem, so thx. But I think you should get Brian Harry to write a blogpost about the issue, since this is often the primary source for TFS related news.

  2. Harry says:

    Dear Buck,

    the TFS 2013 ISO SHA-1 file hash did ***NOT*** match the one listed in MSDN subscriber downloads.

    While all others match, the TFS 2013 installation packages listed here (http://www.visualstudio.com/…/download-visual-studio-vs) and here (http://www.microsoft.com/…/details.aspx) are still buggy.

  3. Jeff Beehler (MSFT) says:

    @Harry – I just downloaded each of the files you mentioned above and they each checked out with the associated SHA-1 values listed with the downloads:

       – http://www.visualstudio.com/…/download-visual-studio-vs: AAC270FDD1B0018F5183F012D8F32A06D8E30C65

       – http://www.microsoft.com/…/details.aspx 2E00D67CEA533C1E18D557F6F72B22353D05C353

    Note that these hash values are different than what's posted on MSDN subscriber downloads as the product keys are different.  

    If you continue to have problems, please feel free to contact me with more details at jeffbe AT microsoft DOT com.



  4. Harry says:

    Jeff, please note that all other products i've compared match the hash listed on MSDN. Compare the VS pro/premium/ultimate hashes yourself. The keys are not part of the product (as for 2012 editions), they are 30 day trial keys and you get your personal key in your msdn subscriber account.

  5. Jeff Beehler (MSFT) says:

    @Harry – that's quite interesting and somewhat surprising to me.  I've asked this question to my team because now I'm confused why we treat these VS and TFS differently in this regard. I can confirm that the two different version of TFS that are posted on MSDN and the download center are from the same build even though the installers are slightly different. As soon as I learn more, I'll come back here with a more detailed explanation. Since it's Thanksgiving in the US, I expect it'll take a few days for the team to reply.  



  6. Jeff Beehler (MSFT) says:

    @Harry – After further digging here, it looks like both you and I are right.  For VS SKUs, in part because of our new online signin features (as described here: blogs.msdn.com/…/welcome-sign-in-to-visual-studio.aspx), we provide trial versions in all public channels and then deliver license keys through the signin experience.  Since that's not a feature for TFS, we continue to provide versions keyed differently on MSDN and the download center as you've noticed.  

    So, the versions of both VS and TFS on our various channels are up to date and correct.  


  7. Javier Moreno says:

    Awesome!! The SQL Script worked perfectly!


Skip to main content