Repair-Search.ps1 does not run for DevOps 2025
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
Comienza con ADO_Server_Diagnostics_2025/Troubleshooting/Repair-Search.ps1 y verifica su dependencia de Common.psm1 en Troubleshooting/Utils. Después inspecciona Analyzers/Test-IndicesHaveUnsupportedMappings.psm1, especialmente la ruta Code y sus solicitudes de mapping, y reproduce el fallo con Elasticsearch 8. Se considera completado cuando Repair-Search se inicia con los archivos incluidos y la reindexación de Code termina sin el error de mapping reportado.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lenguaje dominante
- PowerShell
- Estrellas
- 57
- Forks
- 68
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/Code-Search
-
Azure_DevOps_Server_2025 missing Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
microsoft/Code-Search#98 · 2 comentarios · 2 reacciones ·
-
Code Search extension Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 15/100
microsoft/Code-Search#97 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
microsoft/Code-Search#96 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 30/100
microsoft/Code-Search#95 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
microsoft/Code-Search#93 ·
Todos los issues de microsoft/Code-Search
Issues similares
-
core dependencies
Dificultad 1/5 Menos de una hora Aptitud para principiantes 80/100
-
bug github_actions
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
registrystack/registry-stack#1393 ·
-
module: core
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
bigbluebutton/bigbluebutton#25849 ·
-
bug engine
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
rocky-data/rocky#2181 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100