We would like to hear your opinion…

Dear SQL Server developers and users:   It is this time of the year when we, in the SQL Connectivity product team, take a step back, review the priorities and goals for the long term and identify areas that will benefit from investments.   We view you and your organization as a key stakeholder in…

2

Connection from a Windows Service could be blocked by firewall even if firewall is disabled

Recently, I worked on a customer issue. The customer encountered an “error: 26 – Error Locating Server/Instance Specified” error  although he has applied/verified every steps I posted in the blog:http://www.bing.com/search?q=error+26+blog+protocol&form=QBRE&qs=n After some investigation, we found that: Windows Firewall is disabled on both server and client machine. Running Portqry from a command window also show that…


Understanding the error “An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.”

This error message, which is associated with the Winsock error WSAENOBUFS and actually comes from Windows rather than SQL Server directly, has two well-understood root causes. However, it still stumps people today, probably because  there is no single source which explains both root causes and offers solutions for both. Here is a description of the two…