Either of the below errors is displayed to users when accessing their Kerio Connect mailbox:
Index error in folder ~email@example.com/Calendar: Cannot parse calendar message file 00000019.eml
Cannot open message file D:\Program Files\Kerio\MailServer\store/mail/kerio-domain.com/johndoe/Calendar/#msgs/00000019.eml. The file has been probably removed.
Server error Folder ~firstname.lastname@example.org/Calendar is already being reindexed. Try later.
The users can be facing file corruption issues, emails could be getting stuck in their Outbox, or the users might not be able to use their email.
The Kerio Connect related files could become corrupted or damaged due to unexpected service crashes or server outages. The internal files might also be occupied by another application or built-in OS service, which can lead to indexing issues.
Since version 7.3.0, Kerio Connect repairs corrupted files by automatically re-indexing them. For the older versions or for the cases where the automatic re-indexing fails, you can manually re-index the corrupted files using the below steps.
Exclude the Kerio Connect folders from the Antivirus scanning before implementing these steps:
The user who is seeing the issue should log out of all their mail sessions. Depending on the email client, below are the steps to logout:
- Kerio Connect Client:
- Outlook: close the application itself
Navigate to the Kerio store folder.
Access the user directory via the following path (defaults):
In the specific user's
folder_namecan be INBOX, Calendar, Sent Items, etc.) for which the error is seen, locate the
folder_name contains its own
index.fld file. One of the most common causes of inconsistencies in the
index.fld file is a local anti-virus software that has not been configured to exclude the scanning of the mail server and the store directories.
metadata.dbbfiles in the same folder.
- Start Kerio Connect (Windows, macOS/Linux).
Repeat the above steps for any other user/s that are seeing the errors when accessing their Kerio Connect mailbox.
The user/s who was/were seeing the error should now login to Kerio Connect and access the folder/s for which they were seeing the error. Kerio Connect will start rebuilding the index file after the user accesses the folder/s for the first time. If it is a large folder/s, there might be a slight delay in the re-building process. After this, the user will no longer see the error that they were seeing and will be able to access their mailbox normally.
None of the previously seen error/s should be seen in the error logs in Kerio Connect web administration.
- Fixing Errors: 'Unexpected error 26' and 'Cannot open database'
- Calendar Items Not Syncing in Outlook