After migrating Kerio Connect to a new system, the administrator tries to start the service and logs in using the account used to access the source server. The service fails to start.
This may be caused by an incorrect definition of the store directory. The target system is based on a different operating system or has a different directory structure.
This article provides information on how to resolve the above issue by defining the correct system path/s in Kerio Connect.
A migrated Kerio Connect installation to a new system (Mac OS X, Linux, Windows).
mailserver.cfgfile that is located in the Kerio Connect installation directory. The default locations are:
- Verify that the location of the store directory is accurately configured in the
mailserver.cfgfile by opening the file in a text editor and defining the correct system paths as follows:
Table Variable Description Directories StoreDir Path to the store directory Directories ArchieveDir Path to the archive directory Directories BackupDir Path to the backup directory Update DownloadedFile Path to the recent update file by web administration upgrade feature FullTextSearch Path Path to the full-text search InstantMessaging StorePath Path to the Instant Messaging configuration data WebIM StorePath Path to the XMPP configuration data LogGlobal RelativePathsRoot Path to the log files
- (Optional) If you are using an external disk (HDD, SSD) for the Kerio store, you can modify the above variables accordingly. Please make sure that the disk is mounted correctly and is visible/recognizable by the OS. The same applies to Network locations. If the OS can view the mounting point, the Kerio Connect service should be able to pick up the necessary directories.
Note: If you are not sure how to modify the store location, please leave it as defaults and reach out to Support for assistance.
After defining the correct system paths, the service starts successfully.