You're problem is NOT the same as the original poster, he had some Callsigns missing, your reporting all Callsigns missing. The UDP error message is the clue, if UDP comms between

Missing Callsigns (not all) is a sign that you have one or more Alert Filters engaged. The missing Callsigns are not passing the Filters like LoTW only, hide non-Alerting, hide B4, etc. de Laurie

Here are the settings I have:

Having the same problem here. I have checked the settings (see below) but don't see a problem. It is giving the warning box about UDP settings. The only thing that has changed overnight is two new

This morning I noticed some call sign that were decoded in WSJTX were not being displayed in JTA. I had recently upgraded to JTA Ver 2.16.8 so I downgraded to 2.16.6 and found the same problem. The

When I select a CQ callsign in JTAlert 2.16.8 how do I make that pass-through the callsign to DXLab's Pathfinder ? Despite all the check-boxes in 'Settings' of JTAlert,, the only time I see a

Hi Joe, Tried that and still no alert sounds and no JTAlertV2.manager in the sounder screen 73 John Virus-free. www.avg.com

Hi Dave, all understood Dave, this may have been a different issue from that descripton of Carl's issue. Here 81 QSOs in a row failed to log. No issues prior to that and none

# more AA6YQ comments below Hi Dave, understood. Unfortunately today's issue happened during a pileup and the only priority was to get the log up to date and functioning. I believe the fact that

Hi Dave, understood. Unfortunately today's issue happened during a pileup and the only priority was to get the log up to date and functioning. I believe the fact that restarting JTAlert did not fix

+ AA6YQ comments below today I suffered this issue. JTAlert was giving the message about being unable to confirm logging to DXKeeper, as usual I ignored it since my PC is often very busy and slowing

Hi Dave and Laurie, today I suffered this issue. JTAlert was giving the message about being unable to confirm logging to DXKeeper, as usual I ignored it since my PC is often very busy

If you have a Wanted Call and Filters>>QSL Membership Options>>LoTW member selected, the wanted call will NOT alert. Perhaps the Filter section should be ignored for any wanted calls, mostly since

Great job Jon..This is why these forums work.. 73 Al W1JHU

I got this working, and it is alerting by band/mode just fine. I added the callsigns to the wanted callsigns alerts, and on Worked B4 I set it to ignore B4 status before 2020-07-01. Ignore Band and

I don't think it does, because the B4 is checked against the LOGGED info, and JTalert does NOT do the logging, afaik ... it sends the WSJT log info to the logger; so if the grid is missing in the

Hi Jim, I was not referring to WSJT, I was referring to JTAlert which does know the grid, that's why it highlighted it. The issue isn't really with the grid alert or the Grid box in WSJT, it's with

If WSJT has not detected that station's grid from a previous CQ, how is it supposed to know the grid? When I do tail-end a 73 like that, I look back to see if I can see where that station has

Thank you for all the suggestions. Based on those, I think I figured out most of what's happening. When I respond to a CQ, the Grid is in the DX Grid box and when the QSO is logged, the grid is passed

Paul: Here's the link to the log sheet. Download and use one for each band. http://www.13colonies.us/2019_log Al W1JHU