Repair-Search.ps1 does not run for DevOps 2025
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
Direzione di ricerca
Inizia con ADO_Server_Diagnostics_2025/Troubleshooting/Repair-Search.ps1 e verifica la sua dipendenza da Common.psm1 in Troubleshooting/Utils. Poi esamina Analyzers/Test-IndicesHaveUnsupportedMappings.psm1, in particolare il percorso Code e le relative richieste di mapping, e riproduci l’errore con Elasticsearch 8. Il lavoro è completato quando Repair-Search viene avviato con i file forniti e la reindicizzazione di Code termina senza l’errore di mapping segnalato.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Our migration from Azure DevOps 2022 to 2025 is causing issues after the upgrade from Elasticsearch v7 to v8; the installation did not report any errors, but the Elastic instance was showing an error.
The logs indicated that some indices were still on v6, which is surprising as we were already using a version of DevOps that used Elasticsearch v7.
=> We therefore decided to perform a clean reinstallation and repair the Elasticsearch instance (by deleting the directory and running Repair-Search.ps1).
Unfortunately, the scripts in the ADO_Server_Diagnostics_2025 version appear to have some issues:
-
The recommended script, Troubleshooting\Repair-Search.ps1, crashes on launch because it depends on a module Common.psm1 that is not
present in the Utils directory (https://github.com/microsoft/Code-Search/blob/d4bad2abd67c5326d94bf8b00a94af1cd25b2954/ADO_Server_Diagnostics_2025/Troubleshooting/Repair-Search.ps1#L121)
To resolve this, we tried copying the version available in 2022; this works, but we cannot guarantee it. Could you please fix this issue? -
Re-indexing of the “Wiki” and “WorkItem” works without any problems; however, it does not work for the “Code” ItemType.
The script correctly identifies that the index is missing in Elasticsearch and attempts to create a mapping using the Test-IndicesHaveUnsupportedMappings method; Elasticsearch returns a 400.
Message: GET _mapping/SourceNoDedupeFileContract failed with status code [400] unexpectedly.
[2026-08-19T13:12:03Z][Verbose] Request Uri = [http://localhost:9200/code_sourcenodedupefilecontractv3_1421_shared_94814f29-47cc-46f9-b048-4caa32360ba3]
[2026-08-19T13:12:03Z][Verbose] Response = [{
"Content": null,
"ErrorMessage": "Invoke-WebRequest : Le serveur distant a retourné une erreur : (404) Introuvable.\r\nAu caractère C:\\temp\\Code-Search-master\\ADO_Server_Diagnostics_2025\\Troubleshooting\\Utils\\Common.psm1:236 : 25\r\n+ ... $response = Invoke-WebRequest -Method $Method -Uri $uri -Credential $ ...\r\n+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n + CategoryInfo : InvalidOperation : (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebEx \r\n ception\r\n + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand\r\n \r\n",
"StatusCode": 404
}]
[2026-08-19T13:12:03Z][Error] Indexing index name in SQL [code_sourcenodedupefilecontractv3_1421_shared_94814f29-47cc-46f9-b048-4caa32360ba3] does not exist in Elasticsearch cluster at [http://localhost:9200/]. Re-indexing is required.
[2026-08-19T13:12:03Z][Warn] Actions recommended are [Restart-Indexing].
[2026-08-19T13:12:03Z][Info] ======================================================================================
[2026-08-19T13:12:03Z][Info] Executing analyzer [Test-IndicesHaveUnsupportedMappings]...
[2026-08-19T13:12:03Z][Verbose] ParentPath = [#\Service\ALMSearch\Settings\].
[2026-08-19T13:12:03Z][Verbose] ChildItem = [DefaultCodeDocumentContractType\].
[2026-08-19T13:12:03Z][Verbose] Supported document contract type for entity type [Code] = [SourceNoDedupeFileContractV3].
[2026-08-19T13:12:03Z][Verbose] Request Uri = [http://localhost:9200/_mapping/SourceNoDedupeFileContract]
[2026-08-19T13:12:03Z][Verbose] Response = [{
"Content": null,
"ErrorMessage": "Invoke-WebRequest : {\"error\":\"no handler found for uri [/_mapping/SourceNoDedupeFileContract] and method [GET]\"}\r\nAu caractère C:\\temp\\Code-Search-master\\ADO_Server_Diagnostics_2025\\Troubleshooting\\Utils\\Common.psm1:236 : 25\r\n+ ... $response = Invoke-WebRequest -Method $Method -Uri $uri -Credential $ ...\r\n+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n + CategoryInfo : InvalidOperation : (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebEx \r\n ception\r\n + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand\r\n",
"StatusCode": 400
}]
[2026-08-19T13:12:03Z][Error] Repair-Search failed with following exception:
Message:
GET _mapping/SourceNoDedupeFileContract failed with status code [400] unexpectedly.
Au caractère C:\temp\Code-Search-master\ADO_Server_Diagnostics_2025\Troubleshooting\Analyzers\Test-IndicesHaveUnsupport
edMappings.psm1:78 : 13
+ throw "GET $command failed with status code [$($response. ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (GET _mapping/So...] unexpectedly.:String) [], RuntimeException
+ FullyQualifiedErrorId : GET _mapping/SourceNoDedupeFileContract failed with status code [400] unexpectedly.
Stack Trace:
à Test-IndicesHaveUnsupportedMappings, C:\temp\Code-Search-master\ADO_Server_Diagnostics_2025\Troubleshooting\Analyzers\Test-IndicesHaveUnsupportedMappings.psm1 : ligne 78
à <ScriptBlock>, C:\temp\Code-Search-master\ADO_Server_Diagnostics_2025\Troubleshooting\Repair-Search.ps1 : ligne 155
à <ScriptBlock>, <Aucun fichier> : ligne 1
In the Test-IndicesHaveUnsupportedMappings analyser, there is a specific condition that applies only when the entityType is ‘Code’ and which will trigger a call to _mapping/SourceNoDedupeFileContract and _mapping/SourceNoDedupeFileContractV2
- Lingua principale
- PowerShell
- Stelle
- 57
- Fork
- 68
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/Code-Search
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
microsoft/Code-Search#98 · 2 commenti · 2 reazioni ·
-
Code Search extension Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 15/100
microsoft/Code-Search#97 · 1 commento ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
microsoft/Code-Search#96 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 30/100
microsoft/Code-Search#95 · 1 commento ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 35/100
microsoft/Code-Search#93 ·
Tutte le issue di microsoft/Code-Search
Issue simili
-
Solved site promotion gate fails on runner PHP patch drift (expects 8.2.33, runner installs 8.2.34) Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
Automattic/blocks-engine#2161 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 60/100
github/gh-aw-mcpg#13748 ·
-
agentic-workflows
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
personalrobotics/tsr#128 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
Azure/azure-functions-docker#1257 ·