24 comments

Discussion is closed. Login to edit/delete existing comments.

• 

  Jacob Konopacki November 18, 2019 0

  Collapse this comment Copy link

  I am seeing the following issues when trying to apply Azure DevOps Server 2019.0.1 Patch 3:

  Zipping “C:\Program Files\Azure DevOps Server 2019\Application Tier\Web Services\bin\Microsoft.TeamFoundation.Framework.Server.dll” into “C:\Program Files\Azure DevOps Server 2019\Backup\2019-11-18_14-25-55.zip”
  Error patching files: System.UnauthorizedAccessException: Access to the path ‘C:\Program Files\Azure DevOps Server 2019\Application Tier\Web Services\bin\Microsoft.TeamFoundation.Framework.Server.dll’ is denied.
  at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
  at System.IO.File.InternalDelete(String path, Boolean checkHost)
  at Microsoft.TeamFoundation.AzureDevOpsPatch.AzureDevOpsPatch.UpdateFiles(Logger log)

  Please help!

  • 

    Jacob Konopacki November 22, 2019 0

    Collapse this comment Copy link

    Help! Anyone?

    • 

      Gloridel Morales November 22, 2019 0

      Collapse this comment Copy link

      Hi Jacob, try the following:
      • First thing to try is to stop IIS before running the patch. Run “iisreset stop”, run the patch exe and then run “iisreset start”. This will solve the problem if the issue is IIS holding the file open.
      • The other thing that can hold the file open is virus scanners. You can exclude the “C:\Program Files\Azure DevOps Server 2019” folder from virus scans.

    • 

      Jacob Konopacki December 9, 2019 0

      Collapse this comment Copy link

      Hi Gloridel,

      First sorry for the delay…its been crazy at work and thank you for your inputs.

      I tried both approaches and I am still getting the same error…any other ideas?

    • 

      Bhombal, Rehan February 28, 2020 0

      Collapse this comment Copy link

      Hi Jacob,

      Where you able to resolve this? I am facing the same issue.
      Also do you know the location of log files.

      Rehan

  • 

    Akash Bagh November 18, 2019 0

    Collapse this comment Copy link

    this comment has been deleted.

• 

  super tang October 23, 2019 0

  Collapse this comment Copy link

  Hi Erin,

  I installed TFS 2018 Update 3.2 Patch 7 for our TFS server 2018, but unfortunately, the version still is 16.131.28601.4 (Tfs2018.Update3.2).
  According to your blog, the version should be 16.131.29226.5 if succeed .
  Checked the patch log. No useful message there.
  Thanks.

• 

  Daniel Steiner October 4, 2019 0

  Collapse this comment Copy link

  after installing Azure Devops Server 2019 Update 1 Patch 1 I noticed that it takes a lot more resources than previous version. I found a bug report that Azure Devops Server 2019 Update 1 uses more resources than RTM and therefore I uninstalled Azure Devops Server 2019 Update 1 via Control Panel (as well as the databases in the SQL Server) and installed Azure DevOps Server 2019 RTM followed by installation of 2019.0.1 which both version did require less resources than Update 1 installation.

  I than wanted to install Patch 3 for 2019.0.1 but the patch failed with the message that...

  Read more

  after installing Azure Devops Server 2019 Update 1 Patch 1 I noticed that it takes a lot more resources than previous version. I found a bug report that Azure Devops Server 2019 Update 1 uses more resources than RTM and therefore I uninstalled Azure Devops Server 2019 Update 1 via Control Panel (as well as the databases in the SQL Server) and installed Azure DevOps Server 2019 RTM followed by installation of 2019.0.1 which both version did require less resources than Update 1 installation.

  I than wanted to install Patch 3 for 2019.0.1 but the patch failed with the message that if found the correct TFS 2019.0.1 but also found patch 2019 Update 1 Patch 1 17.153.29226.8 and downgrade patching is not possible.

  How can I install Patch 3 for Azure DevOps 2019.0.1 ?

  or when will the fix against high resource for Update 1 be available ?

  Read less
  • 

    Erin Dormier Author October 4, 2019 0

    Collapse this comment Copy link

    Hi Daniel,

    The fix for the high resources is planned to be available in November. If you would like a private fix earlier, please send me a mail at egeaney@microsoft.com.

    I’m following up with my team to help with the patch installation problem you’re having.

    Thanks,
    Erin

    • 

      Daniel Steiner October 8, 2019 0

      Collapse this comment Copy link

      after applying the private fix on a single server installation the memory usage went down from 9.5GB to 7.6GB for a single collection with one empty project.
      After creating 2 work items and connecting from various VisualStudio version the memory usage increased by 1GB mainly used by the elasticsearch process running on the same server.

      Azure Devops Server should offer a builtin option to configure the memory usage of elasticsearch as this process consumes up-to 50% of the memory which can affect the Azure Devops Server performance due to memory pressure.

    • 

      Erin Dormier Author October 8, 2019 0

      Collapse this comment Copy link

      Hi Daniel,

      Thank you for the feedback. I have passed this along to our team that works on Search.

    • 

      Erin Dormier Author October 4, 2019 0

      Collapse this comment Copy link

      Here is the info on the patch installation:
      The patch checks to make sure that a later version of the patch hasn’t been installed by looking in the registry for the version of the patch that is currently installed. When they uninstalled Update 1 the Update 1 patch info wasn’t removed because it wasn’t written by the MSI. So when the 2019.0.1 patch looked in the registry, it found the Update 1 patch and said that a later version was installed. The customer can delete the HKLM\SOFTWARE\Microsoft\TeamFoundationServer\17.0\PatchVersion value and they will be able to install the 2019.0.1 patch.

