Overview

The customer is experiencing an issue with the full-text search functionality in Kerio Connect. The full-text search no longer works and attempts to rebuild the full-text search index have been unsuccessful. The customer has encountered an error message stating "SEVERE got invalid change Change{HasMoreInitialChanges}" during the indexing process, suggesting an issue with the indexing service recognizing changes. The problem seems to be related to a specific user folder or message that may be corrupted.

Solution

To resolve the issue with the full-text search functionality in Kerio Connect, follow these steps:

1. Disable the Fulltext feature from Webadmin.
2. Stop the Kerio Connect service.
3. Navigate to the Kerio Fulltext folder (/opt/kerio/mailserver/store/fulltext).
4. Move the content of this folder outside the Kerio-related directory.
5. Start the Kerio Connect service.
6. Re-enable Fulltext and try rebuilding the index.

If the issue persists:

1. Locate the folder for the affected user `6b8f3b8d-1b91-4580-9f6c-98f175685d47/6de3525b-603e-49a6-be91-af79d6b3e651` (or a folder that contains one of these values) in your mailstore.
2. Temporarily move it to another directory.
3. Try rebuilding the index.

If you cannot locate the folder with the specified name, request a table from the support team to identify which ID is assigned to which user.

If the issue still persists after both troubleshooting steps were followed:

1. Enable the following debug log messages: Full-text service and Service Manager.
2. Reproduce the issue and send the debug logs and support information file to the support team.

Summary

This article provides a step-by-step guide to troubleshooting and resolving issues with the full-text search functionality in Kerio Connect. The solution involves disabling and re-enabling the Fulltext feature, moving the content of the Fulltext folder, and enabling debug log messages. If the issue persists, it may be necessary to locate and temporarily move the folder for the affected user.

FAQ

1. What if I can't locate the folder for the affected user?
   If you cannot locate the folder with the specified name, request a table from the support team to identify which ID is assigned to which user.
2. What should I do if the issue persists after following the steps?
   If the issue persists, enable the following debug log messages: Full-text service and Service Manager. Reproduce the issue and send the debug logs and support information file to the support team.
3. What does the error message "SEVERE got invalid change Change{HasMoreInitialChanges}" mean?
   This error message suggests an issue with the indexing service recognizing changes. It may indicate a problem with a specific user folder or message that may be corrupted.