Check a Vessel Report Error

Owned by Karl-André Dalby
Last updated: Aug 10, 2016 by Sofi Jonung (Deactivated)

Short Description

The Check a Vessel Report Error page explains how to check whats wrong with a VRS report when you receive a Vessel Report Error mail. For more detailed information on how VRS is locating port calls see Vessel Report System (VRS) Logic.

Long Description

 

Message in Vessel Report Error mailExplanation
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:

  • Check the combination of reported vessel, voyage reference, reason for call and port (add port id column in Port Rotation list by right clicking on column header -> Add Column -> Port -> Identity fields -> Port Id
  • Is the voyage reference correct? Maybe previous or next voyage reference is being reported?
  • Is there a space in the voyage reference number?
  • This check is not case sensitive, so upper and lower case letters is ok.
  • Is parts of the voyage reference missing. Check the reference in Booking and Operations - Voyage List - Reference column.
  • Is departure fixed set for previous port calls? If not, check departure fixed manually.
  • Is departure fixed set for the reported port call? If yes, uncheck departure fixed manually.

If none of the above helps, take a look at how VRS is locating port calls: Vessel Report System (VRS) Logic

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:

  • Is departure fixed set for previous port calls? If not, check departure fixed manually.
  • Is departure fixed set for the reported port call? If yes, uncheck departure fixed manually.
  • Is the correct vessel used in report?
  • Is the correct ports used in report?
  • If Departure report, is reported next port matching next port in VMS?

If none of the above helps, take a look at how VRS is locating port calls: Vessel Report System (VRS) Logic

No departure port call found for the reported date and vesselVRS can not find departure report. Voyage may be missing in the schedule or all departure dates are fixed.
Can not find a matching departure port.VRS can not find departure report. Voyage may be missing in the schedule or all departure dates are fixed.
Can not find next arrival port call.The departure port call is located, but the next arrival port call cannot be located. Check reported next arrival port.
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-inputTechnical 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.