I have installed SQL Server 2005 on a Windows 2003 Server box. When I\nlog in to the Windows 2003 Server as a user other than Administrator,\nand attempt to login to the SQL Server, as the "sa" user, via\nMicrosoft SQL Server Management Studio, using "SQL Server\nauthentication" mode, I get the following message:\n\n-\-\- MESSAGE BEGINS -\-\-\nA connection was successfully established with the server, but then an\nerror\noccurred during the login process. (provider: Shared Memory Provider,\nerror:\n0 - No process is on the other end of the pipe.) (Microsoft SQL\nServer,\nError: 233)\n-\-\- MESSAGE ENDS -\-\-\n\nThough I can't absolutely confirm this, a colleague of mine, who set\nup the Windows Server 2003 box, tells me that, when he logged in to\nthe box as Administrator, he was able to log in to SQL Server 2005 as\n"sa" user.\n\nI went to the "Surface Area Configuration for Services and\nConnections" and\nthe "Remote Connections", under "Database Engine", is set to "Using\nTCP/IP\nonly".\n\nAlso I checked "SQL Server Configuration Manager", under "SQL Server\n2005\nNetwork Configuration" -> "Protocols for BSERVER", and "Shared\nMemory" and "TCP/IP" are the only two "Enabled". "Named Pipes" and VIA\nare "Disabled". Under "SQL Native Client Configuration-\->Client\nProtocols", "Shared Memory", "TCP/IP", and "Named Pipes" are all\nenabled, and in that order. "TCP/IP" has a\nDefault Port of 1433.\n\nAny ideas as to how to resolve this issue? I'd very much appreciate\nany insights.