Re: JTAlert not logging to DXKeeper DB
|
+ AA6YQ comments below
The 2 most common reasons for QSOs not being logged are ...
- 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.
- 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
|
