You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Find troubleshooting information and learn the answers to frequently asked questions (FAQs) about the Search function and extensions available for Azure DevOps.
18
+
19
+
::: moniker range=">= tfs-2017 < azure-devops"
16
20
17
21
<aname="no-search-box"></a>
18
22
@@ -21,27 +25,31 @@ A:
21
25
1. The search box is shown only in the context of a project page.
22
26
Navigate to a project and check if the search box is displayed at the top right.
23
27
24
-
2. If the search box is not shown, verify that the extension is installed for the collection.
28
+
2. If the search box isn't shown, verify that the extension is installed for the collection.
25
29
If not, [install](administration.md#config-tfs) or [configure](administration.md#config-ts-azuredevops) the extension.
26
30
27
31
<aname="no-results-install"></a>
28
32
29
33
## Q: Why are no search results shown after installing or configuring Search?
30
34
A:
31
-
1. Wait until you're sure sufficient time has elapsed
32
-
after installing or configuring Search. It typically takes
33
-
less than one hour for Search to index a collection, but
34
-
it may take up to 12 hours depending on the size and number of code files, work items, or wiki pages.
35
+
1. Wait until you're sure sufficient time has elapsed after installing or configuring Search. It typically takes less than one hour for Search to index a collection. But, it may take up to 12 hours based on the size and number of code files, work items, or wiki pages.
## Q: Why is Code search what's provided when I'm in Work Item view?
43
+
44
+
A: You can toggle between Work Item and Code Search entities by using the picker next to the search box.
41
45
## Q: How do I know if indexing was triggered for all the collections?
42
46
A:
43
47
*[Check indexing status](administration.md#check-index) separately for each collection.
44
48
49
+
## Q: When I search file:span, why does it return files with an extension?
50
+
51
+
A: File:span searches will fetch all files named span with the extension included. This behavior occurs because the most common scenario for users is to fetch the filename along with the extension. In case you don't want to see the extension, use the following search string: file:{filename} NOT file:{filename}.*
52
+
45
53
<aname="no-results-later"></a>
46
54
47
55
## Q: Why does Search stop working and no results are shown?
@@ -54,8 +62,8 @@ name of the server where Search is installed:
54
62
- If the status returned is `200 - OK`, go to step 2.
55
63
- If any other status is returned, [contact Support](https://developercommunity.visualstudio.com/spaces/21/index.html).
56
64
- If you don't get a response, verify that the
57
-
**elasticsearch-service-x64** service is running on
58
-
the server where Search is configured. If the service
65
+
**elasticsearch-service-x64** service runs on
66
+
the same server as Search. If the service
59
67
is stopped, start it and access the Search server again.
60
68
If you still get no response, or a response other than
@@ -71,15 +79,14 @@ name of the server where Search is installed:
71
79
72
80
3. Access the URL `http://SearchServer:9200/_cat/shards?v`
73
81
from a web browser on a computer in the same domain as the server running Search.
74
-
-Make a note of the values in the **Shard** column for the
82
+
-Record the values in the **Shard** column for the
75
83
rows with a **state** value of **unassigned** and [contact Support](https://developercommunity.visualstudio.com/spaces/21/index.html).<p />
76
84
77
85
<aname="unexpected-results"></a>
78
86
79
87
## Q: Why doesn't Search show the expected results?
80
88
A:
81
-
1. If the files were added in the last few minutes,
82
-
wait for 10 minutes or so while they are indexed.
89
+
1. If the files were added in the last few minutes, wait for about 10 minutes while they're indexed.
83
90
2.[Check indexing status](administration.md#check-index) for the collection.
84
91
3. If the files are still not shown in the results,
85
92
[reindex the repository or collection](administration.md#re-index)
@@ -95,10 +102,10 @@ A:
95
102
96
103
<aname="no-search-post-upgrade"></a>
97
104
98
-
## Q: Why doesn't Search work post upgrade to Azure DevOps Server 2019 Update 1?
105
+
## Q: Why doesn't Search work after upgrading to Azure DevOps Server 2019 Update 1?
99
106
100
-
A: If the search is set up on a separate (remote) server and source version is TFS 2018 Update 2 (or higher), verify that [these upgrade steps](administration.md#upgrading-search) were followed.
101
-
If not, then run [this script](https://github.com/microsoft/Code-Search/blob/master/Azure_DevOps_Server_2019/Troubleshooting/Repair-Search.ps1) to fix the issue.
107
+
A: If Search is on a separate remote server and the source version is TFS 2018 Update 2 or higher, verify that the user followed [these upgrade steps](administration.md#upgrading-search).
108
+
Run [this script](https://github.com/microsoft/Code-Search/blob/master/Azure_DevOps_Server_2019/Troubleshooting/Repair-Search.ps1) to fix the issue, if the upgrade steps weren't followed.
102
109
103
110
## Partial results in code search
104
111
@@ -110,17 +117,29 @@ I see a **Showing partial code results** banner in code search.
110
117
111
118
### Explanation
112
119
113
-
You're likely to encounter this scenario when your code base has one or more large repositories (larger the repository, more the number of documents to search). So, when you search such repositories, the request may take more time to process from all documents in the index and cause the search request to time out on the index. In such a case, you may see partial search results along with **Showing partial code results** banner as shown above before the request times out.
120
+
Your code base might have one or more large repositories. The larger the repository, the higher number of documents that get searched. When you search large repositories, the request could take more time to process, which can cause the search request to fail. In this case, you may see partial search results along with the **Showing partial code results** banner, per the previous image.
114
121
115
122
### Recommendation
116
123
117
-
You could try the following alternatives as applicable for your scenarios
124
+
You could try the following alternatives, as applicable to your scenario:
118
125
119
-
*Try to scope your query by using filters to narrow down to a "repo" or a "path".
120
-
* See if you can narrow down your query to avoid scenarios that require matching too many terms while searching.
126
+
*Scope your query by using filters to narrow down to a "repo" or a "path".
127
+
* See if you can narrow your query to avoid scenarios that require matching too many terms.
121
128
122
129
For example, while looking for methods like App_App1, App_App2, and so on, instead of searching for ```a*``` try searching for ```app*``` instead. (```a*``` will match many more terms than ```app*```).
123
130
131
+
::: moniker-end
132
+
133
+
::: moniker range=" <= azure-devops"
134
+
135
+
## Q: How do I search company-wide for published internal NuGet packages?
136
+
137
+
A: Go to [Discover in Azure DevOps(https://aka.ms/discover), enter your query and search, and then choose the **Packages** pivot. You can also navigate from your organization's landing page. At the top left of your screen, there's a link to the Microsoft enterprise search page below the Azure DevOps logo.
138
+
139
+
## Q: Is Azure DevOps Search extensible?
140
+
141
+
A: Currently, no, but you can submit a new feature request in the [Developer Community](https://developercommunity.visualstudio.com/spaces/8/index.html).
142
+
124
143
## Wildcard search
125
144
126
145
### Problem
@@ -135,8 +154,18 @@ while ```get*``` shows **109,134** results.
135
154
136
155
### Explanation
137
156
138
-
Let's understand how wildcard search works in the given scenario. Let's say you search for ```app*```. In the backend, the wildcard `*`is expanded to match any character sequence after the term ```app```. For example, ```app*``` might expand to ```app, app0, app01, .., apple```. This expansion takes place for the first 100 expanded terms only. Post the expansion, all the files associated with the 100 expanded terms are displayed on the search results page. In this case, there is a possibility that ```application``` may not be within the first 100 expanded terms therefore, you may not find files with the search term ```application``` in the search results. This is one of the reasons why you may see fewer search results for the term ```ge*``` as compared to ```get*```.
157
+
Let's say, you're searching for ```app*```. In the backend, the wildcard `*`expands to match any character sequence after the term ```app```. For example, ```app*``` might expand to ```app, app0, app01, .., apple```. The expansion takes place for the first 100 expanded terms only. Post expansion, all the files associated with the 100 expanded terms display on the search results page. There's a possibility that ```application``` may not be within the first 100 expanded terms so, you may not find files with the search term ```application``` in the search results. You may see fewer search results for the term ```ge*``` as compared to ```get*```.
139
158
140
159
### Recommendation
141
160
142
-
This is to ensure the search results remain performant and you can find the most meaningful results as fast as possible. The expectation is that in case of wildcard search you can type more in the search bar to scope the results to a meaningful and actionable chunk.
161
+
Ensuring that you can find the most meaningful and actionable results as fast as possible, enter more criteria in the search bar.
0 commit comments