In the service Vessel Notification, in the releases tab, you may receive error messages when declaring a release. Below, the error messages are explained along with advice on which step you can take.
… is not registered or the registration is not verified
The release-to-party that has been entered is not registered as one of your release-to parties.
Advice:
- Make sure the release-to-party registers with you using a customer code. You can refer your customer to the article Register customer code for the Secure Chain.
- Verify the customer code and review whether the link has been created correctly.
- Resubmit the release.
Visit is cancelled
The visit to which the release is linked via the consignment and the container has been cancelled. This has broken the link.
Advice: Make sure the visit is no longer on the release and resubmit the release.
Release has already been cancelled
The release has been cancelled and therefore cannot be cancelled again.
Advice: If the cancellation has not been processed, please contact customer service via the contact form or go to the terminal web portal and cancel the release manually. Then delete the release in Portbase and submit a new release.
Changing the release-to party is only possible by cancelling and creating a new commercial release
It is not possible to change the release-to-party on a release.
Advice: To adjust the release-to-party, cancel the release and create a new release with a new release-to-party.
It is not allowed to declare a release without release to party
It is not possible to create a release without a release-to-party.
Advice: Enter a release-to-party.
Unable to determine which vessel is associated with the release...
The full error message is: Unable to determine which vessel is associated with the release. This means that the visit could not be found by crn or via the consignment and that the vessel was not included in the request.
This error message only occurs at the AMP2 terminal. It is not possible to determine which vessel is associated with the release. The vessel cannot be found by searching on CRN or using the consignment number.
Advice: For releases to the APM2 terminal, clearly indicate which vessel the release belongs to. APM2 expects this. Without this vessel, the release cannot be processed. You can do this by entering the CRN yourself or adding the vessel name in the release.
Release number is required for a new release
Something went wrong while processing the release.
Advice: Please contact customer service via the contact form.
Unable to find manifest for consignment … and container …
No import manifest was found for the provided BL number and container number.
Advice: Resubmit the manifest.
Changing the equipment number is only possible by cancelling and creating a new commercial release
It is not possible to change the container number on a release.
Advice: To adjust the container number: cancel the release and create a new release with the new container number.
Release-to-party must be the same as the declarant
In the case of carrier haulage, the declarant is the same as the release-to-party. When you enter an inland operator, the release-to-party and the party submitting the release must be the same organisation.
Advice: Make sure the release-to-party is filled in with your organisation or remove the inland operator and create a merchant haulage release.
Inland operator … does not have access to the Portbase service
The designated inland operator does not have access to Portbase’s service Hinterland Container Notification.
Advice: Choose another inland operator or ensure that the designated inland operator requests the Portbase service Hinterland Container Notification. Refer your customer to the Portbase website to purchase the service first.
Changing the inland operator is only possible by cancelling and creating a new commercial release
It is not possible to change the inland operator on a release.
Advice: To adjust the inland operator, cancel the current release and create a new release with the new inland operator.
releaseData releaseDeadline is too far in the past to possibly be valid
The specified release deadline is too far in the past and therefore can no longer be valid.
Advice: Enter a release deadline in the future.
releaseData terminalShortName must not be blank
The release must be sent to a terminal, so this cannot be blank.
Advice: Enter a terminal.
Unknown carrier SMDG code
The specified SMDG code of the shipping line is not recognised.
Advice: Enter the correct SMDG code.
Unknown size type
The size type that was provided cannot be found.
Advice: Check whether the correct size type has been entered. If the size type is correct but this error message still appears, please contact customer service via the contact form to ask whether the size type can be added to the database in Portbase.
Unknown terminal SMDG code
The SMDG code provided cannot be found.
Advice: Check whether the correct SMDG code has been entered.
Unknown release-to-party
The release-to-party provided is not recognised.
Advice: Enter a release-to-party from an organisation that is registered with your shipping line in Portbase. Would you like to add a new release-to-party? You can refer your customer to the article Register customer code for the Secure Chain and follow the steps.
Terminal in commercial release (…) doesn't match terminal in cargo data (…). Please change the terminal in the cargo data first.
The terminal in the commercial release is not the same as the terminal on the manifest.
Advice: Make sure the correct CRN is linked to the release and check whether the terminal indicated in the release is also called at in the specified CRN.
Consignment process not found for crn (…), consignmentnumber (…) and equipmentnumber (…)
No consignment was found in the manifest data for the specified CRN number and container number.
Advice: Make sure the CRN in the release matches the CRN under which the consignment and container were manifested.
Related to