Import errors: causes and fixes
What to do when Avelsta rejects an NKE log: unrecognised format, corrupted file, no NMEA sentence, no usable measurement, incomplete upload, log without a date.
The essentials
A file in error never prevents the others from being processed. The message shown on the file, in the import details, gives the cause.
- Open My imports, then the import concerned.
- Read the message of the failed file.
- Apply the fix from the table below, then upload the file again in a new import if needed.
Going further
Messages and fixes
| Message | Cause | What to do |
|---|---|---|
| Unrecognised format | The file is neither an NKE Box WiFi .LOG nor an NKE Processor HR .nkz | Check that it is the raw file from the box, not converted |
| Corrupted file: n of m sampled sentences are unreadable | Too many NMEA sentences have a wrong checksum | Retrieve the file from the box again; a damaged copy cannot be repaired |
| No NMEA sentence in this file | Empty file, or not a sailing log | Check the file; an empty .LOG is common when recording was started then stopped straight away |
| No record in this .nkz file | Empty or corrupted .nkz | Retrieve the file again |
| No usable measurement | No position, speed or wind in the file | Nothing to analyse: the file can be ignored |
| This log has no date | No usable GPS time or clock | Enter start and end in the import details (account required) |
| The file arrived incomplete (n bytes received out of m) | The upload was cut off before the end | Upload the file again in a new import |
| The file never reached the server | Tab closed or connection lost during the upload | Upload the file again |
| The integrity check failed | File probably corrupted | Retrieve the file again |
| Building the sessions failed | Error while building the sessions | Retry the failures; if it happens again, contact us |
| Technical error during processing | Server-side incident | Try again; if it happens again, write to contact@avelsta.app with the details shown |
Upload refused before sending
| Message | Fix |
|---|---|
| n files dropped, 500 max per upload | Upload your files in several batches |
| n MB upload: 200 MB max per upload without an account | Upload fewer files at once, or create an account |
In both cases, nothing was sent.
The import is done but no session appears
The logs were read but hold no sailing: boat at the dock for the whole recording, or less than 5 minutes of sailing per file. This is normal for a test log or a recording in the harbour. See How sessions are built.
A file is “Already imported” although I never uploaded it
Its content is identical to a file already imported on this boat, even under another name. It is ignored to avoid duplicates.