December patches for Azure DevOps Server
This month, we are releasing fixes that impact our self-hosted product, Azure DevOps Server.
The following will be fixed with this patch:
- Fix work item macro for queries with “Contains Words”. Previously, queries were returning incorrect results for values that contained a line break.
- Increase limits for Maven package version character length.
- Localization issue for custom work items layout states.
- Localization issue in email notification template.
- Issue with console logs getting truncated when there are multiple identical links in a row.
- Issue with NOTSAMEAS rules evaluation when multiple NOTSAMEAS rules were defined for a field.
Azure DevOps Server 2020.1.1 Patch 3
If you have Azure DevOps Server 2020.1.1, you should install Azure DevOps Server 2020.1.1 Patch 3. Check out the release notes for more details.
Verifying Installation
-
Option 1: Run
devops2020.1.1patch3.exe CheckInstall
, devops2020.1.1patch3.exe is the file that is downloaded from the link above. The output of the command will either say that the patch has been installed, or that is not installed. -
Option 2: Check the version of the following file:
[INSTALL_DIR]\Azure DevOps Server 2020\Application Tier\bin\Microsoft.Teamfoundation.Framework.Server.dll
. Azure DevOps Server 2020.1.1 is installed toc:\Program Files\Azure DevOps Server 2020
by default. After installing Azure DevOps Server 2020.1.1 Patch 3, the version will be 18.181.32011.3.
Azure DevOps Server 2020.0.1 Patch 8
If you have Azure DevOps Server 2020.0.1, you should install Azure DevOps Server 2020.0.1 Patch 8. Check out the release notes for more details.
Verifying Installation
-
Option 1: Run
devops2020.0.1patch8.exe CheckInstall
, devops2020.0.1patch8.exe is the file that is downloaded from the link above. The output of the command will either say that the patch has been installed, or that is not installed. -
Option 2: Check the version of the following file:
[INSTALL_DIR]\Azure DevOps Server 2020\Application Tier\bin\Microsoft.Teamfoundation.Framework.Server.dll
. Azure DevOps Server 2020.0.1 is installed toc:\Program Files\Azure DevOps Server 2020
by default. After installing Azure DevOps Server 2020.0.1 Patch 8, the version will be 18.170.32011.2.
Azure DevOps Server 2019.1.1 Patch 12
If you have Azure DevOps Server 2019 Update 1.1, you should install Azure DevOps Server 2019 Update 1.1 Patch 12. Check out the release notes for more details
Verifying Installation
-
Option 1: Run
devops2019.1.1patch12.exe CheckInstall
.devops2019.1.1patch12.exe
is the file that is downloaded from the link above. The output of the command will either say that the patch has been installed, or that is not installed. -
Option 2: Check the version of the following file:
[INSTALL_DIR]\Azure DevOps Server 2019\Application Tier\Web Services\bin\Microsoft.VisualStudio.Services.Feed.Server.dll
. Azure DevOps Server 2019 is installed toc:\Program Files\Azure DevOps Server 2019
by default. After installing Azure DevOps Server 2019.1.1 Patch 12, the version will be 17.153.32011.1.
41 comments
Does your team have any news about Azure DevOps Server 2022?
Hi Nikita, we plan to release on Q1 of 2022.
is a fix for Log4j (ElasticSearch for Code Search functionality) included or will there be a another patch in the next 2-3 days ?
Hi Daniel, we didn’t include patches for the log4j vulnerability. We will continue to update the Azure DevOps (and Azure DevOps Server) and the log4j vulnerability blog post with details. You can subscribe to the patches category to receive updates.
Hi Gloridel,
Are the SAAS versions which MS manages patched?
After updating to Patch 8 for AzureDevOps 2020.0.1 we are no longer able to receive email notifications when using @mentions in our user stories and bugs. dewoweb
anyone else having this issue or found a way to resolve?
https://developercommunity.visualstudio.com/t/Use-mention-in-work-items-no-working-af/1615815#T-N1637342
Am trying to install the December patch, we have 18.181.31527.1 but the patch keeps saying “This patch does not apply to Azure DevOps Server version 18.181.31527.1.”
I am getting the same issue. Patch output is the following:
Hi Kevin, it looks like you are being impacted by the issue reported in this blog post https://devblogs.microsoft.com/devops/azure-devops-server-2020-1-1-rtw-now-available/
The initial release of 2020.1.1 was buggy and had been replaced after a few days and you should reinstall the new version again before applying any patches.
Thank you Daniel for providing guidance 🙂
We, dewoweb.com are one of the leading third-party technical assistance providers for web design. dewoweb All the images, trademarks, and logos are used for education purposes only. We provide assistance only at customers’ requests.
For Further Information connect with Us:
Call Us:+98-21-7105-7477
write Us:info@dewoweb.com
Visit Us: https://www.dewoweb.com/
Hi Kevin, like Daniel mention it seems like your install is being impacted by an issue after upgrading from 2020.1 patch 2 to 2020.1.1. The Azure DevOps Server 2020.1.1 blog post has more details.
Thank you. Re-applying 2020.1.1 seems to have worked.
Hi Trent, it seems like your install is being impacted by an issue after upgrading from 2020.1 patch 2 to 2020.1.1. The Azure DevOps Server 2020.1.1 blog post has more details.
Thanks – I updated devops server again and that seems to have resolved it.
Thank you
Does this patch add support for pipeline builds using Visual Studio 2022? We keep getting the following error after we upgraded our build to .NET6
I upgraded the build agent to v2.195.2 but it did not help. We are using the VSBuild@1 task and have tried passing ‘17.0’ and ‘latest’ but both still run with VS2019.
Both VisualStudio_17.0 and MSBuild_17.0 show up under the agent capabilities tab and are pointing to VS2022. The yaml task for VSBuild@1 is showing as 1.166.2 in the logs. Does this need to be updated?
If anyone else has this issue I followed the instructions mentioned in the link below and it seems to be working.
https://github.com/microsoft/azure-pipelines-agent/issues/3567#issuecomment-947764654
After manually updating the VSBuild@1 task it shows as 1.192.3 in the logs and uses VS2022.
Thank you, Kevin, for sharing your findings and providing guidance.
Hi Gloridel
We are facing the same problem and wondering why the MSBuild, VSBuild and VSTest build tasks is created so that they look for a hardcoded set of Visual studio version that were know at compile time, instead of relying on vswhere to find either a specifically specified version or latest. That would work in cases where no breaking changes have been made.
Hi everyone, i was facing a problem that may be hard for me.
I can’t solve the “Security Updates for Microsoft Team Foundation Server and zure DevOps Server (April 2021)”
I had installed the patch 11 and double checked the “…..Feed.Server.dll” was version 17.153.31707.1
Azure Resource Group Deployment V2 also been uplaoded (I guess so)
Any else i need to install or how can i check?
Hi San, it looks like you are being impacted by the issue reported in this blog post https://devblogs.microsoft.com/devops/azure-devops-server-2020-1-1-rtw-now-available/
The initial release of 2020.1.1 was buggy and had been replaced after a few days and you should reinstall the new version again before applying any patches.
Hi Daniel, is the issue following the blog post that you share also impacted version 2019.1.1?? Because i’m using version 2019.1.1 in a intranet environment. Thanks.
After updating to Patch 8 for AzureDevOps 2020.0.1 we are no longer able to receive email notifications when using @funigma in our user stories and bugs.
anyone else having this issue or found a way to resolve
https://developercommunity.visualstudio.com/t/Use-mention-in-work-items-no-working-af/1615815#T-N1637342
Log4j/ElasticSearch Vulnerability in Microsoft Visual Studio Team Foundation Server
Gloridel,
Sorry if this is a repetitive inquiry. We use Microsoft Visual Studio Team Foundation Server Version 16.131.28601.4 which had the vulnerable Log4j library located in the directory C:\Program Files\Microsoft Team Foundation Server 2018\Search\ES\elasticsearchv5\lib. We have manually patched the vulnerability. As a point of clarification, does Microsoft intend to publish an update to patch on-premises versions of TFS?
Hi Chris, please see the guidance provided in the Azure DevOps (and Azure DevOps Server) and the log4j vulnerability.
We will continue to post updates in the blog as we learn more.
After updating to Patch 8 for AzureDevOps 2020.0.1 we are no longer able to receive email notifications when using @mentions in our user stories and bugs.
anyone else having this issue or found a way to resolve?
Yes, we have the same problem since installation of 2020.1.1 Patch 3. This is also discussed here:
https://developercommunity.visualstudio.com/t/Use-mention-in-work-items-no-working-af/1615815
Hi Michael, we apologize for the impact this may have caused. We have a fix for the issue and plan to release with the next patch.
Developer Community Ticket
Hi Joe, we apologize for the impact this may have caused. We have a fix for the issue and plan to release with the next patch.
Developer Community Ticket
Hi, i cannot update my Azure DevOps server, the log said: This patch does not apply to Azure DevOps Server version 18.181.31230.2
I tried with all patches from this site https://docs.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2020?view=azure-devops#azure-devops-server-2020-patch-1-date-december-8-2020, and i got the same issue. Can you tell me what should I do?
Hi Linh. Based on the version number, you have Azure DevOps Server 2020.1. You should install Azure DevOps Server 2020.1.1 from our download page and then apply the patch.
Hi Gloridel,
Any update on this bug? https://developercommunity.visualstudio.com/t/Use-mention-in-work-items-no-working-af/1615815
I was about to apply the update but just saw people having this issue which is a show stopper.
Hi Kevin, we plan to fix @mentions email notifications with our next patch.
Hi Gloridel,
Is there any public target date for this fix? We’re also struggling due to this problem…
Dear Gloridel, I am very happy with your posts on this blog. All of your posts are informative and come from experience. Good lock.
طراØÛŒ سایت