Welcome to the Veson Nautical Knowledge Base. In the Help Center, you can view the same articles and contact support as needed.
Voyage Reporting - Position Report Errors - Arrival, Departure, or Noon
FAQs > Error Messages > Voyage Reporting - Position Report Errors - Arrival, Departure, or Noon
Voyage No. can be explicitly set or determined by inference by the system.
Error Text | Comments | Resolution |
|---|---|---|
Position Report missing ROBs | Appears if user enters all zeroes in the ROB control (with the possible exception of SPOT and RELT voyages) | May have Track Bunkers config setting enabled incorrectly. |
Report designated as In Port, but date/time places it at sea. | The Noon report was specified as In Port, but the date/time on the report corresponds to an At Sea leg of the voyage. | Verify that the form’s date and port match the voyage itinerary. |
Report designated as At Sea, but date/time places it in port. | The Noon report was specified as At Sea, but the date/time on the report corresponds to an In Port leg of the voyage. | Verify that the form’s date and port match the voyage itinerary. |
ROB of xxx.xx for fuel type HFO is greater than previous value of xxx.xx | Can be disabled by global config flag | Master entered wrong ROB on current or previous report, or enable Allow Negative Consumption in config. |
Aux engine consumption exceeds total consumption for fuel type HFO | The value entered for AUX consumption is greater than the total consumption (previous ROB - new ROB). | Master entered wrong value; resubmit with correct value. |
Consumption for fuel type HFO is negative; cannot specify consumption breakdown | Master entered inconsistent values. Resubmit without consumption breakdown. | |
Bunkers ROB for HFO was entered as xxx.xx, but computed (from last ROB, consumption and bunkers received) as xxx.xx. | Master entered inconsistent values for ROB, consumption or bunkers received. | The system attempts to compute correct values but should be validated by Operator before resubmit. |
Voyage has no arrived ports. | Departure form was not approved before completing the voyage. | Set the voyage status back to commenced or manually input the information from the departure form if needed. |
Autonoon.exe Error Codes and What They Mean
Error Code | Technical Description |
|---|---|
-101 | GENERAL_ERROR |
-102 | DB_CONNECT_FAILED |
-103 | INVALID_XML |
-104 | DB_ERROR |
-105 | READ_REPORT_ERROR |
-106 | GENERAL_VALIDATION_FAILED |
-107 | VALIDATE_DELETE_FAILED |
-108 | STORE_RPT_FAILED |
-109 | INVALID_LEG_SEQ |
-111 | VOYAGE_CLOSED |
-112 | MISSING_TYPE_TIME |
-113 | UNKNOWN_RPT_TYPE |
-114 | MISSING_ROB |
-115 | SET_CPMNOONLIST_FAILED |
-116 | COMMENCE_VOYAGE_FAILED |
-117 | UPDATE_VOYAGE_FAILED |
-118 | MISSING_VOYAGE_PORTCALL |
-119 | RPTTYPE_FUNCTION_MISMATCH |
-121 | MISSING_ACTIVITY_NAME |
-122 | MISSING_ACTIVITY_SEQ |
-123 | MISSING_ACTIVITY_TIME |
-131 | MISSING_CARGO_SEQ |
-132 | MISSING_CARGO_NAME |
-133 | MISSING_CARGO_ACTION |
-134 | MISSING_CARGO_QTY |
-135 | PORT_FUNCTION_MISMATCH |
-136 | BERTH_NOT_FOUND |
Still need help? Visit the Veson Nautical Help Center.
Copyright © 2017-2023 Veson Nautical LLC All Rights Reserved - Privacy Policy Terms & Conditions Licenses