After patching, database mirroring stopped and the ERRORLOG showed Error 26023: TCP Port is already in use on 5022. Here is how we found the cause and fixed it.
SQL SERVER – Fix Connection Error – [Microsoft][ODBC SQL Server Driver][DBNETLIB][ConnectionOpen(Connect())
A connection error on a named instance that works by port but not by name. What SQL Browser answers on UDP 1434, and why local tests prove nothing.
SQL SERVER – Database Mirroring Error -The Specified Network Name is No Longer Available
A client’s ERRORLOG showed database mirroring error 1474, ‘The specified network name is no longer available’. The cause was outside SQL Server.
SQL SERVER – Unable to Bring Resource Online – Error – Could Not Find Any IP Address that this SQL Server Instance Depends Upon
A clustered SQL Server could not find any IP address it depends upon, so it would not start. Here is how to fix it and bring the resource online.
Network Packet Size: When a Bigger Packet Helps Large Results
Test network packet size on a specific SQL Server connection, verify the negotiated value, and compare large-result performance carefully.
SQL SERVER – Fixing Annoying Network Binding Order Error – Notes from the Field #112
Ryan Adams explains a critical SQL Server error about network binding order and shows how to fix it in this Notes from the Field episode.
SQL SERVER – FIX – A connection cannot be made to redirector. Ensure that ‘SQL Browser’ service is running. (Microsoft.AnalysisServices.AdomdClient)
I opened SQL Server Management Studio and instead of a database engine. Below is the error which I received for SQL Browser: