Page 3 of 7

Re: JTalert and Log4OM version 2

Posted: 23 Jan 2020, 20:33
by sq9jxb
JT-Alert beta 0003

Such a message after running Settings.


Image

Do I need to create a MySQL database?

Re: JTalert and Log4OM version 2

Posted: 23 Jan 2020, 20:49
by NN7D
No, you don't have to be using a MySQL database to use the JTAlert Beta 0006 integration with V2. But it looks like you may have selected MySQL in the JTAlert Logging, Log4OM V2 settings? Check that first.

Doug - W7DRM

Re: JTalert and Log4OM version 2

Posted: 24 Jan 2020, 05:56
by sq9jxb
W7DRM wrote: 23 Jan 2020, 20:49 No, you don't have to be using a MySQL database to use the JTAlert Beta 0006 integration with V2. But it looks like you may have selected MySQL in the JTAlert Logging, Log4OM V2 settings? Check that first.

Doug - W7DRM
Hello W7DRM

I'm using SQLite instead of MySQL, and Settings in JT Alert does not open.
I stayed with JT-Alert - 0001 Beta

Regards

Re: JTalert and Log4OM version 2

Posted: 24 Jan 2020, 08:26
by G4POP
sq9jxb wrote: 24 Jan 2020, 05:56
W7DRM wrote: 23 Jan 2020, 20:49 No, you don't have to be using a MySQL database to use the JTAlert Beta 0006 integration with V2. But it looks like you may have selected MySQL in the JTAlert Logging, Log4OM V2 settings? Check that first.

Doug - W7DRM
Hello W7DRM

I'm using SQLite instead of MySQL, and Settings in JT Alert does not open.
I stayed with JT-Alert - 0001 Beta

Regards
I had same issue with an early version of JTalert and told Laurie about it, try the latest update

Re: JTalert and Log4OM version 2

Posted: 24 Jan 2020, 14:23
by va3vf
If JTAlert is not opening, download beta 6 again.

Make sure to use the Log4OM v2 tab in JTAlert, and point it to the SQLLite or MySQL file you are currently using in Log4OM.

73 de Vince

Re: JTalert and Log4OM version 2

Posted: 24 Jan 2020, 15:36
by sq9jxb
va3vf wrote: 24 Jan 2020, 14:23 If JTAlert is not opening, download beta 6 again.

Make sure to use the Log4OM v2 tab in JTAlert, and point it to the SQLLite or MySQL file you are currently using in Log4OM.

73 de Vince
Hello

Unfortunately it doesn't work. If in the configuration the author of the program has set MySQL by default, that's probably why.
I uninstalled the old version, cleaned the registry, removed all directories from the HamApps application data. I installed the Beta 0006 version and the same effect

Photo below.

Image

Regards

Re: JTalert and Log4OM version 2

Posted: 24 Jan 2020, 15:44
by IW3HMH
Log4OM current connection is reported in the l4ong.status file in the settings folder (HELP -> OPEN CONFIGURATION FOLDER)
this should reflect current configuration settings.
Please check if that file is correctly pointing to your actual database archive.
In case of errors please let me know, you can safely delete it, Log4Om will regenerate on next start

Re: JTalert and Log4OM version 2

Posted: 24 Jan 2020, 15:44
by IW3HMH
Log4OM current connection is reported in the l4ong.status file in the settings folder (HELP -> OPEN CONFIGURATION FOLDER)
this should reflect current configuration settings.
Please check if that file is correctly pointing to your actual database archive.
In case of errors please let me know, you can safely delete it, Log4Om will regenerate on next start

Re: JTalert and Log4OM version 2

Posted: 24 Jan 2020, 17:10
by sq9jxb
IW3HMH wrote: 24 Jan 2020, 15:44 Log4OM current connection is reported in the l4ong.status file in the settings folder (HELP -> OPEN CONFIGURATION FOLDER)
this should reflect current configuration settings.
Please check if that file is correctly pointing to your actual database archive.
In case of errors please let me know, you can safely delete it, Log4Om will regenerate on next start
Hello Danielle

Contents of the L4on.status file

"[MAINTENANCE]

[STATUS]
L4ONG_RUNNING = true
L4ONG_START =
PORTABLE = false

[PATH]
APPLICATION = C:\Program Files (x86)\IW3HMH\Log4OM NextGen\
CONFIG = C:\Users\sq9jx\AppData\Roaming\Log4OM2\
USER = C:\Users\sq9jx\AppData\Roaming\Log4OM2\user\

[INTERFACE_STATUS]
OPEN_RIBBON =

[DATABASE]
CONNECTED = True
TYPE = SQLITE
CONNECTIONSTRING = D:\Logi-HR\NEW\2020\Log4OM-2\SQ9JXB-FT.SQLite

[SERVICES]

[VOACAP]
GRADIENT = 0
BAND = 20m
VIEW = SNR

[CONTEST]
CONTEST_ID =
START_DATE = 20200120185634
END_DATE = 20200121185634
EXCHANGE_FIXED = Y
FIXED_VALUE =
PREFIX_VALUE =
SUFFIX_VALUE =
VALUE = 1

[INBOUND_SERVICES]
JT_MESSAGE = 2333;12040
ADIF_MESSAGE = 2237

[FORMS]"

Re: JTalert and Log4OM version 2

Posted: 24 Jan 2020, 21:07
by KD0ZV
The Latest JTAlert version 2.15.8 is now available @ https://hamapps.com/JTAlert/

This release has support for the newly released Log4OM V2. Both SQLite & MySQL logs are supported.
Log4OM V2 users should view the Help file for proper setup instructions (they are very simple).
See the "Settings -> Logging -> Log4OM V2" topic in the help file. Using the Help button when on the Log4OM V2 section of the JTAlert Settings window will take you to the relevant help topic.