• 

  Stanton, Andrew September 11, 2019 0

  Collapse this comment Copy link

  @Erin Dormier - Any chance that the build history that was deleted without warning or authorization is going to get restored? Also all the version numbers that were broken due to that "streamlining" get fixed?   The engineer working the feedback ticket does not seem to understand the risk this creates for your customers, even when painstakingly explained. Per his (push off) request, I opened a support request to have the history restored and the questions the support rep is asking are the kind one would get when the the source is trying to push-off or delay and hope the problem...

  Read more

  @Erin Dormier – Any chance that the build history that was deleted without warning or authorization is going to get restored? Also all the version numbers that were broken due to that “streamlining” get fixed?   The engineer working the feedback ticket does not seem to understand the risk this creates for your customers, even when painstakingly explained. Per his (push off) request, I opened a support request to have the history restored and the questions the support rep is asking are the kind one would get when the the source is trying to push-off or delay and hope the problem goes away. The only thing that the pipeline’s dev team agreed to fix was a bug in the settings UI related to this feature that still isnt fixed despite that feedback item indicating otherwise (and this defect ought to have been caught by by anyone testing the new feature). Meanwhile more of your customers are discovering all thier build numbers are reset and they are issuing programs and packages with different code and old version numbers. My only recourse was to make a utility that marks every build as retain indefinitely.
  I would have contacted you or the other AzDo PM’s directly, but all I can find on here are what look like non-work contact addresses.

  Read less
  • 

    Erin Dormier Author September 11, 2019 0

    Collapse this comment Copy link

    Hi Andrew,

    I’m following up with my team to find out what’s going on. Stay tuned.

    • 

      Andrew Stanton September 17, 2019 0

      Collapse this comment Copy link

      @Erin Dormier In case you are getting stonewalled or only half the facts, here is the Azure case: 119090124000098 and the devcomm issue

• 

  Matthieu Penant September 11, 2019 0

  Collapse this comment Copy link

  Any chance the documentation part of the Azure Dev Ops API gets adressed in a future sprint? 
  For those of us that rely on the API, the struggle is real, as the stacking github issues can testify : https://github.com/MicrosoftDocs/vsts-rest-api-specs/issues .

  • 

    Whitney Jenkins September 11, 2019 0

    Collapse this comment Copy link

    Hi Matthieu, 

    Thanks for reaching out. We’re always working to address user feedback on our docs. As of right now, we publish incremental improvements to our REST API documentation each sprint. If there are any particular github issue in the repo linked above that need immediate consideration, please add a comment to the issue. This will help us with prioritizing fixes. 

    Best,

    Whitney 

    • 

      Matthieu Penant September 12, 2019 0

      Collapse this comment Copy link

      Thanks a lot Whitney! I’ll ping you in the issue on GH.

• 

  MICHAEL SCHORR September 11, 2019 0

  Collapse this comment Copy link

  Is there a possibility to automatically update Azure DevOps Server for example via WSUS?

  • 

    Erin Dormier Author September 11, 2019 0

    Collapse this comment Copy link

    Hi Michael,

    We don’t do automatic updates of Azure DevOps Server or TFS due to the complexities of configurations. For example, there may be multiple ATs and load balancers that need to be upgraded simultaneously.

    • 

      Vital Koshalew November 5, 2019 0

      Collapse this comment Copy link

      Hi Erin,

      Please consider adding automatic updates in the nearest future. There is always an option to disable automatic updates for any reason: complex environment or otherwise. For example, Sharepoint/SQL reporting server deployments can be really complex, but that has never been a reason not to provide updates through WSUS.

      This article describes a remote code execution vulnerability. This is a major security issue. What is the recommended process for server administrators to stay secure with Azur DevOps Server installed? Follow the blog?

    • 

      Kibel, Reinaldo November 8, 2019 0

      Collapse this comment Copy link

      Erin, I heard the challenge however I agree with Michael, the process of upgrade is painful now… and with any “Azure” branded product the expectation is a simple, clean, robust upgrade process. what will it take to remove these barriers you listed?

• 

  t shirai September 10, 2019 0

  Collapse this comment Copy link

  I applied “Azure DevOps Server 2019 Update 1 Patch 1”, but the “Microsoft.TeamFoundation.Framework.Server.dll” file was not changed and remained at “17.153.29207.5”.
  The following four files have been changed to “17.153.29226.8”.Is it correct?
  “Microsoft.VisualStudio.Services.Search.ReSearch.Core.dll””Microsoft.VisualStudio.Services.Search.Common.dll””Microsoft.VisualStudio.Services.Search.Indexer.dll””Microsoft.VisualStudio.Services.Search.Platforms.SearchEngine.dll”

  • 

    Erin Dormier Author September 11, 2019 0

    Collapse this comment Copy link

    Thanks for this feedback, you are absolutely correct. I just updated the post.