Overview
After an unexpected Power outage, Kerio Control might disconnect from the Domain controller. When checking the Webadmin > Domain and User Login settings, there is no connection to the Domain server. Domain joining issues causing VPN client authentication failures.
While re-joining Kerio Control to the domain, the "Error while connecting domain: Could not initialize message context. Try running as root” is displayed.
This article provides information on how to resolve such an issue.
Solution
When checking the Dashboard, the disk storage appears to be fully occupied.
That is the primary reason why the Kerio Control couldn't join the Directory Server.
As a side consequence of full storage, the Antivirus update might be failing. AV creates temporary folders for database signatures and a fully occupied disk prevents temp locations to be initialized.
- On the Dashboard screen, click Go to System Health.
- Click Manage and delete the redundant data. In this case, it is the "Delete all logs at once" option, but it can be huge Kerio Control Statistics as well.
If you're getting "Error while connecting domain: tdb_expand overflow detected current map_size[<number>] size [212]", please reboot your Kerio Control from the System Health.
Testing
The Kerio Control is joined to DC successfully.
