It's up to each user to report their own state correctly -- you have to set up all your locations in TQSL. Mike W9MDB

Because your QSO partner did their upload with Nevada. Doesn't matter what state you put in. Mike W9MDB

JTAlert does not use grids for state....LOTW does not use grids for state. Doing that we would have cheaters all over the place. From LOTW FAQ -- it's up to each one in the QSO to report their own sta

Try the Import capability

And what weblink would that be? hams.info website is an empty domain. Mike W9MDB

Perhaps Settings/Rebuild Alert Database ?? Mike W9MDB

Name is Rebuild Alert Database Mike W9MDB

#DXLAB

Because LOTW uses THEIR state (not the one you claim) and JTAlert uses the state in your database record. So a mismatch is possible. Mike

Check your MA confirmation and ensure it's registered correctly in ACLog as MA. And that you "Rebuild Alert Database". Mike W9MDB

Look at the path in the bottom of the Log4OM window and ensure JTAlert is pointing at the same file. Probably have different paths. Mike W9MDB

Did you try a reinstall? Next step would try a new config. Go to \users\[username\AppData\Local Rename HamApps directory to something else and see if it will start up. Laurie may want your bad config

It's up to you.... Mike W9MDB

#1 Ensure that there are no green icons on the rig audio device in "Sound Control Panel". Should look like this: And not like this: If you have green icons on your rig audio device then right-click yo

On Wednesday, January 6, 2021, 08:50:19 AM CST, iz6gvc via groups.io <iz6gvc@...> wrote: Hi Mike, I find the info directly on the help of the JTAlert sw? Thanks, Camillo iz6gvc

Help/Frequently Asked Questions/Move JTAlert to a New PC Mike W9MDB

Are the missing states confirmed? What do you have checked for confirmations? Assuming you are going for LOTW WAS should look like this and only those QSO confirmed by LOTW will count. You can try my

Hmmm...try disabling the autostart items...we've never been able to track down what causes this. I haven't seen this error in a LONG time and, come to think of it, was around the time I stopped using

Mike W9MDB

Make sure you have "Accept UDP requests" in WSJT-X.

OK Laurie -- it was the CQ_ZONE and ITU_ZONE being zero was a problem. So, if those values are zero they shouldn't be put in the ADIF log. Mike W9MDB