Microsoft SQL server error:233



1. Login with windows authentication.
2. Right click on the Instance name - Server Properties
3. Security page
4. Set the Server Authentication - 'SQL Server and Windows Authentication mode'
5. Restart the SQL Service.

Then close the sqlserver and restart. It should work.



if the above steps donot work then try thebelow ones:

Make sure the user is not disabled

1. Login as an Administrator into the SqL Server
2. Expand Security/ Logins folder
3. Right Click on the particular user and go to properties
4. Click Status Permission: Granted
Login : Enabled



Mj Machuisa wrote:

Error in SQL Connection
14-Dec-09

A 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: 223)

Previous Posts In This Thread:

On Wednesday, February 06, 2008 4:24 PM
saw wrote:

Connection Established Successfully..Error during the log process
Hello,

When trying to connect to the SQL SERVER 2005 through Microsoft SQL Server
Management Studio Express, I get the following error:

Cannot connect to (SERVER NAME) which both are on the same machine, I am
using one machine for everything since it is a lab machine.

Additional Information:
A 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: 223)

This error prevents my application on the same server machine from
connecting to the sql server on the same machine.

Please let me know what I can do to correct the issue.

Your help is greatly appreciated.

On Friday, February 08, 2008 1:00 PM
Rick Byham, \(MSFT\) wrote:

Any luck on this?
Any luck on this? I would be interested in knowing what the problem was.
I have documented some of the reasons in Books Online:
http://msdn2.microsoft.com/en-us/library/ms175496.aspx
but these shouldn't occur when you make a local connection.
More reasons would be nice to add to this topic.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"saw" <swexpress(remove)@hotmail.com> wrote in message
news:eo7WuKQaIHA.4476@xxxxxxxxxxxxxxxxxxxxxxx

On Tuesday, April 01, 2008 3:51 PM
Markus Bohs wrote:

I'm having the same problem. Here's my situation.
I'm having the same problem.
Here's my situation. I have SQL 2005 SP2 (3042) DEV Edition and try to
connect through application on the same machine. When using a sql login I get
the error "provider: Shared Memory Provider, error: 0 - No process is on
the other end of the pipe.". In the SQL Errorlog i see failed login messages.
So I tried Integrated Security and I can connect.
You might think that the server is configured to accept only Windows logins,
but in SSMS I can open a connection using the sql account. I already enabled
TCP and Named Pipes but no succes. I also tried other sql accounts but the
same result.
When I change the connection string to a different server the sql login
works fine.

For the moment I use Integrated Security as a workaround, but I sincerely
pray I never have this issue on a production server.

Markus
"Rick Byham, (MSFT)" wrote:

On Tuesday, April 01, 2008 4:07 PM
MarkusBohs wrote:

Just found something very weird.
Just found something very weird.
When I use a sql login with a name of 8 characters I get the error.
If I use a shorter login name it works fine. The same with a longer
loginname.
Only 8 character like "TestUser" causes the problem.

Markus
"Markus Bohse" wrote:

On Wednesday, April 02, 2008 11:33 AM
Rick Byham, \(MSFT\) wrote:

Very weird. Sorry, I have no suggestions.
Very weird. Sorry, I have no suggestions.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

On Tuesday, May 12, 2009 8:16 PM
Roy Higgs wrote:

8 chars too
The same thing is happening for me. Trying to connect on the same server and my username is 8 characters. If that is indeed the cause chalk this one up as one of the wierdest bugs ever!!!

On Tuesday, May 12, 2009 8:20 PM
Roy Higgs wrote:

Still happens with 7 chars
Alright, just tried it with a username of 7 chars and still get the issue. Back to the drawing board.

On Monday, December 14, 2009 7:00 AM
Mj Machuisa wrote:

Error in SQL Connection
A 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: 223)


Submitted via EggHeadCafe - Software Developer Portal of Choice
Store ASP.NET Site Visitor Stats in MongoDb
http://www.eggheadcafe.com/tutorials/aspnet/3a73c6de-82a1-4690-a7aa-d0eda58203f7/store-aspnet-site-visitor-stats-in-mongodb.aspx
.



Relevant Pages

  • Re: Connection issues between .Net framwok and SQl Express 2005
    ... You will no longer need the database MDF file name in the connection string. ... simply attach the ASPNETDB.mdf to SQL Server permenantly, ... as USER INSTANCE on existing SQL Server Express, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Performance of ODBC
    ... if you have a software firewall; forward 1433/1434 to your server ... I've now created my own server with SQL Server 2005 Express, ... glitch concerns the Upsizing Wizard. ... I originally set up my ODBC connection via ...
    (microsoft.public.access.adp.sqlserver)
  • Re: SQL User SID format?
    ... When you move databases to another server, you can remap users to logins ... capability to remap a user to a login with new ALTER USER syntax - I ... The new ALTER USER syntax works for remapping both SQL and Windows ... this means you already have access to a SID from the syslogins catalog; ...
    (microsoft.public.sqlserver.security)
  • SQL 2005 Express and VS .Net 2003 wizard error More options
    ... Open the server explorer panel ... Go to the Provider tab and select SQL NAtive Client (DON'T use oledb ... Go back to the Connection tab and carry on setting up the connection ... I have installed Visual Studio 2005 Professional and then Visual Studio ...
    (microsoft.public.sqlserver)
  • Re: Timeout problem with SS2K, VS03
    ... I noticed calls in sql profiler: ... This is the server side debug stored procedure. ... a timeout issue that I cannot identify the source of. ... transaction is committed and the connection is closed cleanly and all ...
    (microsoft.public.dotnet.framework.adonet)