Team Foundation Server 2015 Update 2.1 Fixed Bugs



Microsoft released Team Foundation Server 2015 Update 2.1 on May 04, 2016. This article lists the fixed bugs for Team Foundation Server 2015 Update 2.1.

To see the full list of Team Foundation Server 2015 products and download a product, go to the Downloads page.

Team Foundation Server 2015 Update 2.1 details

To discover what's new in Team Foundation Server 2015 Update 2.1, see the Team Foundation Server 2015 release notes.

Fixed bugs

Agile Tools

  • On the product backlog, if the mapping view is off and the Add Panel (quick create) work item isn't open, you receive an error message when you bulk edit work items by selecting Edit selected work items(s) in the context menu. If you dismiss the error message and try again, the operation succeeds.
    The error message resembles the following:
Cannot read property ‘-105’ of undefined  
  • In Internet Explorer, you cannot use the Maximize button to maximize a long text field or use the Save button after you edit the text in a work item. You receive the following error message:
    Script5007: Unable to get property 'document' of undefined or null reference.  
  • When you use the Client Object Model (or any of the tools that use Client Object model, such as Visual Studio or your custom tool), you cannot save large attachments to work items, even though the same attachments work successfully together with web-access forms.

  • When you use hyperlinks in work item templates, they don't appear in web access. The hyperlinks work correctly in Visual Studio.

  • In Safari and Chrome under some circumstances, if you go to the backlog, right-click a work item, and then try to assign or move to an iteration, the menu doesn't appear.


  • In Simplified Chinese, Traditional Chinese, Japanese, and Korean languages model, the Build feature does not work.

  • During Test Results publishing, XAML builds may cause failures because of the COMException in BeginDataStoreInit() function. This is resolved by resetting the TFS cache on the build server.

  • If you have a build definition that has a gated check-in trigger, and you create a draft of that same definition and then try to trigger a build by making a check-in, you receive the following error message:

    Your check-in validation could not be queued for build definition. Details: An item with the same key has already been added.  
  • If you create a Maven build task, and you use SonarQube together with Maven, you see your credential in the build. This issue occurs only if you turn on debug and have a password that includes a backslash () or a double quotation mark (").

  • After you upgrade to Team Foundation Server 2015 Update 2, you may see performance degradation because of QueryBuildInformation.

  • Extensions that have cross-platform Build tasks do not work.


  • The Backup tool fails if the tlog backup is longer than 100 minutes.

  • You cannot upgrade if IIS_USRS does not have the "Impersonate a client after authentication" user right. During readiness checks in the Upgrade Wizard, you receive the following error message:

    VS402818:The built-in security group IIS_IUSRS does not have the required "Impersonate a client after authentication" user right. Grant this user right to the IIS_IUSRS group, and then re-run the readiness check. For more information, see [](  
  • In the activity log, the parameters are blank for some failed commands.

  • "Trial" has been removed from the name of the download from

  • Web experiences do not work correctly if a TFS server is configured to be accessible through both HTTP and HTTPS.

Version Control:

  • An event log error may be logged every time that a user leaves a code comment on changesets or shelvesets. The following event log entry appears in the event log:
TF53010: The following error has occurred in a Team Foundation component or extension:   
 Date (UTC): <Event date>  
 Machine: TFS01   
 Application Domain: /LM/W3SVC/2/ROOT/tfs-1-131050129800124161   
 Assembly: Microsoft.TeamFoundation.Framework.Server, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v4.0.30319   
 Service Host: ed43e969-7a17-4d30-b27c-cee1283e5c64 (TourOperators)   
 Process Details:   
 Process Name: w3wp   
 Process Id: 3884   
 Thread Id: 1680   
  • Team Foundation Version Control displays a GUID in the usernames in code review email messages.

  • If there are multiple build definitions configured for the repository, the status badge might show the wrong build definition name for the build.

  • When you create a pull request, the associated work items list includes only the first 25 commits instead of inspecting all the commits in the pull request.

  • When you add a link from a work item to a version control item at latest, the link is broken and appears as the following: "vstfs:///VersionControl/LatestItemVersion/undefined"

  • In Team Foundation Version Control, if you branch across projects or move a branch to another project, your branch may lose its parent relationship.

Test Tools:

  • When you upgrade Team Foundation Server 2015 Update 2 RC to Update 2 RTW, you cannot see the option to use Test Plans in the "Run Functional Tests" task.


  • Extensions that work in Visual Studio Team Services and deliver content (HTML, JavaScript, CSS, and so on) from their own service or domain may not work in on-premises Team Foundation Server. You may receive the following error message:
resource from origin <service endpoint URL> has been blocked from loading by cross-origin Resource Sharing policy:  

Release Management:

  • The email option in the release management approvals are not enabled if there is more than one approver in an environment.

  • Security in release environments are too strict. Denying access to one environment may restrict it in others.


  • You may not consistently receive code review alerts.
  • If your team project name contains a space, your notifications may have invalid links.

More information

How to download Microsoft support files

Updates for other products in the Team Foundation Server family can be found on the Downloads website.


For detailed system requirements, see the TFS requirements and compatibility page.

Restart requirement

You may have to restart your computer after you install this package.

Software requirement

To apply this update, you must have Team Foundation Server 2015 installed on your computer.

Supported architectures

  • 32-bit (x86)
  • 64-bit (x64) (WOW)

Applies to

  • Team Foundation Server 2015
  • Team Explorer Everywhere 2015
  • Team Foundation Server Express 2015
  • Team Foundation Server for Project Server Extensions 2015


The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.