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

Buoyage and Beaconage

Floating seamarks deployed on the Humber conform to the International Association of Lighthouse Authorities System "A". This system is used throughout Northern Europe and employs lateral marks "red to port", "green to starboard" and cardinal marks. It was first introduced in the Humber in 1974.The Harbour Master has 113 floating marks at his disposal, of which 29 are floats and 84 are buoys. In addition, 29 shore marks are maintained or monitored by ABP staff. A further 35 shore marks on the River Ouse are maintained by the Port of Goole.

Current Positions of Seamarks

To enable mariners to plot the positions of seamarks and mooring buoys under the control of ABP Humber Estuary Services, as Local Lighthouse Authority, the following list contains details of both the National Grid co-ordinates (OSGB 36 datum), for use with Ordnance Survey maps and Latitude and Longitude (WGS84 datum) geographical positions, which are compatible with GPS satellite receivers.

The list is updated regularly, but users should check the 'corrected' date and any subsequent local Notices to Mariners issued by ABP, in order to ensure that the most up-to-date positions are used. (There have been as many as 90 movements of seamarks in one year).