For the August release, we are releasing patches for Azure DevOps Server 2019.0.1, TFS 2018 Update 3.2, and TFS 2017 Update 3.1. This month, there are no security fixes; these patches include functional changes.
Azure DevOps Server 2019.0.1: We added information to service connections to clarify that they are authorized for all pipelines by default.
TFS 2018 Update 3.2 and TFS 2017 Update 3.1: Fixed a bug where the Work Item Tracking Warehouse Sync stops syncing with an error: “TF221122: An error occurred running job Work Item Tracking Warehouse Sync for team project collection or Team Foundation server ATE. —> System.Data.SqlClient.SqlException: Cannot create compensating record. Missing historic data.”
Azure DevOps Server 2019.0.1 Patch 2
If you have Azure DevOps Server 2019, you should first update to Azure DevOps Server 2019.0.1. Once on 2019.0.1, install Azure DevOps Server 2019.0.1 Patch 2.
Verifying Installation
To verify if you have this update installed, you can check the version of the following file: [INSTALL_DIR]\Application Tier\Web Services\bin\Microsoft.TeamFoundation.Framework.Server.dll. Azure DevOps Server 2019 is installed to c:\Program Files\Azure DevOps Server 2019 by default.
After installing Azure DevOps Server 2019.0.1 Patch 2, the version will be 17.143.29207.6.
TFS 2018 Update 3.2 Patch 6
If you have TFS 2018 and you are seeing the TF221122 error in you Work Item Tracking Warehouse Sync job, you should first update to TFS 2018 Update 3.2. Once on Update 3.2, install TFS 2018 Update 3.2 Patch 6.
Verifying Installation
To verify if you have this update installed, you can check the version of the following file: [TFS_INSTALL_DIR]\Application Tier\Web Services\bin\Microsoft.TeamFoundation.WorkItemTracking.Web.dll. TFS 2018 is installed to c:\Program Files\Microsoft Team Foundation Server 2018 by default.
After installing TFS 2018 Update 3.2 Patch 6, the version will be 16.131.29131.4.
TFS 2017 Update 3.1 Patch 7
If you have TFS 2017 and you are seeing the TF221122 error in you Work Item Tracking Warehouse Sync job, you should first update to TFS 2017 Update 3.1. Once on Update 3.1, install TFS 2017 Update 3.1 Patch 7.
Verifying Installation
To verify if you have a patch installed, you can check the version of the following file: [TFS_INSTALL_DIR]\Application Tier\Web Services\bin\Microsoft.TeamFoundation.Server.WebAccess.Admin.dll. TFS 2017 is installed to c:\Program Files\Microsoft Team Foundation Server 15.0 by default.
After installing TFS 2017 Update 3.1 Patch 7, the version will be 15.117.29131.0.
Hello, we want to upgrade from TFS 2018 3.1 to TFS 2018 Update 3.2.6. So, the right path would be to update first to TFS 2018 Update 3.2 and then? Does patch 6 include all the other patches?
Thank you.
Yes, first upgrade to TFS 2018 Update 3.2 and then install Patch 6. Patch 6 includes all the previous patches.
Hi,
I’m getting the below error when trying to install TFS 2017 3.1 Patch 7:
Error patching files: System.UnauthorizedAccessException: Access to the path ‘C:\Program Files\Microsoft Team Foundation Server 15.0\Application Tier\Web Services\bin\Microsoft.TeamFoundation.Framework.Server.dll’ is denied.
Hi Nichole,
If you download the .exe file and run it from the command line as an administrator, do you get the same error?
Yes, i do…though for updating TFS 2015 4.2 patch 2. If you give all permissions to that folder or file, it will work, but then fails later trying to update the registry for the new version.
I found out this is an issue that will be fixed in the next release. As a workaround, you should run “net stop TeamFoundationSshService” before installing the patch, then run “net start TeamFoundationSshService” after the patch is installed.
Is there a Microsoft resource for instructions on upgrading TFS 2017 from Update 1 to Update 3.1? Even if there are general instructions on the steps needed, that would be great.
Hi Jon,
Here are the upgrade instructions: https://docs.microsoft.com/en-us/azure/devops/server/upgrade/get-started?view=azure-devops.
The upgrade from TFS 2017 Update 1 to Update 3.1 is fairly quick and has the same system requirements, so you don’t need to worry about upgrading the OS or SQL.
I am about to upgrade our QA envoirnment from TFS2018 Update 3 to the latest. Do I need to install 2019.0.1 first before this patch? Or does this patch contain all the bits for the upgrade? Also I need to do an offline install of it and I am usign the following command to do so "azuredevopsserver2019.0.1.exe /Layout E:\Staging\DevOps201901" Will this work for the patch? And one last question is the the officall realease now? ...
Hi Craig,
Yes, you need to install 2019.0.1 first. The patch only includes the files that changed, not the whole upgrade.
To do an offline install, you can download the patch .exe file locally and install it offline. The patch is small, so the .exe includes everything and doesn’t need an internet connection to install.
Great thanks 2019.0.1is that the offical production release for on Prem use? I was just confirming that verion (2019.0.1) was not an Release Candidiate and an official release version.
Yes, 2019.0.1 is an official production release.
This comment has been deleted.
@Erin, are these patches included in the Azure DevOps Server 2019 Update 1 RC2?
After our upgrade from TFS 2018 Update 2 to Azure DevOps Server 2019 Update 1 RC2 in PROD, we are seeing this error for some users “VS402647: Widget took too long to load”. Do you know when are the first set of patches be coming in for Azure DevOps Server 2019 Update 1 RC2 and hope that this issue has already been reported and fixed?
Just reporting that after talking Erin, we applied Update 1, https://devblogs.microsoft.com/devops/now-available-azure-devops-server-2019-update-1-rtw/ and that fixed “VS402647: Widget took too long to load” issue.
Hi Scott,
They are not in RC2, but will be in the final release. If you need a fix before the final release (expected next week), send me a mail at egeaney@microsoft.com.