Skip to main content

Examine Index Errors on Umbraco Cloud: Access Denied, Missing, or Corrupted Indexes

Explains why Umbraco Cloud sites see Examine index access-denied errors, corrupted indexes, or crashes after Azure maintenance, and how to fix it with a TEMP folder rebuild or upgrading to Examine v3.9+.

Written by Joana Knobbe

Product or Service: Umbraco Cloud
Version: Affected on Examine versions prior to v3.9

Type: Troubleshooting

Tags: Examine, search index, Kudu, Azure, UnauthorizedAccessException, index corruption

Issue: You may see one or more of the following on an Umbraco Cloud environment:

  • A System.UnauthorizedAccessException referencing a path like C:\local\Temp\ExamineIndexes\[ID]\ExternalIndex\[file].cfs, with a message such as "Access to the path ... is denied."

  • Examine indexes appear missing, or search/back office UI stops working and requires a manual rebuild.

  • The site goes down entirely after an Azure maintenance window, with an error like: The process cannot access the file '...ExamineIndexes\[ID]\ExternalIndex\[file].fdt' because it is being used by another process.

Cause: This is a known Examine issue (Shazwazza/Examine#434). Azure's background maintenance processes can temporarily lock the Lucene/Examine index files stored in the local temp folder. Depending on timing, this shows up as an access-denied error, a corrupted/missing index, or — in the worst case — a full site crash.

Solution:

Option 1 — Quick workaround (clears the current error):

  1. Open Kudu → Debug ConsoleCMD.

  2. Navigate to C:\home\site\wwwroot\umbraco\Data.

  3. Delete the TEMP folder. This does not delete your content.

  4. Restart the environment.

Indexes rebuild automatically on startup. Search may be briefly unavailable while this happens; content and data are not affected.

Option 2 — Permanent fix (recommended):


Update the Examine NuGet package to v3.9 or later, which resolves the underlying file-locking issue.

  1. Clone your Cloud project repository locally.

  2. Update the package reference (via NuGet Package Manager or directly in your .csproj):

xml

   <PackageReference Include="Examine" Version="3.9" />
  1. Build locally to confirm the project resolves correctly.

  2. Commit and push — your Cloud deployment pipeline will pick this up.

If your site is down right now and you can't deploy immediately, restarting the environment from the Cloud Portal will release the file lock as an immediate stopgap while you plan the package update.

Prevention: Keep the Examine package at v3.9+ across your environments to avoid recurrence, particularly after Azure maintenance windows.

Still having issues? If the TEMP folder workaround doesn't resolve the symptom, or the deploy-marker shows a separate extraction failure, reach out to support with the contents of Kudu's deploy-failed file (see Manually run Extractions on your Cloud Environments) — that's a distinct issue from Examine locking and shouldn't be confused with it.


Last updated on July 24, 2026

Did this answer your question?