You are currently offline, waiting for your internet to reconnect

Your browser is out-of-date

You need to update your browser to use the site.

Update to the latest version of Internet Explorer

You cannot connect to a local instance of SQL Server on a Windows XP-based computer or on a Windows 2000-based computer when you use "localhost" in the pipe name

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

Bug #: 443555 (SQLBUDT)
SYMPTOMS
On a Microsoft Windows XP-based computer or on a Microsoft Windows 2000-based computer, you use the Named Pipes protocol to connect to a local instance of Microsoft SQL Server 2005 or Microsoft SQL Server 2000. When you use "localhost" in the pipe name, you cannot connect to the instance of SQL Server. Depending on the tool that you use to connect to the instance of SQL Server, you experience one of the following issues:
  • If you use the Osql.exe command-line utility to connect to the local instance of SQL Server 2000, you receive the following error message:
    [DBNETLIB]SQL Server does not exist or access denied.[DBNETLIB]ConnectionOpen (Connect()).
  • If you use the Sqlcmd.exe command-line utility to connect to the local instance of SQL Server 2005, you receive the following error message:
    HResult 0x34, Level 16, State 1Named Pipes Provider: Could not open a connection to SQL Server [52].Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

    Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
Note This issue does not occur on computers that are running Microsoft Windows Server 2003 or later versions of Windows.
CAUSE
This issue occurs because the version of Microsoft Data Access Components (MDAC) that is included with Windows XP and Windows 2000 does not support using "localhost" in a pipe name.
RESOLUTION
To resolve this issue, use one of the following methods:
  • Use an alternative representation of the name of the local host address instead of "localhost". Possible alternative representations include the following:
    • 127.0.0.1
    • "."
    • The actual local host name
  • Use a different connection protocol, such as TCP/IP.
STATUS
This behavior is by design.
MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 929152 - Last Review: 09/17/2011 08:30:00 - Revision: 2.0

  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Standard Edition
  • kbexpertiseadvanced kbtshoot kbprb kbinfo KB929152
Feedback
/html>: none; " src="https://c1.microsoft.com/c.gif?DI=4050&did=1&t=">r(Math.random() * 16).toString(16); })).replace("R", (8 | Math.floor(Math.random() * 3)).toString(16)); var m = document.createElement("meta"); m.content = guid; m.name = "ms.dqid"; document.getElementsByTagName("head")[0].appendChild(m); >