Short Description
The Debug Vessel Report Error page explains how to check whats wrong with a VRS report when you receive a Vessel Report Error mail.
Chapter Contents:
Long Description
Message in Vessel Report Error mail | Explanation |
---|---|
The port reported by vessel, X (id: 123456). Does not match the port in Dataloy: Y (id: 234567) | This error needs investigation by VRS user. It's possibly one of the below issues:
|
No port call found for this combination of vessel, voyage number, reason for call and port where departure fixed is not set | This error needs investigation by VRS user. It's possibly one of the below issues:
|
No departure port call found for the reported date and vessel | |
Can not find a matching departure port. | |
Can not find next arrival port call. | |
javax.mail.MessagingException: * BYE [UNAVAILABLE] Temporary System Error; | Technical Gmail problem. This problem will solve itself and its not necessary to contact Dataloy. |
javax.mail.MessagingException: Remote host closed connection during handshake; | Technical Gmail problem. This problem will solve itself and its not necessary to contact Dataloy. |
com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input | Technical problem. Message or parts of message is missing. Master should resend the report. If problem persists raise a support ticket on support.dataloy.com. |
com.fasterxml.jackson.databind.exc.InvalidFormatException: Can not construct instance of java.util.Date from String value '15.06..2016.13:00': not a valid representation (error: Failed to parse Date value '15.06..2016.13:00': Unparseable date: "15.06..2016.13:00") | Technical problem. Date format is wrong. Master should resend the report. If problem persists raise a support ticket on support.dataloy.com. |