Invalid State

Discussion in 'Logbook User Forum' started by KK4GGL, Dec 1, 2014.

Thread Status:
Not open for further replies.
ad: L-HROutlet
ad: l-rl
ad: L-MFJ
ad: K5AB-Elect-1
ad: MessiPaoloni-1
ad: Subscribe
ad: Left-3
ad: Left-2
  1. KC9LOX

    KC9LOX Ham Member QRZ Page

    since I'm not a xml member I upload my adi file for my log updates. Now I can not do this since this update. I think I'm done using the qrz logbook. I upload more for other stations that use qrz but I'm about ready to call it quits.
     
  2. W1DQ

    W1DQ Logbook Administrator Volunteer Moderator Volunteer DX Helper Platinum Subscriber QRZ Page

    Sorry for the inconvenience. Your uploads are appreciated.

    The most recent system change that resulted in this problem has been corrected. Simply re-import your logbook ADIF file. Also, check the logbook start and end date as it seems you have a few QSOs that precede the start date and are being rejected.

    Open your logbook, click on SETTINGS then PROPERTIES, scroll down and adjust date as necessary.
     
  3. KB1ZBA

    KB1ZBA XML Subscriber QRZ Page

    Same Problem, I can't import my ADI file. This is what I'm returned with:

    QRZ has completed the import processing of your logbook file.

    File name: L03132014.ADI (25 records)

    Destination Book(s):
    "KB1ZBA Logbook" (5586)


    Started on: Wed Dec 3 16:09:00 2014
    Finished on: Wed Dec 3 16:09:01 2014


    ------------------------------------------------------------------------------
    ------------------------------ Book Breakdown --------------------------------
    ------------------------------------------------------------------------------
    Book: "KB1ZBA Logbook" (5586)


    Import Results:

    0 QSO's were inserted
    0 duplicates were replaced
    0 duplicates ignored
    25 errors.


    System Messages:

    Error 1. Insert error on record: DH1TT de KB1ZBA on 2014-12-03 15:03:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 2. Insert error on record: F5VIX de KB1ZBA on 2014-12-03 14:55:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 3. Insert error on record: OZ5HP de KB1ZBA on 2014-12-03 14:52:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 4. Insert error on record: IT9MOK de KB1ZBA on 2014-12-03 14:48:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 5. Insert error on record: DO8ABS de KB1ZBA on 2014-12-03 14:41:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 6. Insert error on record: EB5GC de KB1ZBA on 2014-12-03 14:39:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 7. Insert error on record: F5HLQ de KB1ZBA on 2014-12-03 14:37:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 8. Insert error on record: DL5NAD de KB1ZBA on 2014-12-03 14:35:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 9. Insert error on record: DO4MTB de KB1ZBA on 2014-12-03 14:31:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 10. Insert error on record: SV2HNN de KB1ZBA on 2014-12-03 14:28:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 11. Insert error on record: EC5SP de KB1ZBA on 2014-12-03 14:19:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 12. Insert error on record: UT3EV de KB1ZBA on 2014-12-03 14:17:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 13. Insert error on record: UX9IX de KB1ZBA on 2014-12-03 14:12:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 14. Insert error on record: SQ5MJB de KB1ZBA on 2014-12-03 14:02:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 15. Insert error on record: SP8AWL de KB1ZBA on 2014-12-03 13:54:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 16. Insert error on record: SP7VW de KB1ZBA on 2014-12-03 13:48:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 17. Insert error on record: SP8BJU de KB1ZBA on 2014-12-03 13:32:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 18. Insert error on record: DL6YRA de KB1ZBA on 2014-12-03 13:29:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 19. Insert error on record: IK2ZEC de KB1ZBA on 2014-12-03 13:26:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 20. Insert error on record: ON3AHA de KB1ZBA on 2014-12-03 13:22:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 21. Insert error on record: 9A5BSD de KB1ZBA on 2014-12-03 13:20:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 22. Insert error on record: IK5DHL de KB1ZBA on 2014-12-03 13:18:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 23. Insert error on record: G1EIX de KB1ZBA on 2014-12-03 13:12:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 24. Insert error on record: UA6YD de KB1ZBA on 2014-12-03 12:52:00.
    Invalid 2-letter state code given for other party: Connecticut
    Error 25. Insert error on record: OH5EP de KB1ZBA on 2014-12-03 12:47:00.
    Invalid 2-letter state code given for other party: Connecticut

    ------------------------------------------------------------------------------
    ---------------------------------- Notes -------------------------------------
    ------------------------------------------------------------------------------

    Duplicates are determined when a match exists between the incoming record and an
    existing record in the database where:

    The two callsigns match -and-
    The operating BAND is the same -and-
    The operating MODE is the same -and-
    The QSO DATE is the same -and-
    The QSO Start Time is the same to the minute.

    Duplicate Rules:

    If the duplicate has not yet been confirmed, the incoming record REPLACES the existing one.
    If the duplicate is of a confirmed record, it is IGNORED.


    73,

    The QRZ Team
     
  4. W1DQ

    W1DQ Logbook Administrator Volunteer Moderator Volunteer DX Helper Platinum Subscriber QRZ Page

    It appears that the state code in your ADIF file is not in accordance with ADIF protocol that requires the following code and not the full alphabetic word:
    Per: www.adif.org

    (also refer to: http://forums.qrz.com/showthread.ph...t-QRZ-logbook-to-accept&p=3340242#post3340242)

    [TABLE="class: cms_table_primaryadministrativesubdivisiontable"]
    [TR="class: cms_table_primaryadministrativesubdivisiontabletitle"]
    [TH="colspan: 5"]Enumeration for Country Code 291 (United States)[/TH]
    [/TR]
    [TR="class: cms_table_primaryadministrativesubdivisiontablecolumntitles"]
    [TH]Code[/TH]
    [TH]Primary Administrative Subdivision[/TH]
    [TH]CQ Zone[/TH]
    [TH]ITU Zone[/TH]
    [TH]Prefix[/TH]
    [/TR]
    [TR]
    [TD]CT[/TD]
    [TD]Connecticut[/TD]
    [TD]05[/TD]
    [TD]08[/TD]
    [TD]W1[/TD]
    [/TR]
    [TR]
    [TD]ME[/TD]
    [TD]Maine[/TD]
    [TD]05[/TD]
    [TD]08[/TD]
    [TD]W1[/TD]
    [/TR]
    [TR]
    [TD]MA[/TD]
    [TD]Massachusetts[/TD]
    [TD]05[/TD]
    [TD]08[/TD]
    [TD]W1


    [/TD]
    [/TR]
    [/TABLE]
     
  5. N0AMT

    N0AMT Platinum Subscriber Platinum Subscriber QRZ Page

  6. KC9YPR

    KC9YPR Platinum Subscriber Platinum Subscriber QRZ Page

    Me too...Me too...
     
  7. N0AMT

    N0AMT Platinum Subscriber Platinum Subscriber QRZ Page

    I have now made it so that if your ADIF incorrectly contains the entire state name such as "Arizona" instead of the ADIF specifications requirement for the 2-letter state code "AZ" it will correctly resolve the state to AZ.

    There should be no more "Invalid State" errors when importing an ADIF, or manually adding a QSO unless the state you enter is truly invalid.
     
Thread Status:
Not open for further replies.

Share This Page