Browse by Tags
Secure connection to SQL Server can be enforced by different ways, e.g. forcing encryption by using “ ForceEncryption” property under the Network Configuration in the server. But this setting will force all clients to use encryption and any client that
Read More...
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
Read More...
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
Read More...
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
Read More...
Endpoint configuration seems to be creating some confusion. I hope that this will clarify some of the behavior as it applies to TCP endpoints. With a default configuration of SQL Server, try the following: > select name, port, is_dynamic_port, state
Read More...
Lately we have noticed many misunderstandings surrounding the usage of the Data Source keyword in connection strings, caused by people generalizing from an example demonstrating a connection string for local connectivity and creating their own connection
Read More...
Sometimes we are asked about the possibility of configuring SQL Server protocols through PowerShell. In SQL Server 2008, the sqlps tool incorporates WMI and SMO into this powerful Windows administrator tool, making it easy to manage SQL Server protocols
Read More...
Some customers have reported connection failure because of wrong TDS version. The client application gets the following error message: (or similar depends on the protocol used) A connection was successfully established with the server, but then an error
Read More...
On a Windows Cluster it is possible to install a SQL Server Cluster, which will be a separate entity with disctinct Virtual Server Name, IP address, and pipe name. The nodes of the SQL Cluster must be able to communicate with one another. This communication
Read More...
SQL Server 2008 contains a new feature designed to help troubleshoot particularly tricky connectivity problems. This new feature, the Connectivity Ring Buffer, captures a record for each server-initiated connection closure, including each kill of a session
Read More...
Understanding the error message: “Login failed for user ''. The user is not associated with a trusted SQL Server connection.” This exact Login Failed error, with the empty string for the user name, has two unrelated classes of causes, one of which has
Read More...
We have been seeing and trying to resolve SQL connectivity issue all the time. I guess it would be helpful if we can put some guidance on how to resolve connectivity issues. Here comes a proposal based on my experience. Basically, when you failed to connect
Read More...
We see a couple of cases where customer could not connect to named instance on X64. They all have the following symptons. 1) Customer has no problem to connect X86 instance on the same server machine even if it's a named instance. Customer can even connect
Read More...
Sporadic “Connection forcibly closed by remote host” errors with SQL Server connections can be very difficult to troubleshoot and resolve. This blog post is targeted at diagnosing TOE/Chimney issues that may lead to this client error message. Chimney
Read More...
After installing SQL Server 2008, some users might notice that sqlbrowser.exe is installed under %ProgramFiles%Microsoft SQL Server\90\Shared, rather than %ProgramFiles%Microsoft SQL Server\100\Shared as some users expect. When setup fails for some reason,
Read More...
