If it's any help; in JTAlert, 127.0.01; 2236 ADIF_MESSAGE Port; on the right you should see 2241 Control Port. In the Log4oM V2 program configuration, in connections: (UDP_INBOUND) (ADIF_MESSAGE)

I do have 127.0.0.1 as the IP address and 2237 as the port set in JTAlert (under Logging/LOG4OM V2). I suspect I need a different Out port/settings on LOG4OM (Program Settings/Connections UDP OUTBOUND

FYI, ZoneAlarm has been problematic for some users in recent weeks. It is blocking ports without providing user notification. Disabling ZoneAlarm will not correct any Firewall rules it has

Has your HRD Logbook been upgraded to support the SUBMODES? If your Logbook is old, than likely it hasn't been upgraded. de Laurie VK3AMA

FYI, this is not a JTAlert requirement, but a WSJT-X requirement. In a nut-shell, WSJT-X Tab2 functionality is broken (has been for several versions) when running in Contest mode. de Laurie VK3AMA

A higher-priority alert is coloring the Callsign. See https://hamapps.groups.io/g/Support/message/30858 de Laurie VK3AMA

Did that help, deleting the HamApps folder? de Laurie VK3AMA

What Windows version are you currently running that you're getting this error? Is it an old Server version? de Laurie VK3AMA

I installed 2.17.17 just now hoping it would fix the crashing, and everything looked fine for about 10 minutes, and then this happened: Same error, different line number. I'll be installing the new

In my experience, color highlights at times seem incorrect due to Alert Priorities being set inappropriately... I suggest that you check those, as a first step. -- Patrick - W2TAR

The latest JTAlert version 2.16.17 is now available @ https://hamapps.com/JTAlert/ Please review the release notes at the end of this message, in particular the wsjtx 2.3.0-rc2 requirements. de

This worked fine at one time but now no highlighted color only sound alarm . Wanted DXCC and zone are working fine . Do I have something in setting wrong ? Help please Ed N5DG

It's common enough that I was experiencing the exact same frustrating error message on an old, very tired, Win7 32bit machine, but didn't see this thread before I posted. I already had its successor

Wsjt. Darn auto suggest

Want needs 127.0.0.1 and port 2237 so jtalert can listen for udp. Then in jtalert you need to direct on a different port to log4om and pogrom needs to be listening on that port There is a guide on

Thanks Laurie. I did downgrade to 2.16.14 and it still does the same thing.-- Coy C Day, N5OK 20685 SW 29 Union City, OK 73090 H(405) 483-5632 C(405) 448-2368 n5ok@...

Stuart, It seems like this is not a common problem since others aren't speaking up about it. In my case, I'm off the air with digital modes until I get this fixed. I get the AutoIt Error box with

I have installed JTAlert v2.16.16 with WSJT-X v 2.2.2 and it worked fine with HRD v 5.0. I have now replaced HRD with LOG4OM v2 and the logging part works. QSOs made with WSJT-X get routed to LOG4OM

You mean 3 May 2020 right? Sent from my T-Mobile 5G Device Get Outlook for Android

Thanks, I realized, the format is Day, Month, Year not the method I have used my entire 70 years, Month, Day, Year. Grrrrr ! So when I thought it said March, 5th, 2020 it was actually saying the 5th