Welcome to the Veson Nautical Knowledge Base. In the Help Center, you can view the same articles and contact support as needed.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Error Text

Comments

Resolution

Could not find a unique cargo of CARGO (discharging) for this port call.

Ambiguous port cargo. If there are no voyage cargoes associated with this voyage (could happen from a TCO voyage), checks if a single port cargo matches on cargo type/function on this voyage leg, and this error results if not found.

 

Cargo row n, No cargoes of type CARGO are associated with this voyage.

No port cargo or voyage cargo (vfixcar) for this voyage in IMOS.

Make sure a Cargo is specified for the port call in the IMOS Voyage Manager.

Cargo row n, Multiple cargoes of type CARGO are associated with this voyage, please select a specific voyage cargo within the row's details.

No port cargo, ambiguous voyage cargo.

Select a specific Cargo and resubmit.

No berth named BERTH exists at port PORT

 

In the IMOS Voyage Manager for the specified voyage and port call, make sure the port has the required berth defined.

Unit mismatch: input unit but cargo’s actual units are unit.

Port cargo exists, but within different units than user specified

Change form units to match port cargo as defined in IMOS Voyage Manager.

Could not find a previous loading for port cargo cargo to discharge for this port call.

Only for TCO voyages with no pre-existing port cargoes (i.e., port cargoes are being created by Veslink)

Correct and resubmit.

Cargo row n, Same stowage location specified more than once.

If using the stowage subcontrol, can’t specify the same tank or hold number twice in the same cargo row.

Correct and resubmit.

Too many holds specified in stowage breakdown for CARGO (limit 8).

 

Limitation of the Veslink integration in IMOS, not of IMOS itself.

Correct and resubmit.

Cargo row n, CARGO (discharging) is associated with an invalid PortCargoID.

Tends to happen on form resubmits, if the cargo handling line was deleted in IMOS since the first submit (even if later re-created).

Add Cargo Handling line back into IMOS.

Warning: letter of protest is too long and will be truncated by autonoon.

Letters of protest must fit on five lines of 100 characters wide.

Shorten letter of protest text.

Error: no cargo name found with Id N

 

Cargo name referenced on the vessel has since been deleted from IMOS.

Add Cargo back to into IMOS.

  • No labels