- Check that you have the latest country file for your logging software. Most DXCC errors are due to out-of-date country files.
- Search under DXCC Mappings for any relevant articles.
- If the error message says "There are comments about <callsign> in Club Log", please follow the link and read the comments that may explain the error.
- If you have transcribed QSOs from old QSL cards and/or paper logs, or if you have been configuring language settings on your computer, double-check that the day and month have not been transposed in the date field: date ranges are strictly observed for DXpeditions.
- Check for typos in the callsigns such as O instead of 0, I instead of 1, Z instead of 2, or the converse.
- "Your log claims no known DXCC value. " means that your logging software doesn't know the DXCC entity for this callsign and date combination.
- "Club Log has a specific exception for GB1XXXX and will use SCOTLAND" means that Club Log knows the DXCC enity is Scotland and has mapped the QSO to that entity.
- You can see the exceptions for a callsign/date combination in Call Tester. (left menu)
- You can see how your QSO is mapped in Log Inspector (left menu).
Before raising a support ticket please check your QSO in Log Inspector. We sometimes get multiple support tickets raised for the same problem. We only need to be told once and we only fix the problem once. If you check Log Inspector and your QSO is now mapped correctly it means the issue has been rectified. Please do not raise a support ticket in this case.
- The reason you disagree with Club Log.
- Supporting evidence such as a scan or photo of the QSL, or a URL to a relevant web page. Simply asserting that Club Log has got it wrong is unlikely to convince anyone!
- A copy of the Club Log error message concerning the QSO in question, containing the QSO details that we can check.
PS If Club Log doesn't email its upload reports to you, you may have have turned off this option under Settings.