%menu.branch% System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception: The network path was not found --- End of inner exception stack trace --- at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.Open() at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) at Logic.Hoopla.DataInterface.RunProcedure(String Command, Hashtable Parameters) --- End of inner exception stack trace --- at Logic.Hoopla.DataInterface.RunProcedure(String Command, Hashtable Parameters) at Logic.Hoopla.Tags.Menu.createXmlMenuObject() at Logic.Hoopla.Tags.Menu.processMenu_Branch() at Logic.Hoopla.Tags.Processor.GetTagContent(String TagCode) at Logic.Hoopla.Tags.Extractor.internalProcessContent(String UnprocessedContent, String StartTag, String EndTag) -->

Harbour Authority

Navigation Aims

To improve and promote continuously the safety of navigation within the Humber harbour area.

Navigation Objectives

  • Operate a Vessel Traffic Management Information Service (VTMIS). This is the vessel through which the Competent Harbour Authority manages the passage of vessels navigating through the harbour.

  • Operate a Vessel Traffic Service (VTS). This is the vehicle through which the Competent Harbour Authority monitors and regulates navigation, providing vessels with the necessary information or advice to ensure safe passage through the harbour.

Navigation Roles

The key players who fulfil the objectives of the VTS are the VTS Manager, 10 Assistant Harbour Masters and 7 Vessel Traffic Services Operators, supported by the 11 Marine Information Officers.

Navigational Safety

ABP HES, as the Competent Harbour Authority, operates a bespoke system to safely manage, monitor and control the safety of navigation on the river, which is called Port and Vessel Information System (PAVIS).

The system provides a fully-integrated administration and information system for pilotage, VTS and the VTS support (Data Centre) and is linked to the external stakeholder facing element, Agents Online. Agents Online is a system through which ships agents can book, amend and update their vessels arrival, movements and departure information.