Log4OM

Hello everyone,

I made some QSOs as PA/DK2HS/P while I was on holiday. As I didn't have my laptop with me, I logged the QSOs in Wavelog and then imported them into LOG4OM via ADIF export/import after my return. This also worked perfectly.
Now I would like to transfer them to QRZ.com using the QSL Manager
I have created a new LOGBook PA/DK2HS/P in QRZ.com.
During the upload I get

Upload failed: 'STATUS=FAIL&RESULT=FAIL&REASON=wrong station_callsign for this logbook PA/DK2HS/P doesnt match book callsign DK2HS&EXTENDED=' for QSO Callsign: OT6V/P Date: 03.07.2025 15:53:00 Uhr Band: 40m Mode: SSB
QRZCOM END

I have exported the QSO from LOG4OM as ADIF and attached it here.

Any advice
vy73
Heribert
DK2HS

You need to update external sources/QRZ in log4om

And

Ensure that the station callsign for those qso's is correct

I did the following changes:

User Configuration -->
Station Information -->
Station Callsign: PA/DK2HS/P
Station Country: Netherlands
Operator Callsign: PA/DK2HS/P

External services
API Key (from QRZ.com for the Logbook PA/DK2HS/P)
Force Sttaion Callsign: PA/DK2HS/P

Anything I missed to change ?

One thing I had discovered
I have established the additional QRZ logbook with PA/DK2HS/P, however I have seen that QRZ.com in the proporties of the logbook the Book-Callsign is PA/DK2HS. Just to mention

Have you tried uploading an ADIF file to the QRZ website manually direct

Yes I tried two ways:

Export the QSO from LOG4OM into adi and then import in the WEBUI of qrz.com.
Export the QSO from wavelog into adi and then import in the WEBUI of qrz.com.
Unfortunately it dosn't work in both cases with the message

Error on record: IZ7QFN de PA/DK2HS/P on 2025-07-09 19:47:00. could not be imported into the specified book (). This can happen because the callsign doesnt match or the QSOs date/time is outside of the logbooks date range.

Both I have double checked and are ok.
I will contact the qrz.com support

Sounds odd, please let me know what happens

Here the response from qrz.com

Unfortunately, QRZ logbook doesn't currently support callsigns with a regional prefix and an operational modifier (double slash). This is due to a database issue and we're working on resolving it, but we do not currently have a timeline for a fix. We apologize for the inconvenience.

73
Heribert
DK2HS

dk2hs wrote: 16 Jul 2025, 19:29 Here the response from qrz.com

Unfortunately, QRZ logbook doesn't currently support callsigns with a regional prefix and an operational modifier (double slash). This is due to a database issue and we're working on resolving it, but we do not currently have a timeline for a fix. We apologize for the inconvenience.

73
Heribert
DK2HS

Whoops!