Updated: Now available: Azure DevOps Server 2022 RTW
Gloridel Morales
12/16 Update: There is an additional step that you will have to follow while upgrading to Azure DevOps Server 2022. This applies to Azure DevOps Server/Team Foundation Server and Elasticsearch installations on the same and in different machines.
- Upgrade Elasticsearch 2.x and 5.x to 7.x
You will have to select Install New Search while configuring search post Azure DevOps Server upgrade.
- Upgrade Elasticsearch 6.x to 7.x
Re-indexing is not required in this case. If any index is found which is below 6.x then re-indexing is required for that index to upgrade Elasticsearch to 7.x.
The following table includes mapping of Azure DevOps Server/Team Foundation Server and Elasticsearch versions.
Azure DevOps and Elasticsearch Versions
| Azure DevOps Server/Team Foundation Server Version | Elasticsearch Version |
|---|---|
| Team Foundation Server 2017 Update 3.1 | 2.4.1 |
| Team Foundation Server 2018 Update 3.2 | 5.4.1 |
| Azure DevOps Server 2019 | 5.4.1 |
| Azure DevOps Server 2020.1.1 | 6.2.4 |
| Azure DevOps Server 2022 RC1 | 6.8.23 |
| Azure DevOps Server 2022 RC2 and RTW | 7.17.5 |
We’re excited to announce the final release of Azure DevOps Server 2022! You can upgrade from Azure DevOps Server 2022 release candidates or previous versions of TFS and Azure DevOps. You can find the full details in our release notes.
Here are some key links:
We’d love for you to install this release and provide any feedback at Developer Community.
Light
Dark
24 comments
Do Azure DevOps Server 2022 RTW Support SQL Server 2022 ?
Yes, see https://devblogs.microsoft.com/devops/azure-devops-server-2022-rc2-now-available/#comment-3595
Hi, I installed this version ADS 2022 RTW and could not make the Search module run. I use a JDK8 as specified in the readme, and I get an error regarding Java memory upon running the service:
2022-12-08 09:06:54 Commons Daemon procrun stderr initialized java.lang.OutOfMemoryError: Direct buffer memory at java.nio.Bits.reserveMemory(Unknown Source)And the doc in the Search zip Readme is a 404 (https://go.microsoft.com/fwlink/?linkid=822603)
We had several problems with the Search Service in previous versions of Azure DevOps Server 2020 and we hoped to solve this by using 2022… it’s really annoying if this feature still doesn’t work
Vincent,
sorry you having difficulties with Azure DevOps Server 2022 RTW. Could you please share logs?
Just zip up C:\ProgramData\Microsoft\Azure DevOps\Server Configuration\Logs directory and send via email (vladimir.khvostov at microsoft.com)
How much RAM do you have on machine?
Thanks!
–Vladimir
ok my bad with the recommended Azul JDK it works flawlessly. Be sure to use this jdk though
Hi Vincent, thank you for reporting the issue with the doc link. It has been fixed.
We are running into the same error attempting to start the updated Elasticsearch service. This server has been running the same version of JRE8 351 and the previous version of search was running on it and functional for some time. The server has 16GB or RAM.
Any advice before opening a support case?
“Download PDF” in the bottom left corner of any learn.microsoft.com page I tried gives a 404 error.
Hi,
Our Elasticsearch Search server does not start anymore since we upgraded the server from latest version to 2022:
[2022-12-10T10:01:07,616][ERROR][o.e.b.Bootstrap ] [xxx] Exception java.lang.IllegalStateException: The index [projectsearchshared_1_1310/A1yxU94DQZGziai-ueUCRw] was created with version [5.4.1] but the minimum compatible version is [6.0.0-beta1]. It should be re-indexed in Elasticsearch 6.x before upgrading to 7.17.5. at org.elasticsearch.cluster.metadata.IndexMetadataVerifier.checkSupportedVersion(IndexMetadataVerifier.java:98) ~[elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.cluster.metadata.IndexMetadataVerifier.verifyIndexMetadata(IndexMetadataVerifier.java:80) ~[elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.gateway.GatewayMetaState.upgradeMetadata(GatewayMetaState.java:279) ~[elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.gateway.GatewayMetaState.upgradeMetadataForNode(GatewayMetaState.java:265) ~[elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.gateway.GatewayMetaState.start(GatewayMetaState.java:178) ~[elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.node.Node.start(Node.java:1183) ~[elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:335) ~[elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:443) [elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:169) [elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:160) [elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:77) [elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112) [elasticsearch-cli-7.17.5.jar:7.17.5] at org.elasticsearch.cli.Command.main(Command.java:77) [elasticsearch-cli-7.17.5.jar:7.17.5] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:125) [elasticsearch-7.17.5.jar:7.17.5] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80) [elasticsearch-7.17.5.jar:7.17.5] [2022-12-10T10:01:07,621][WARN ][stderr ] [xxx] java.lang.IllegalStateException: The index [projectsearchshared_1_1310/A1yxU94DQZGziai-ueUCRw] was created with version [5.4.1] but the minimum compatible version is [6.0.0-beta1]. It should be re-indexed in Elasticsearch 6.x before upgrading to 7.17.5. [2022-12-10T10:01:07,621][WARN ][stderr ] [xxx] at org.elasticsearch.cluster.metadata.IndexMetadataVerifier.checkSupportedVersion(IndexMetadataVerifier.java:98) [2022-12-10T10:01:07,621][WARN ][stderr ] [xxx] at org.elasticsearch.cluster.metadata.IndexMetadataVerifier.verifyIndexMetadata(IndexMetadataVerifier.java:80) [2022-12-10T10:01:07,621][WARN ][stderr ] [xxx] at org.elasticsearch.gateway.GatewayMetaState.upgradeMetadata(GatewayMetaState.java:279) [2022-12-10T10:01:07,621][WARN ][stderr ] [xxx] at org.elasticsearch.gateway.GatewayMetaState.upgradeMetadataForNode(GatewayMetaState.java:265) [2022-12-10T10:01:07,621][WARN ][stderr ] [xxx] at org.elasticsearch.gateway.GatewayMetaState.start(GatewayMetaState.java:178) [2022-12-10T10:01:07,621][WARN ][stderr ] [xxx] at org.elasticsearch.node.Node.start(Node.java:1183) [2022-12-10T10:01:07,621][WARN ][stderr ] [xxx] at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:335) [2022-12-10T10:01:07,621][WARN ][stderr ] [xxx] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:443) [2022-12-10T10:01:07,622][WARN ][stderr ] [xxx] at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:169) [2022-12-10T10:01:07,622][WARN ][stderr ] [xxx] at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:160) [2022-12-10T10:01:07,622][WARN ][stderr ] [xxx] at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:77) [2022-12-10T10:01:07,622][WARN ][stderr ] [xxx] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112) [2022-12-10T10:01:07,622][WARN ][stderr ] [xxx] at org.elasticsearch.cli.Command.main(Command.java:77) [2022-12-10T10:01:07,622][WARN ][stderr ] [xxx] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:125) [2022-12-10T10:01:07,622][WARN ][stderr ] [xxx] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80) [2022-12-10T10:01:07,622][WARN ][stderr ] [xxx] For complete error details, refer to the log at C:\Program Files\Azure DevOps Server 2022\Search\ES\v7.17\logs\TFS_Search_xxx.logI decided to simply erase the index folder and restart from scratch.
Hi Thomas, let us know how the upgrade goes after the restart.
Hi Gloridel
Looking very much forward to installing this new version.
Small note: Your last sentence indicates that it is still a release candidate, which I don’t believe it is:
“We’d love for you to install this release candidate and provide any…“
Hi Tore, thanks for the feedback. I fixed the wording on the last sentence.
Speaking of your feedback request, I seem to quite often getting entries closed, either because the person in the other end does not understand the product or as the following one with the message that they can’t help and I have to create a support ticket:
https://developercommunity.visualstudio.com/t/Build-Validation-and-Status-Checks-uses-/10240468#T-ND10248353
Since the analysis database and reports are intergrated in Azure Devops, is it safe to disable the regarding services „SQL Server Analysis Services (MSSQLSERVER)“ and „SQL Server Reporting Services“ after an upgrade from 2020.1 to 2022?
Yes, it is safe to disable
We have now upgraded our test instance from 2020.1.2 Patch 1 and so far things work including search.
However, at the end of the installation the Restart button did nothing and after a manual restart the migration wizard did not start automatically. There is also a leftover Azure DevOps Server 2020 folder in Program Files.
Same thing happened when upgrading our production instance. 133 files are left in the 2020 folder, so compared to the 78679 files in 2022, most of the 2020 files are gone.
Files left in C:\Program Files\Azure DevOps Server 2020\
Tore,
thanks for reporting this issue. It is safe to delete C:\Program Files\Azure DevOps Server 2020\ after installing Azure DevOps Server 2022.
Regards,
–Vladimir
Does anyone know how to enable preview features in Azure DevOps Server?
All documentation seems to be around how this is done for Azure DevOps Services, but I cannot find the Account menu item mentioned here:
https://learn.microsoft.com/en-us/azure/devops/project/navigation/preview-features?view=azure-devops&tabs=new-account-not-enabled
I would like to try out the new “Preview of templates support in YAML editors”, which is listed as available in ADO Server 2022:
https://learn.microsoft.com/en-us/azure/devops/release-notes/2021/sprint-187-update#preview-of-templates-support-in-yaml-editor
Hello-
I just upgraded to 2022 RTW. A behavior I am noticing- when I search for something in the search box in the upper right hand corner, then go to “Work item”, I get all the search results (as expected.) However, when I click the “Types: All” pulldown and select an individual Work Item type (Bug, User Story etc.), I get “No work items found for ‘xxx’ with applied filters.”, However, the pulldown screen gives me the correct number of WIs of the type that I just selected (a non-zero number).
Do I need to re-run an index or something?
Many thanks!
Azure DevOps 2022 seems to break the Proxy feature mostly used for TFVC.
The issue is reported here:
https://developercommunity.visualstudio.com/t/Proxy-upgrade-to-2022-breaks-its-functio/10264792
For now workaround is to stay on the previous version, which should work just fine, but a fix seems to be already scheduled for next Patch.