%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) -->
Potential Risk Report
Potential Risk Report Marine Safety Management System
The Port’s Marine Safety Management System (SMS) endeavours to reduce the risks arising from the day-to-day operations in the harbour and Pilotage areas to as low a level as reasonably practical.
In accordance with the requirements of the Port Marine Safety Code the Port has undertaken, in consultation with stakeholders, a Formal Safety Assessment of the hazards in the port, assessed the associated risks and introduced or verified control measures, to minimise the risks.
To ensure the control measures remain valid, it is essential that all the Port’s Stakeholders (Port Staff, PEC holders, tug Masters, Agents, berth operators, recreational users) advise the Harbour Authority of ‘potential risks’, which, in their opinion, could indicate a weakness in a particular control measure or risk assessment.
This is an iterative process, and will only be effective if all our stakeholders participate in it. The goal for all of us is to achieve an incident free harbour and pilotage area.
Please use this pro-forma to report any ‘potential risks’ you encounter in harbour or pilotage waters.
(This form does not preclude the requirement for Pilots and PEC holders to complete a Pilotage Incident Report (PIR1) in accordance with the Port’s Pilotage Directions)
