Log4OM says LOTW validated, LOTW doesn't
Posted: 16 Sep 2023, 02:54
I've been going over my log to check for DX QSOs I still need confirmed. I've discovered 8 DX QSOs for new countries worked between 10/14/22 and 8/22/23 that have problems. Log4OM claims they are validated by LOTW. But when I go to the LOTW Web interface, they don't show up at all.
Three QSOs are from Thailand, two from Lebanon, Qatar, and Nepal, and one from Rodriguez Island. All are FT8 QSOs. I just tried to re-upload the Nepal QSOs to LOTW, and I got a "duplicate QSO suppressed on line xx" error, so LOTW does have them in its database.
I did not edit these contacts manually, so I'm guessing that either LOTW confirmed the contact incorrectly, or confirmed and then withdrew the confirmation (is that even possible?). Or Log4OM's database got slightly corrupted somehow. Or perhaps I clicked on something unwittingly. Any idea how to fix this?
Windows 11, Log4OM 2.28.0.0, 16 GB RAM, 1.17 Terabytes of available SSD disk space. I update Log4OM fairly regularly, usually lagging a week or two behind in case any updates have major issues. I did wait a couple of months to update to the version that required us to redo our connections to other programs (WSJT, JTDX, FlDigi, etc.)
Three QSOs are from Thailand, two from Lebanon, Qatar, and Nepal, and one from Rodriguez Island. All are FT8 QSOs. I just tried to re-upload the Nepal QSOs to LOTW, and I got a "duplicate QSO suppressed on line xx" error, so LOTW does have them in its database.
I did not edit these contacts manually, so I'm guessing that either LOTW confirmed the contact incorrectly, or confirmed and then withdrew the confirmation (is that even possible?). Or Log4OM's database got slightly corrupted somehow. Or perhaps I clicked on something unwittingly. Any idea how to fix this?
Windows 11, Log4OM 2.28.0.0, 16 GB RAM, 1.17 Terabytes of available SSD disk space. I update Log4OM fairly regularly, usually lagging a week or two behind in case any updates have major issues. I did wait a couple of months to update to the version that required us to redo our connections to other programs (WSJT, JTDX, FlDigi, etc.)