# Could not get file content for lucene indexing

> What the "Could not get file content for lucene indexing" error means, and how to identify and clear the corrupt file that causes it.

URL: https://www.hannonhill.com/cascadecms/latest/articles/cascade-administration/search/could-not-get-file-content.html
category: Cascade Administration
article-type: reference
content-kind: faq
release-availability: all
tags: errors, search
updated: 2026-10-06

Users may see an error similar to the following when viewing the *tomcat/logs/**cascade.log* file:

`ERROR [SearchWorkerImpl] : Could not get file content for lucene indexing:
com.hannonhill.cascade.model.render.file.FileRenderException:
Could not fetch contents of file (id='97e7a2f60a000182011a542b7e51160d'): null`

This message indicates that the file with this particular id is corrupt. To clear the log file of this error, follow these steps:

1.  Execute (or have your DBA execute) the following SQL query:
    ```markup
    SELECT name, cachePath FROM cxml_foldercontent WHERE id = 'idFromErrorMessage';
    ```
         making sure to replace `idFromErrorMessage` with the 32-digit id seen in the log file.
1.  Using the result from the query above, browse to the asset inside of Cascade CMS by using a direct link of the form:
    ```bash
    https://{hostname}/entity/open.act?id={id}&type=page
    ```
         where `{id}` is the id from the error message and `{hostname}` is the name of the application server.
1. Delete the asset by clicking **More > Delete**.