Login failed because the server was in script upgrade mode, stuck while deleting collection set ‘Utility Information’. Here is how we got past it.
SQL SERVER – Event ID 1045 – No Matching Network Interface Found for Resource ‘Cluster IP Address’ IP address ‘10.10.10.10’ (Return Code was ‘5035’)
A new node could not bring an AlwaysOn multi-subnet listener online, with Event ID 1045: no matching network interface found. Here is the cause and the fix.
SQL SERVER – AlwaysOn Listener Error – The WSFC Cluster Could Not Bring the Network Name Resource With DNS Name ‘DNS name’ Online
Creating an AlwaysOn listener failed: the WSFC cluster could not bring the Network Name resource with DNS name online. Why it happens and how to fix it.
SQL SERVER – Maintenance Plan failing with 0x80131904 – A network-related or instance-specific error occurred while establishing a connection to SQL Server.
After patching, a client found every Maintenance Plan failing with 0x80131904, a network-related or instance-specific error. Here is the cause and the fix.
SQL SERVER – Unable to Start SQL Service – Server TCP provider failed to listen on [‘any’ 1433]. Tcp port is already in use.
One of my SQL instances would not start: Server TCP provider failed to listen on port 1433, TCP port is already in use. How I found what held the port.
SQL SERVER – FIX – Error: 26023 – TCP Port is Already in Use
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.