Overview

After finishing the initial configuration of Kerio Connect on a Linux deployment, the Kerio Connect service is restarting, as seen in the screenshot below. Once it has restarted, the configuration wizard needs to be filled again from the start and this occurs endlessly.

When running systemctl status kerio-connect.service from the command-line to check the Kerio Connect service's status, it throws the error Can't open PID file /run/kms.pid (yet?) after start: No such file or directory

<supportagent>

The below message is seen repeatedly in the error log file indicating that the server is in a blank state:

externalLogger.cpp: FullText [external]: SEVERE Bad response, tag domain not found,
or no users on the server (IndexingMessageHandler.handleUsers)

</supportagent>

Solution

1. Manually stop the Kerio Connect service.
2. Open the Kerio Connect installation folder. The default location is /opt/kerio/mailserver.
3. Open the mailserver.cfg file and modify the value of the ConfigWizardDone variable from 0to 1.
   
   
   
   
4. Save the changes.
5. Start the Kerio Connect service.

Testing