Locked logging #logging


Roger
 

This is not a WSJTX problem so I am locking this thread. Please continue discussions on a JTALERT forum.

73
Roger
GW4HZA
Moderator


richard clare
 

Dave, the issue seems to be the newest update release (2.51.5) of jtAlerts. When I reverted back to the last version I didn't get the error about not logging to dxlab when making a new qso. When I reinstalled the newest update to jtAlerts I got the error alert again. I then went back to the previous version (2.51.4) and it was working correctly. The error seems to be the latest update of jtAlerts. Thanks Dave for the quick response. Richard wb6ewm


Dave AA6YQ
 

+ AA6YQ comments below

Got an error that qso not sent to dxkeeper. Also checked and qso had not been sent to eqso or lotw. Last time it worked was 6/14/2022 at 20:18. Last windows update was on 5/13/2022 and logging has been correct after that for 30 days. Has anybody else had that problem? I know of at least two others who have had the same issue. I use jtalerts and all the right boxes are checked in logging under dxkeeper. Thanks Richard wb6ewm

+ Please do the following:

1. on the General tab of DXKeeper's Configuration window, check the "log debugging info" box

2. log a test QSO via JTAlert

3. on the General tab of DXKeeper's Configuration window, uncheck the "log debugging info" box

4. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ (DXLab developer)


JTAlert Support (VK3AMA)
 

On 17/06/2022 04:55, richard clare wrote:
Got an error that qso not sent to dxkeeper. Also checked and qso had not been sent to eqso or lotw. Last time it worked was 6/14/2022 at 20:18. Last windows update was on 5/13/2022 and logging has been correct after that for 30 days. Has anybody else had that problem? I know of at least two others who have had the same issue. I use jtalerts and all the right boxes are checked in logging under dxkeeper. Thanks Richard wb6ewm
Sounds like you have set DXKeeper with elevated privileges, set to run as administrator. Windows security will prevent JTAlert from interacting with elevated processes. There is never any legitimate need to run DXKeeper to run elevated if it has been installed per the DXLab authors instructions.

de Laurie VK3AMA


Wendy W8FR
 

Yes, occasionally have the same problem. Just look up the QSO in the logging window in DXKeeper, right click it and send it to LoTW or Club Log or wherever you want it to go

73, Wendy WF8R

Sent from my iPhone please excuse any typos and/or grammatical errors.

On Jun 16, 2022, at 1:56 PM, richard clare <crrr@...> wrote:

´╗┐Got an error that qso not sent to dxkeeper. Also checked and qso had not been sent to eqso or lotw. Last time it worked was 6/14/2022 at 20:18. Last windows update was on 5/13/2022 and logging has been correct after that for 30 days. Has anybody else had that problem? I know of at least two others who have had the same issue. I use jtalerts and all the right boxes are checked in logging under dxkeeper. Thanks Richard wb6ewm





richard clare
 

Got an error that qso not sent to dxkeeper. Also checked and qso had not been sent to eqso or lotw. Last time it worked was 6/14/2022 at 20:18. Last windows update was on 5/13/2022 and logging has been correct after that for 30 days. Has anybody else had that problem? I know of at least two others who have had the same issue. I use jtalerts and all the right boxes are checked in logging under dxkeeper. Thanks Richard wb6ewm