SQL Server 2008 Error 233

Question

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

CREATE LOGIN [xyz] WITH PASSWORD=\'xyz\',
            DEFAULT_DATABASE=[master], DEFAULT_LA         


        

Answer 1

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.

Answer 2

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

Answer 3

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>' ;

Answer 4

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

Answer 5

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.

Answer 6

"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.