Re: LoTW "All confirmed"
toggle quoted messageShow quoted text
Thanks for the reports. Yes, I just tried it and got the same results here as well. Obviously nothing changed with AC Log. Apparently there is either a problem with the LoTW server, or ARRL has intentionally reconfigured the server's behavior, presumably to reduced demand on the server.
From: Bob Stothfang <bobstothfang@...>
Sent: Wed, Apr 1, 2020 9:57 am
Subject: Re: [N3FJPSoftwareUsers] LoTW "All confirmed"
I have the same symptoms as Steve, AI3KS has experienced and I have used his same work around to accomplish the task.
My symptoms started at the same time as his also.
Bob - W8RES
On 04/01/2020 09:45, Scott Davis via Groups.Io wrote:
Thanks for your e-mail. I understand that between the WPX contest last weekend and increased number of users with so many of us home, the LoTW server is experiencing heightened demand. Please see this FAQ here:
Serving the Amateur Radio community with contesting and general logging software since 1997.
From: AI3KS <AI3KS.01@...>
Sent: Wed, Apr 1, 2020 9:37 am
Subject: [N3FJPSoftwareUsers] LoTW "All confirmed"
Using ACLog 6.6, LoTW Manager 1.9.
I do an "all confirmed" for LOTW several times a year. Doing that this morning it was extremely quick. Looking at the raw data, the start date was 2020-03-04. Coincidentally, that was the last time I updated the log. I tried that with all three of my callsighns and the result was the same. The only way I could get a complete history was to to a "confirmed since" and change the date to the date of the original callsign issue.
Is my config hosed or is there something else going on?