After having many Windows 10 problems, I decided to reinstall the OS or "Reset the PC" as Windows now describes it.  I have most of my software reinstalled (N3FJP's Amateur Contact Log V6.7, JTAlert V 2.16.16 and WSJT-X V2.2.2) and working but I can't get JTAlert to function as before the Windows reinstallation.  The colors remain just the same WSJT-X stock colors of Yellow for TX, Green for CQ and Red for MyCall.  The only one that I remember working previously was the B4 color of gray.  I don't recall making too many changes to the JTAlert software on the first install, so I was surprised that it just didn't work as before when I reinstalled it.

Any specific ideas or links to written instructions, outside of the ones that part of Amateur Contact Log, JTAlert and WSJT-X, which I've already tried.

Thanks much,

phil
WA6HOO!

On Tue, Dec 1, 2020 at 11:59 AM, HamApps Support (VK3AMA) wrote:

• What does "Crash" mean exactly? It shuts down and has to be restarted..
  
• Is there an error dialog being shown, if so what does it say (post an image)?-No warning or dialog box is shown....
  
• Is JTAlert just disappearing or is it becoming non-response?  just disappears
  
• What was the last version of JTAlert that worked for you? it has been several versions now at least 4 updates would be my guess. i posted on this when it first started but just lived with it as i got busy with work.  trying to revisit it now.
•  

I did notice there are four JT alert managers under firewall>allow apps...all are checked to allow all options.

Bill 

You didn't answer my questions. The answers to which would provide me with some insight into what may be happening. I still don't know what you mean by "Crash". Is there an error popup? Is JTAlert becoming non-repressive or simply closing without warning?

My best guess is that your Protection software is interfering and deliberately killing JTAlert as soon as it sees some network traffic.

The JTAlert.exe executable (the main window and process) itself does not play any audio, instead it offloads that task to a background process, the JTAlertV2.Manager.exe. That operation involves sending a UDP message to the Manager. My guess is that your PC protection software is directly interfering with JTAlert.exe as soon as it issues this UDP instruction.

What Protection software are you running?

de Laurie VK3AMA

I don't always update software immediately to the latest release, so this may be a problem of my own making, but FWIW here's what I experienced recently.

I was running JTAlert v2.16.10 with whatever version of the Callsign Database was current with that release. I realized that the older Callsign Database was the reason all users were showing a last LoTW update in July. I installed the Callsign Database v2020.11.18 and that took care of the LoTW problem. But it introduced a NEW problem. When right-clicking on an alert to send a message to the operator, I was no longer getting an ONLINE or OFFLINE indication in the message window. I updated JTAlert to v2.16.16 and now all is well again.

I was not aware that updating the Callsign Database by itself could be a problem, but it was in this case.

Thanks for a great program!

73,

John, K9MM

John,

Sorry to "burst your bubble". Updating the Callsign database is not the fix. All that installer does is install 2 sqlite database files. That will not affect Text Messaging. Likely the Text Message service was either having issues at the time or one of its listening ports (there are 4) was temporarily down.

de Laurie VK3AMA

That didn't last long.  Now I'm getting the error with FT8.

Sorry, I don't have an answer at this time. I am unable to reproduce the defect. Part of the problem is that the line numbers in these errors are typically grossly incorrect and don't point at the true cause. There is likely a coding/logic error, but I haven't found it yet.

At this time, since you already tried 2.16.15, your best to downgrade JTAlert to 2.16.14

de Laurie VK3AMA

JTAlert was working fine when I shut down the station last night, but today when I open JTAlert it seems to be fine
until after the first few decode cycles, then this error appears:



When I click OK JTAlert closes.  I have uninstalled and reinstalled all
three applications with the same outcome.

Windows 7, WSJT-X v2.2.2, JTAlert 2.16.16

Dennis,

Sorry, I don't have an answer at this time. I am unable to reproduce the defect. Part of the problem is that the line numbers in these errors are typically grossly incorrect and don't point at the true cause. There is likely a coding/logic error, but I haven't found it yet.

At this time, your best to downgrade JTAlert to 2.16.15 or 2.16.14

de Laurie VK3AMA

I just noticed, that the contact complete notification popup time/Date of JTalert is completely wrong.

Going through all the menu's and settings, I found no way to set the displayed time and date correctly.

My JTalert somehow is set to March.

How is this corrected ?

Bill
K2WH

Doesn't sound like a JTAlert issue to me.

The only logging notification popup produced by JTAlert is either a "success" or "failure" popup produced post-logging and it doesn't contain any Date/Time information.

Please post an image of the popup you believe is from JTAlert.

Are the QSOs being logged with the correct Date/Time despite the popup error?

Are you perhaps referring to the wsjtx "Log QSO" window?


de Laurie VK3AMA

I managed to go back to an earlier version by just running the earlier install file over the top of the later version. It all seemed to install OK.  Do you still have the earlier install file?

For the guy who asked why...the sound alerts would not work on the later version and I also had issues with the UDP not talking the DXlab so I went back to the fault free earlier version.

73 Mark N1UK

That version is?

Regarding the sound problems, that is likely a UDP issue as well. JTAlert itself doesn't produce sounds, but sends a UDP command to the JTAlertV2.Manager.exe process which is responsible for playing all audio. JTAlert doesn't talk UDP to DXLab, that is purely DDE and TCPIP, and both of those are handled by the same manager process.

It sounds to me like your Protection software (what are you running?) didn't like the newer builds of JTAlert and was blocking all the network traffic to/from the Manager process. There is nothing I can do about overly aggressive or configured Protection software.

de Laurie VK3AMA

I managed to go back to an earlier version by just running the earlier install file over the top of the later version. It all seemed to install OK.  Do you still have the earlier install file?

For the guy who asked why...the sound alerts would not work on the later version and I also had issues with the UDP not talking the DXlab so I went back to the fault free earlier version.

73 Mark N1UK

That's a WSJT-X error message referencing a WSJT-X temp file.   You're not running any programs 'as administrator' are you?  

 

Neil, KN3ILZ

--

I keep getting the attached error message, any help would be appreciated.
I am using WSJT-X 2.2.2 and JTAlert 2.16.16 with Win 10
Thanks,
Gary
KD4VRZ

Rather than further investigate why my version of Log4OM2 isn't playing nice with LoTW, I proceeded to download N3FJP and gave it a whirl; N3FJP was simple to set up, easy to understand/use, and works well with LoTW - I think that I'll stick with it, despite the minimal fee.

I did finally get my WAS (Mixed) award, with WV and MA particularly difficult in coming by.

Thanks, everyone, for your helpful feedback and comments. 
--
Patrick - W2TAR

JTAlert was working fine when I shut down the station last night, but today when I open JTAlert it seems to be fine
until after the first few decode cycles, then this error appears:



When I click OK JTAlert closes.  I have uninstalled and reinstalled all
three applications with the same outcome.

Windows 7, WSJT-X v2.2.2, JTAlert 2.16.16

There were no software updates overnight.  I'm using Spybot S&D 2.7.64.0 as anti-virus.

--

I just noticed, that the contact complete notification popup time/Date of JTalert is completely wrong.

Going through all the menu's and settings, I found no way to set the displayed time and date correctly.

My JTalert somehow is set to March.

How is this corrected ?

Bill
K2WH

--

--