Chris,
This has been a long-standing topic this week.
Your logger set the ADIF tag for your callsign to "CHRIS".
"owner_callsign: CHRIS"
That's a nice vanity call, perhaps, but it's wrong.
Here's the definition of what goes into OWNER_CALLSIGN:
The callsign of the owner of the station used to log the contact (the
So, you need to fix this as your log is wrong. There's no reason for your log to contain an OPERATOR if it's not a callsign, nor a OWNER_CALLSIGN or STATION_CALLSIGN.
When a logging program does no data validation for this kind of stuff, this is what happens.
Sadly, this is pretty hard to fix, as this is stored in the Windows registry.
I disagree with your "Don't let TQSL update" stand. You are saying "Stay with TQSL 2.5.1 because it lets you upload garbage logs". That's wrong - this is an opportunity for you to fix the data in your log so your QSOs are properly recorded.
73,
-Rick
On Sun, Apr 12, 2020 at 5:51 AM Christopher J. Shaker, KJ7BLE <
cjshaker@...> wrote:
You may NOT WANT to let the ARRL LOTW tool TQSL update itself to version 2.5.2. If you do, it may break your
LOTW.
As of LOTW TQSL V2.5.2, they now seem to care about the 'Operator Callsign' in our Certificate.
Before that, their software did not seem to care about it, and now they do.
Looks like it's supposed to be our call sign, and somehow our first name got put there?
"Signing using Callsign KJ7BLE, DXCC Entity UNITED STATES OF AMERICA
Error: QSO date is not within the date range specified on your Callsign Certificate on line 33
band: 20m
call: WW4LL
freq: 14.249000
mode: SSB
my_cnty: Deschutes
my_country: United States
my_cq_zone: 3
my_gridsquare: CN94ia
my_itu_zone: 6
my_state: OR
operator: KJ7BLE
owner_callsign: CHRIS
station_callsign: KJ7BLE
time_on: 1955
qso_date: 20200411
Warning: Signing cancelled
No records to upload"
I tried updating to the V2.5.3 RC1, and it just fails with a different error:
"Signing using Callsign KJ7BLE, DXCC Entity UNITED STATES OF AMERICA
Error: There is no valid callsign certificate for CHRIS available. This QSO cannot be signed on line 33
band: 20m
call: WW4LL
freq: 14.249000
mode: SSB
my_cnty: Deschutes
my_country: United States
my_cq_zone: 3
my_gridsquare: CN94ia
my_itu_zone: 6
my_state: OR
operator: KJ7BLE
owner_callsign: CHRIS
station_callsign: KJ7BLE
time_on: 195550
qso_date: 20200411
Warning: Signing cancelled
No records to upload"
This person ran into the same issue:
https://groups.arrl.org/g/ARRL-LoTW/topic/lotw_error_message/72949746?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,72949746
I have canceled my LOTW Certificate, and have requested a new one. Hopefully, I will set it up correctly this time. Not sure
how I hosed it before, but I must have...
Chris Shaker, KJ7BLE
--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
