JTALERT MY SQL START FAILURE

[WA2SQQ]

Installing WSJT / JTALERT using latest versions. Referring to Pg144, step #5 when I try to enter the settings I'm getting a Fatal Error, "MY SQL Start Failure" and the program shuts down. All previous settings related to WSJT / JTALERT installation went in just fine.

Suggestions?

[G4POP]

This is a known bug in the JTalert program

[WA2SQQ]

Very strange because I’ve seen many comments that works fine. Last night I started thinking about this and I may have a clue as to what’s happening. Follow what I did ..
Radio was on and LOG4OM was running.
Made sure that WSJT and JTALERT were updated and working OK with V1
Started the step-by-step procedure in the LOG4OM manual to integrate WSJT / JTDX
Everything was fine until I got to step #5. I was not able to go beyond that step.
So my thought was, must the setup be done without LOG4OM running, or perhaps running JTALERT in an Admin mode?
Could not having the steps beyond #5 completed cause this error?

[G4POP]

No nothing to do with Log4om, this issue was introduced with the latest release of JTalert.

I am informed that if you revert to the previous release of JTalert everything works

[WA2SQQ]

Really, well that's a fairly easy solution. Do you know if I can "downgrade" right over the newer version?
I'll try it tonight - thanks!

One other question. In the manual, below the setup instructions, I saw "default port" settings for WSJT / JTALERT The instructions suggest slightly different ports. Any reason why they differ?

Thanks again!

[G4POP]

Yes just reinstall over existing

Suggest that you download the user guide again and ensure that you have Log4OM 2.3.0.0 installed because we have updated quiet a lot of the integration to provide more facility

[WA2SQQ]

2.3.3.0 installed and otherwise working fine. I'm really liking it, despite the relearning phase.
Also downloaded the latest manual

So JTALERT 2.15.8 appears to be the latest version, and oddly it says that it adds full LOG4OM compatibility.
Previous version had many comments about not working correctly with LOG4OM V2. Oh well, nothing to loose, I guess!
I'll let you know how it turns out

[G4POP]

So JTALERT 2.15.8 appears to be the latest version, and oddly it says that it adds full LOG4OM compatibility.
Previous version had many comments about not working correctly with LOG4OM V2. Oh well, nothing to loose, I guess!

Previous version only supports SQLite, latest is supposed to also support MySQL so unless you need MySQL the previous version will work fine

[WA2SQQ]

Terry
This appears to be the two fixes, immediate and long term

https://hamapps.groups.io/g/Support/message/27673
Know problem affecting a very small number of users and discussed in this group many times.
The fix is to wait until the next JTAlert release due in a day or two or install an updated VC 32bit runtime package.
See https://hamapps.groups.io/g/Support/message/27654
de Laurie VK3AMA

https://hamapps.groups.io/g/Support/message/27654
Install the latest vc_redist.x86.exe runtime from here
https://support.microsoft.com/en-us/hel ... -downloads
Not the 64-bit version as JTAlert is a 32-bit application.
de Mike W9MDB

[WA2SQQ]

Installing the MS patch above fixes the Fatal Error.
However, at the end of a QSO I'm getting "Fail QSO Not Logged - SQlite unable to confirm" message
Otherwise all else appears to be OK
Suggestions?