%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) -->

Public Consultation

ABP HES will consult with all those parties, individual and corporate, which have a legitimate interest in the estuary in order to ensure that our duties and responsibilities and the way we undertake them are widely recognised.

ABP HES will consult in such a way that the views expressed by others are understood and, where required, acted upon.

ABP HES consults with river users, interested parties, ABP employees, the general public and authorities that are involved in the management of the Humber environment, e.g. The Humber Liaison Committee. They consult for a number of reasons:

  1. To aid passage of information between ABP HES and all other associated groups.
  2. As part of the commitment ABP and Humber Estuary Services has made to the compliance with the Port Marine Safety Code.
  3. To provide a method to allow interested parties to contribute towards the safe operation of the harbour.
  4. To comply with legislation, viz, Pilotage Act 1987 (paragraph 7, section 4) and Harbours Act 1964 (9,6) (Annexes 4 & 5).

If you wish to give us feedback now, click here.

Consultation - Humber Liaison Committee