I am getting an error message that JTAlert cannot confirm that a QSO was logged to DXKeeper. The QSOs in fact are NOT being logged to DXKeeper via JTAlert.

?

This started when I installed the latest database updates; until then, I had no issues with logging to DXKeeper using JTAlert. I suspect overlooking closing DXKeeper, DXView and SpotCollector when I did so may have caused this issue (my bad!).

?

How can I back out of my logging mess? Thank you!

?

73 Paula k9ir

+ AA6YQ comments below

I am getting an error message that JTAlert cannot confirm that a QSO was logged to DXKeeper. The QSOs in fact are NOT being logged to DXKeeper via JTAlert.

?

This started when I installed the latest database updates; until then, I had no issues with logging to DXKeeper using JTAlert. I suspect overlooking closing DXKeeper, DXView and SpotCollector when I did so may have caused this issue (my bad!).

?

+ Is there an errorlog.txt file in any of your DXKeeper, DXView, or SpotCollector folders? If so, please attach it to an email message, and send the message to me via

aa6yq (at) ambersoft.com

? ? ?73,

? ? ? ? ? ?Dave, AA6YQ

+ AA6YQ comments below

The 2 most common reasons for QSOs not being logged are ...

1. DXKeeper is running with elevated privileges. That is set to "run as administrator". Outside of testing there is no legitimate need to run DXK elevated.
2. The DXKeeper network service is not running or has faulted and no longer listening.

JTAlert automatically determines the DXK log file to read in order to confirm QSO logging and the network service port to receive logging instructions by reading the Windows registry settings for DXK. You can easily check what JTAlert is getting from the registry by examining the "Logging -> DXLab DXKeeper" section of the JTAlert main window settings.

+ None of the errorlog.txt files that Paula sent me contained program errors. The next diagnostic step is to see if she can log a test QSO from DXKeeper's Capture window; if that works, will see what happens when she directs WSJT-X to log a QSO via JTAlert to DXKeeper.

? ? ? ?73,

? ? ? ? ? ? ? Dave, AA6YQ

# AA6YQ comments below

The 2 most common reasons for QSOs not being logged are ...

1. DXKeeper is running with elevated privileges. That is set to "run as administrator". Outside of testing there is no legitimate need to run DXK elevated.
2. The DXKeeper network service is not running or has faulted and no longer listening.

JTAlert automatically determines the DXK log file to read in order to confirm QSO logging and the network service port to receive logging instructions by reading the Windows registry settings for DXK. You can easily check what JTAlert is getting from the registry by examining the "Logging -> DXLab DXKeeper" section of the JTAlert main window settings.

+ None of the errorlog.txt files that Paula sent me contained program errors. The next diagnostic step is to see if she can log a test QSO from DXKeeper's Capture window; if that works, will see what happens when she directs WSJT-X to log a QSO via JTAlert to DXKeeper.

# Paula K9IR had both N1MM and DXKeeper running. As Laurie VK3AMA explained,

"Very likely that N1MM is set to use unicast UDP with Wsjtx and that is blocking JTAlert from receiving the QSO logged message from Wsjtx. Only a single app can work with Wsjtx when using unicast UDP. For multiple apps to concurrently work with Wsjtx, without interference to each other, they all need to use multicast UDP."

# Terminating N1MM enabled Paula to log QSOs to DXKeeper via JTAlert.

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