Tnx Mike, So there are two possible errors, the JTAlert "MySQL Failure" error and the "VC RUNTIME is missing" error reported by Ed WA5RHG. I wonder what version of

Gary, Log4OMV2 is much slower in writing the QSO to its log file/database compared to V1. If the QSOs are indeed getting logged you will need to increase the "Check QSO Log

If it's logging then you need to increase the time in Logging for Check QSO Log Record. I've got mine at 15 seconds now. de Mike W9MDB

This may be a repeat so sorry in advance. Have the latest version of both Jtalert and LOg40m2. All is working but keep getting the unsuccessful log alert when I log a qso. It is logging in WSJT and

The mySQL failure when opening Settings -- fixed by installing the latest VC https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads Mike

I'm confused. What are you describing? What is not being highlighted, what app/window? de Laurie VK3AMA

I was using only enabled DXCC. I enabled all and then removed a couple DXCC countries from the NOT WANTED. Then scanned all categories. Results were all highlighted EXCEPT: DXCC . The scan updated

V2.15.8 New update entry's to log are NOT highlighted.. I just use the regular setup for JTDX. Ideas? -- 73 Bob K1RI Sent from my Rotary Phone

?? Yes to what, the VC error or the JTAlert MySQL failure error? de Laurie VK3AMA

Ed, Don't worry about testing by loading the last restore point. I have sent the new build to a couple of affected users and am waiting on their response. Thanks

Yes...

Mike, This person your helping, are they getting the VC error or the JTAlert generated "MySQL start failure" msgbox when opening the Settings? de Laurie VK3AMA

The web site says the latest for 2015, 2017, 2019 see: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

Which version of vc_redist.x86? 2015 mabye? 2013 didn't fix it for another person. de Mike W9MDB

Correction: Only the last started instance is shown. Dear Laurie I did upgrade to JTAlert 2.15.8, It does work Ok in 4 instances and with my Log4OMV2 but Decode window does still show only

Same issue here - starts OK but on pressing settings I get MYSQL wont start fatal error and it closes Mike G0AMO

Thanks Laurie! This is what I suspected. I'll post this issue to the JTDX group and see if it can be addressed on their side. 73, Doug - W7DRM

Dear Laurie I did upgrade to JTAlert 2.15.8, It does work Ok in 4 instances and with my Log4OMV2 but Decode window does still show only for the first instance. Same was for 2.15.7. Please repair

Laurie, at Mike's suggestion I ran vc_redist.x86.exeand that solved the error opening settings. I tried your testversion and it also worked FB, but I'm not sure that is a fair test as I didn'troll

Ed, I am unaware which file in JTAlert is causing this error. There are several 3rd party dll files used and they are likely compiled requiring the VC runtime, it is a very