RE: Shared Memory Provider error



Hello,

Thank you for posting here.

From the problem description of the post you submitted, my understanding
is: the following error message is received when attempting to log in with
the "SA" account on a SQL Server 2005 Express Server.

"Connection was successfully established with the server, but then an error
occurred during the login process. (provider: Shared Memory Provider,
error: 0 - No process is on the other end of the pipe.) (Microsoft SQL
Server, Error: 233)"

As I understand, you have checked the TCP/IP, Mixed mode authentication, SA
account access but the issue still persists and the Windows authentication
is working. If I have misunderstood about your concern, feel free to let me
know.

Before going further, as you have mentioned that "TCP/IP" is enabled in SQL
Server Configuration Manager tool, I would like to confirm whether the
"Shared Memory" and "Named Pipes" are all enabled as well and "TCP/IP" is
enabled to listen on all IP Addresses.

In addition, I also suggest we manually check the SQL ERRORLOG (the default
path is C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\) to make
sure "Shard Memory" is actually enabled though it have been configured via
Surface Area configuration or SQL configuration manager. If the settings
have already been set to this, please go ahead and then refer to the
following troubleshooting information.

Based on my research and experience, this behavior can also occur when the
server is not configured to accept remote connections. By default, SQL
Server 2005 Express Edition and SQL Server 2005 Developer Edition do not
allow remote connections. At this point, I suggest we

Suggestion 1: Configure the SQL Server 2005 to allow remote connections
====================================================
To configure SQL Server 2005 to allow remote connections, complete all the
following steps:

1. Enable remote connections on the instance of SQL Server.
2. Turn on the SQL Server Browser service.
3. Configure the firewall to allow the relevant network traffic.

This article describes how to complete each of these steps.

How to configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/kb/914277

For more information regarding this error, please visit the following
address in SQL Server 2005 BOOK Online
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqlerrm9/html/201665dc-7ac8-4c19-90d3-
33354c5caa72.htm

However, if this issue still persists, let's try LPC for shared memory
connection and TCP for TCP connection by using sqlcmd.

Suggestion 2: Try the LPC for shared memory connection and TCP for TCP
connection by using sqlcmd.
=========================
1. Click Start, click Run, type cmd, and then click OK
2. At the command prompt, type the following command, and then press ENTER.


sqlcmd -S lpc:<computer name>
sqlcmd -S tcp:<computer name>,<port number>

3. Please check if we can successfully connect to the instance of SQL
Server 2005 by using sqlcmd

For more information regarding the sqlcmd, please visit the following link
in the SQL Server 2005 BookOnline

How to: Connect to the Database Engine Using sqlcmd.exe
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/74b0fb71-7f8e-4171-9431-d075
28532524.htm

Please let me know the results at your earliest convenience. If anything is
unclear in my reply, please don't hesitate to let me know and I will be
glad to help. Thank you for your efforts and time.

Have a nice day!

Best regards,

Adams Qu, MCSE 2000, MCDBA
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Shared Memory Provider error
| thread-index: AceF9LOsaQZoVpacTUOkK5iSW/HguQ==
| X-WBNR-Posting-Host: 136.223.19.49
| From: =?Utf-8?B?VVdpZGUgVXNlcg==?= <iseek2no@xxxxxxxxxxxxxxxx>
| Subject: Shared Memory Provider error
| Date: Mon, 23 Apr 2007 15:14:03 -0700
| Lines: 18
| Message-ID: <6C07D6DF-8001-4CB5-A024-8AFE8E3D700B@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
| Newsgroups: microsoft.public.sqlserver.connect
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.connect:894
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| I am having a problem logging in with the "SA" account on a SQL Server
2005
| Express server (latest service pack). Here is the error message:
|
| "connection was successfully established with the server, but then an
error
| occurred during the login process. (provider: Shared Memory Provider,
error:
| 0 - No process is on the other end of the pipe.) (Microsoft SQL Server,
| Error: 233)"
|
| I hvae Googled this and checked what was recommended; TCP/IP enabled,
Mixed
| mode authentication enable, SA account access enabled. Nothing seems to
fix
| this problem. the server OS is Windows 2003 Standard with SP1. Windows
| authentication is working, but the database server is setup for a
particular
| application using SA.
|
| Any help would be greatly appreciated.
|
| -----------
| Anyone who knows everything, leads a pretty boring life
|

.



Relevant Pages

  • RE: Shared Memory Provider error
    ... I tried the lpc sqlcmd and indeed got an error: ... Shared Memory Provider: The Shared Memory dll used to connect to SQL Server ... An error has occurred while establishing a connection to the server. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Server 2K connection is interrupted regularly, why ?
    ... I've never had connectivity problems at start up of a remote connection. ... > I found that if I turned of Shared Memory in the Client Configuration ... stop and restart SQL Server. ...
    (microsoft.public.sqlserver.connect)
  • Re: Error "SQL Server does not allow remote connections"
    ... The application could not connect to the sql server db. ... network is blocking the connection. ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 ... integratedSecurity, SqlConnection owningObject) +737554 ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Connection from remote computer to network SQL Server
    ... There is no firewall on the W2K machine acting as the SQL server. ... I tried making the SQL machine a "trusted" on the router. ... connection works. ... To find the IP address of your computer inside the network, ...
    (microsoft.public.access.adp.sqlserver)
  • ADO.net Orcas Samples Install Problem
    ... An error has occurred while establishing a connection to the server. ... When connecting to SQL Server 2005, this failure may be caused by the ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, ... or am I better off with a full SQL Server install. ...
    (microsoft.public.dotnet.framework.adonet)