Handling Key Import Error

• After import, the stats dialog shows failures via Lines With Error.
• Always check:

  • Total Lines
  • Lines With Error
• Total Lines excludes blank and commented lines.

Finding the failing line

• Export the app log.

  • Use Log/Export Log.
• Search for import errors.
• The log includes:

  • line number
  • error reason

Why not show errors on UI:

• Key lists can be large.

  • Up to ~2500 keys.
• UI space is limited.
• Showing all errors is error-prone.

Example: Master Session import error

Scenario:

• MS/KBPK/2-xxxxx.txt contains 100 key lines.
• Lines 33 and 76 resulted in error.
• Export the App log using the "Log/Export Log" menu item and look for the error and line number

Recovery options

1) Creating a new key list

There is no existing dataset on KLD.

Options:

• Option A (recommended)

  • Delete the partially imported key list in the UI.
  • Fix or remove the failing lines in 2-xxxxx.txt.
  • Import again using Create New List.
• Option B (be careful)

  • Keep the partially imported key list on KLD.
  • In 2-xxxx.txt, delete all lines except the failing ones.
  • Fix those lines.
  • Remove all other files under MS/KBPK on the USB.
  • Copy only the corrected 2-xxxx.txt back to MS/KBPK.
  • Import again using Existing Key List.
  • Select the partially imported key list.
  • This appends the corrected keys into the original KLD file.

2) Refilling an existing key list

• Use the same approach as Option B above.
• Keep only the corrected lines on the USB.

Critical rule for refills:

• Do not keep any successfully imported lines or files on the USB.
• Otherwise you will duplicate key data on KLD.
• Duplicates can be a security issue.

  • The same key could be sent to different terminals.