Legacy Knowledge Base
Published Jun. 30, 2025

"NoSuchFileEntryException" error message appears

Written By

Shimada Taro

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

"NoSuchFileEntryException" error message appears

Issue

  • It throws an error like this:
ERROR [liferay/scheduler_dispatch-3][TrashEntryLocalServiceImpl:190] com.liferay.document.library.kernel.exception.NoSuchFileEntryException: No FileEntry exists with the key {fileEntryId=XXXX}

Environment

  • DXP 7.0+

Solution

  • It appears that there is a reference in the TrashEntry table to an element that was deleted from the original table.
    The FileEntry with ID fileEntryId is affected.
  • Run the following query to check the document library entries:
    select * from DLFileEntry where fileEntryId = 67110;
    
    

    Run the following query to see the trash entries:
    select * from TrashEntry where classPK = 67110;
    
    

    When you delete the contents of the trash, the original elements are deleted at the same time.
    Because the original record does not exist, a NoSuchFileEntryException is thrown.

    Run the following script to delete unnecessary tables from the TrashEntry table.
    It is understood that the error will no longer occur once the table has been deleted.
    import com.liferay.trash.service.TrashEntryLocalServiceUtil
    

    def entry = TrashEntryLocalServiceUtil.getTrashEntry(XXXX);

    TrashEntryLocalServiceUtil.deleteEntry(entry);
Did this article resolve your issue ?

Legacy Knowledge Base