|
|
|
|
|
Most common errors are caused by an incorrect configuration of the database or the database connection parameters.
Configuration varies with each different database engine and you should confirm that
Then use the Import now button to retry the import and look for mlaimp.exe process in Task Manager to see if it's running.
If the problem doesn't relate to a database or you run into issues even with the basic MS Access database, often the most effective solution is backing up the files you have customized, deleting the whole IceWarp\loganalyzer directory, running the IceWarp Server installer of the same version you have and reinstalling- this will recreate the Log Analyzer files and settings to a fresh and consistent form, without touching anything else on the server. Then you can try putting back the customized files/settings one by one to isolate the cause.
We welcome any kind of feedback from early adopters on the following:
Contact your support center, please.