LoTW (ARRL) error tq.5

Discussion in 'Ham Radio Discussions' started by CU3AK, Dec 6, 2012.

Thread Status:
Not open for further replies.
ad: L-HROutlet
ad: l-assoc
ad: l-rl
ad: L-rfparts
ad: Subscribe
ad: l-gcopper
  1. CU3AK

    CU3AK Ham Member QRZ Page

    I'm getting this error always and I can't get forward in the process. I already follow the instructions as it showns the link and nothing.
    I tried to check on the web for this error and nothing, not even in the ARRL page. Or I'm looking wrong.
    Can someone help me with this pse ... tnx

    Certificate request processor result:
    Started processing your New Certificate Request.
    For call sign: CU3AK
    For DXCC Entity: AZORES (149)
    For QSOs not before: 1984-07-19 00:00:00
    For QSOs not after:
    Call sign, DXCC Entity and QSO date range don't match up
    **Your certificate request contains error(s); please correct and resubmit.
    See http://www.arrl.org/fixcert for more information.
    Here you can upload a certificate-request (.TQ5) file.

  2. N8MSA

    N8MSA Premium Subscriber QRZ Page

    Good morning Eloy -

    I recommend that you contact ARRL LoTW support team directly:

    They have been very helpful in correcting a couple of minor issuses that I had.

    Good luck!
  3. CU3AK

    CU3AK Ham Member QRZ Page

    Hi Michael, N8MSA,

    Thanks for the tip. I just finished to send an e-mail to ARRL.

  4. CU3AK

    CU3AK Ham Member QRZ Page

    I sent the e-mail on the 6th until today nothing received. Are they usually that slow ?

  5. N8MSA

    N8MSA Premium Subscriber QRZ Page

    No, they usually get back to me within an hour. I'm sending you a PM.
  6. AC0FP

    AC0FP Ham Member QRZ Page

    I had a tq.5 problem with lotw several years ago, never heard back from the ARRL. I always assumed it was because I was not a member at the time.

  7. K7MH

    K7MH XML Subscriber QRZ Page

    It would seem to indicate that the date you used (not before: 1984-07-19 00:00:00)
    may include a range of time for which your callsign was a callsign not assigned to Azores, or not assigned to you.

    You need to be sure to use the correct date of your current callsign being issued or the date of your first QSO
    with that specific callsign and that the callsign at the time you use was issued to the Azores
    and not some other DXCC entity.

    You cannot overlap the range of dates that you have had the callsign, nor if it was previously assigned to some other
    entity and later transferred to yours during the range of dates you specify.

    Without all the specifics to your callsign, I can only make an educated guess as to what the problem is
    but I have heard of this being the problem before sometimes with Russian callsigns.
    Last edited: Dec 12, 2012
  8. N1JGE

    N1JGE Ham Member QRZ Page

    Told me something along the line that I didn't have computor skills. They are probably right I still don't have LOTW and that was two years ago.
  9. CU3AK

    CU3AK Ham Member QRZ Page

    Thanks for the information ..... I solved this problem. I have enter the date 1986/01/01 and all was ok. The new callsign was issue yet during the year 1985, but seems that arrl has it only after this date. Since I only have a few qso's in 1985, I will not miss nothing.

    N8MSA thanks for the pm. I will keep the information for further information that I may need.

    73 de
  10. ZL2HAM

    ZL2HAM Ham Member QRZ Page

    You don't have to be an ARRL member to use LoTW.
Thread Status:
Not open for further replies.

Share This Page