Joining a database to an availability group can fail with Availability Group Error 35250. Here is why it shows up in the wizard and how I fix it.
SQL SERVER – TCP Provider – An Operation On a Socket Could Not be Performed Because the System Lacked Sufficient Buffer Space or Because a Queue was Full
Sometimes, I am contacted by blog readers via email and trust me, I get to learn something new. One of my blog reader contacted me for below error about buffer space.
Finding Which Network Protocol Each Session Uses
Before you switch off a protocol, find out who still uses it. Two short queries show how each session connected, and why the address is not a person.
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.