CODEWITHSUNDEEP
sqlsql-server
clumpter
clumpter

Reputation: 1958

SQL Server 2008 Error 233

I'm creating new login in SQL Server 2008 with following sql script:

CREATE LOGIN [xyz] WITH PASSWORD='xyz',
            DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english], 
            CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF

It creates new login successfully. But when I try to login with it using SQL Server Management Studio it fails saying:

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: 233)

What's wrong? How do I solve this issue?

Upvotes: 23

Views: 90131

Answers (14)

GorgE_MirO
GorgE_MirO

Reputation: 554

Here is how I done it, maybe it works for you too.

  1. login Microsoft SQL Server 2012 with windows authentication.

  2. right-click onto the server name in Object Explorer and click Properties

  3. In the new tab click Security

  4. select SQL Server and Windows Authentication

  5. Ok

  6. Close the SQL server management studio.

  7. start+run

  8. write services.msc

  9. search for SQL there and restart all services.

that works for me.

Upvotes: 37

bytedev
bytedev

Reputation: 9099

"A connection was successfully established with the server, but then an error occurred during the login process."

I was getting this problem from sqllocaldb when used from within Docker. The problem was the Docker image was not allocated enough memory. Increasing the memory actually fixed the problem.

Upvotes: 0

James
James

Reputation: 527

After following the examples here and still not getting in, I found that my sa login was disabled. The following got me in: 

Logged back in under windows authentication.  
Expanded Security Tab 
Expanded Logins Tab 
Right-clicked sa and selected Properties
Went to the Status Tab
Under Login: Clicked 'Enabled' radio
Restarted Server and logged in as sa.
This assumes you have set sa password already using
ALTER LOGIN sa WITH PASSWORD = '<enterStrongPasswordHere>' ;

Upvotes: 0

Robabeh Ghasemi
Robabeh Ghasemi

Reputation: 470

According to: https://msdn.microsoft.com/en-us/library/bb326280.aspx

Go to --> Remot setting

Go to "Remote" tab

in "Remote Assistance", Tick "Allow Remote Assistance connection to this computer", Click the "Advance" button and tick the "Allow..." and in the "Invitation" set the "30 days"

Then in the "Remote Desktop" part

Just tick "Allow remote connection to this computer"

Upvotes: 0

Nikhil G
Nikhil G

Reputation: 1594

I have not used the script style, but login through GUI I encountered the same error code. I had entered wrong user name and this is why I was getting the Sql Server, Error: 233.

In order to resolve this, you should input the following information:

Server Name: MachineName\SQLEXPRESS
Authentication: SqlServer Authentication
User Name: Assigned user-name or simply sa
Password: xyzpqr

NOTE: Here I have wrote above data for demo purpose only, actual data is your machine & software's properties.

Upvotes: 0

muhammad liaquat
muhammad liaquat

Reputation: 1

I tried most of the solution but was not able to solve it until I found this URL which says to do the following:

Open SQL Server Management Studio and run the these queries:

sp_configure 'show advanced options', 1;
go
reconfigure
go
sp_configure 'user connections', 0
go
reconfigure
go

The reason why we got this error is that the user connections was reset to 1, so only one user was able to connect with the SQL server. just a simple query worked for. I hope this will work for others as well.

Upvotes: 0

Maloy Bain
Maloy Bain

Reputation: 1

I got a way to go around the problem.

  • Open one instance and login using the windows authentication
  • allow sql and windows auth both by right cliking on the db server.
  • Open second instance and login using sql authentication.

bingo the sql authenticated instance open .. :)

Actually in this way we cheat the sql authenticated instance as it tries to find an already running instance.. worked fr me.. good luck

Upvotes: 0

patrickwlarsen
patrickwlarsen

Reputation: 168

I had the same issue when i first setup SQL Server 2014 on my local machine. In my case the solution was to set a correct defualt database.

Upvotes: 1

BKH
BKH

Reputation: 31

I had a similar issue: 1. log in as the master user or windows authenticated user. 2. right click on the database --> properties --> security --> 3. change Windows Authentication mode to "SQL server and windows authentication mode" by clicking on the radio button. (if it is not) 4. restart the server

Upvotes: 1

Atheeth
Atheeth

Reputation: 1

This is might not be a connection issue . Check your default database and if that is online . More commonly this issues seen when the default database will be offline or not exists . If your default database other than master ,better check this option.

Upvotes: 0

CSharp
CSharp

Reputation: 1583

I was facing the same error.
I've resolved the error by following below mentioned steps:

  1. Disable named pipes and restart sql services.
  2. After restart sql server I enabled names pipes and did a sql server restart again (Link for Step 1 and 2)
  3. Connect to SQL server via studio.
  4. Right click on SQL instance --> Properties --> Connections --> "Set the Maximum number of 5. concurrent connections to '0' ".
  5. Save the change.
  6. Restart the SQL server if possible. (Link for step 3 to 6)

I hope this will help someone

Upvotes: 0

Manoj Shrivastava
Manoj Shrivastava

Reputation: 1

Login with Administrator in SQL Server Go to Securities >> Logins >> select your user name and go to properties

From Status >> uncheck user account lock check box Change password for the user Restart the sql server and login with your username.

Upvotes: 0

Beevik
Beevik

Reputation: 570

It's also possible that you're trying to use SQL Server Authentication without having enabled it. To fix this, right-click Properties on your server instance in SQL Server Management Studio, and update the security settings to include "SQL Server and Windows Authentication mode".

Upvotes: 12

Andomar
Andomar

Reputation: 238086

Looks like you're trying to connect using named pipes, but SQL Server is not listening on that protocol. See MSDN.

The two fixes MSDN suggests are:

  • Connect using TCP/IP, or use the SQL Server Configuration Manager to enable remote connections using named pipes.
  • Using SQL Server Configuration Manager on the client computer, move TCP before named pipes in the protocol order list.

Upvotes: 3

Related Questions