Hello,
This issue usually occurs when the full text search index file is being used by another process making it unavailable to LabKey.
Based off of the path (virtual machine: C:\Program Files\Apache Software Foundation\Tomcat 8.5\temp\labkey_full_text_index\write.lock) in the stack I'm guessing you are using a windows machine.
You could use the resource monitor
- Open Resource Monitor, which can be found
- By searching for Resource Monitor or resmon.exe in the start menu
- As a button on the Performance tab in your Task Manager
- Go to the CPU tab of the resource monitor
- Use the search field in the Associated Handles section
- Here you can search for "labkey_full_text_index\write.lock"
Once you locate the process using that file you can terminate it. If the crawler doesn't automatically continue, you may need to go to "Admin Console" --> "Management/Full-Text Search" and start the crawler.
If these steps do not resolve the issue you may consider deleting the index and allowing it to create a new one, but you will likely need to terminate the process holding that .lock file to accomplish this as well.
Thanks,
Chet