Skip to content

Commit 333e50b

Browse files
authored
Merge pull request #6742 from Migaroez/patch-10
Document corrupt examine index resolution
2 parents 293b9c7 + 5c88e02 commit 333e50b

File tree

1 file changed

+25
-1
lines changed

1 file changed

+25
-1
lines changed
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,31 @@
11
---
2-
description: How to deal with...
2+
description: How to deal with Corrupt Examine indexes
33
hidden: true
44
---
55

66
# Corrupt Indexes
77

8+
The data integrity of Examine index files can be compromised if for example files are removed. When this happens, Umbraco considers the index to be corrupt.
9+
10+
As some systems are already hooked into the Examine index lifecycle, resolving this issue outside the application is safest.
11+
12+
## Resolution in a self-hosted environment
13+
14+
The following steps cover clearing out corrupt indexes in a self-hosted environment.
15+
16+
1. Stop the website/app pool.
17+
2. Remove the directory containing the corrupted index files.
18+
3. Restart the website.
19+
20+
## Resolution on Umbraco Cloud
21+
22+
The following steps cover clearing out corrupt indexes in a setup hosted on Umbraco Cloud.
23+
24+
1. Open the project in the Cloud Portal.
25+
2. Select the correct environment.
26+
3. Access KUDU.
27+
4. Open the debug console.
28+
5. Choose CMD.
29+
6. Navigate to `C:\home\site\wwwroot\umbraco\Data\Temp`.
30+
7- Click the delete button next to the index file.
31+
8. Restart the environment.

0 commit comments

Comments
 (0)