The Laserfiche 8 Search Engine Can Become Unstable When Automated Backup Programs Lock the .IDX Files.

March 8, 2010 | KB: 1012535
Laserfiche 8

Summary

The Laserfiche Search Engine does not smoothly recover from being unable to access a search catalog's idx files. This situation can occur when third party programs, such as backup programs, acquire a file lock on the idx files.

When idx files are not available to the Laserfiche Search Engine, search catalog corruption may occur. This can cause text searches from Laserfiche client program to display 9132 errors and the Windows Event Log may contain variations of the following error messages.

  • Failed to flush 'RepositoryPath\SEARCH8\lflink.idx', err: -1. (Event ID 32983)
  • Idx err: 7805. (Event ID 33176)
  • LFException: (Line: 0) Idx err: null., Catalog CatalogName will restart. (Event ID 33266)
  • Failed to write 'RepositoryPath\SEARCH8\lfword.idx', err: 13. (Event ID 32986)
  • Failed to read 'RepositoryPath\SEARCH8\lflink.idx', err: 13. (Event ID 32985)
  • Fatal error encountered: 0x26cc000809f.
  • Invalid catalog status for the operation for search catalog CatalogName. (Event ID 32937)

Resolution

From the Windows Services MMC snap-in, start the Laserfiche VSS Writer service. In certain configurations, this service allows the Laserfiche Search Engine to handle interruptions to idx file access when using the build-in backup tool included in Windows or other third party backup programs that implement the Microsoft Windows Volume Shadow Copy Service.

Note: The Laserfiche 8.1.1 VSS Writer does not support Windows 7.

Note: Consult your backup software documentation to determine whether the software supports Microsoft's Volume Shadow Copy Service.

Workaround 1

Configure your third party backup program to exclude the SEARCH8 subfolder located in the repository folder.

Workaround 2

Temporarily stop the Laserfiche Search Engine prior to backing up the search index files. Searching and indexing will be unavailable until the service is restarted.