Log4OM

JTAlert 2.15.8 works fine with Log4OM2 , loging and notification ...

Yes, i can confirm this. Have installed the new one this morning and all is working fine.
Great job from Laurie (VK3AMA) .... Thank´s

Hello

Everyone writes that JT Alert 2.5.18 works without a problem. Yes?

So how do you explain it?



Old version of JT Alert uninstalled, registry cleaned, computer restart, installation of JT-Alert 2.5.18, program running -> OK, I go to Settings- Manage stettings and what?

Fatal ERROR - MySQL start failure -
And what should I do about it?


2.5.17 Beta 0001 works without a problem. newer versions unfortunately not.

sq9jxb wrote: 25 Jan 2020, 15:06 Hello

Everyone writes that JT Alert 2.5.18 works without a problem. Yes?

So how do you explain it?



Old version of JT Alert uninstalled, registry cleaned, computer restart, installation of JT-Alert 2.5.18, program running -> OK, I go to Settings- Manage stettings and what?

Fatal ERROR - MySQL start failure -
And what should I do about it?


2.5.17 Beta 0003 works without a problem. newer versions unfortunately not.

Did you dissable antivirus and firewalls before installing JTalert? I find that I always need to othwise I have problems.

If all else fails contact Laurie the developer for help, he understands his own software better than we do.

Antivirus and firewall have nothing to do with it.

JT-Alert 2.5.17 beta 0001 works without a problem

sq9jxb wrote: 25 Jan 2020, 15:27 Antivirus and firewall have nothing to do with it.

JT-Alert 2.5.17 beta 0001 works without a problem

I am out of suggestions so I suggest that you contact Laurie because his latest release (non beta) seems to work fine for everyone.

First of all, you don´t have to uninstall the older version of JTalert. If you install over the fly all settings
are o.k. in the new installed. If you uninstall you have to do a full new setup of JTalert. I see that you
reporting a "MYSql error" .... Did you use a MySQL database in Log4OM V2 or do you use the standard
SQlite ? If you use SQlite you have to disable the MySQL in JTalert and you have to insert the path of
your SQlite database. By the way, in my screenshot you see Port 2233 for ADIF message but this was
changed by me so i´ve had the 2233 used since the first JTalert beta was given by Laurie to our Alpha
Team. Normally using standard 2236 in JTa and L4O should work to0.

Hello

The problem is that I've NEVER used MySQL in Log4OM.
How do I turn off the MySQL database in Log4OM, if the configuration panel does not open in JT Alert, it just crashes Fatal ERROR after clicking Settings -> Manage Settings?

This problem occurs not only with me, but also with others, which was reported to VK3AMA Support.
Another question -> why version 2.15.7 Beta 0001 works and already versions 0003, 0006 or 2.15.8 do not?

Regards

sq9jxb wrote: 26 Jan 2020, 10:06 Hello

The problem is that I've NEVER used MySQL in Log4OM.
How do I turn off the MySQL database in Log4OM, if the configuration panel does not open in JT Alert, it just crashes Fatal ERROR after clicking Settings -> Manage Settings?

This problem occurs not only with me, but also with others, which was reported to VK3AMA Support.
Another question -> why version 2.15.7 Beta 0001 works and already versions 0003, 0006 or 2.15.8 do not?

Regards

These are questions that you should send to Laurie of JTAlert, he wrote the program not us

Does not matter how many times you ask this question here and on our Facebook group the answer is the same, we do not know the problem with JTAlert!

If you have not used MySql in Log4OM you have to do nothing. When installing normally all is set
to use SQlite. You have only to change in JTalert but if the setup window will not open there it
could be another problem. But it´s JTalert problem and not Log4OM. If this is reported by other
JTalert users on Lauries site i think he will be fix this. But you can try a fresh installation of JTa
so it could be possible that you have only a corrupt installation.