A connection was successfully established with the server but then an error occurred during the login process Error Number 233

Question

I am having error while connecting to SQL Server     Details in Stack Trace are                                        Cannot connect to ServerName                                        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     Net SqlClient Data Provider   ------------------------------ For help  click  http   go microsoft com fwlink ProdName Microsoft SQL Server amp EvtSrc MSSQLServer amp EvtID 233 amp LinkId 20476  ------------------------------ Server Name  ServerName Error Number  233 Severity  20 State  0   ------------------------------ Program Location      at System Data SqlClient SqlInternalConnection OnError SqlException exception  Boolean breakConnection     at System Data SqlClient TdsParser ThrowExceptionAndWarning TdsParserStateObject stateObj     at System Data SqlClient TdsParserStateObject ReadSniError TdsParserStateObject stateObj  UInt32 error     at System Data SqlClient TdsParserStateObject ReadSni DbAsyncResult asyncResult  TdsParserStateObject stateObj     at System Data SqlClient TdsParserStateObject ReadNetworkPacket      at System Data SqlClient TdsParserStateObject ReadBuffer      at System Data SqlClient TdsParserStateObject ReadByte      at System Data SqlClient TdsParser Run RunBehavior runBehavior  SqlCommand cmdHandler  SqlDataReader dataStream  BulkCopySimpleResultSet bulkCopyHandler  TdsParserStateObject stateObj     at System Data SqlClient SqlInternalConnectionTds CompleteLogin Boolean enlistOK     at System Data SqlClient SqlInternalConnectionTds AttemptOneLogin ServerInfo serverInfo  String newPassword  Boolean ignoreSniOpenTimeout  Int64 timerExpire  SqlConnection owningObject  Boolean withFailover     at System Data SqlClient SqlInternalConnectionTds LoginNoFailover String host  String newPassword  Boolean redirectedUserInstance  SqlConnection owningObject  SqlConnectionString connectionOptions  Int64 timerStart     at System Data SqlClient SqlInternalConnectionTds OpenLoginEnlist SqlConnection owningObject  SqlConnectionString connectionOptions  String newPassword  Boolean redirectedUserInstance     at System Data SqlClient SqlInternalConnectionTds  ctor DbConnectionPoolIdentity identity  SqlConnectionString connectionOptions  Object providerInfo  String newPassword  SqlConnection owningObject  Boolean redirectedUserInstance     at System Data SqlClient SqlConnectionFactory CreateConnection DbConnectionOptions options  Object poolGroupProviderInfo  DbConnectionPool pool  DbConnection owningConnection     at System Data ProviderBase DbConnectionFactory CreateNonPooledConnection DbConnection owningConnection  DbConnectionPoolGroup poolGroup     at System Data ProviderBase DbConnectionFactory GetConnection DbConnection owningConnection     at System Data ProviderBase DbConnectionClosed OpenConnection DbConnection outerConnection  DbConnectionFactory connectionFactory     at System Data SqlClient SqlConnection Open      at Microsoft SqlServer Management SqlStudio Explorer ObjectExplorerService ValidateConnection UIConnectionInfo ci  IServerType server     at Microsoft SqlServer Management UI ConnectionDlg Connector ConnectionThreadUser     NOTE I have tried    closing  reopening Sql server Management Studio  closing   reopen VS  amp  rebuild Solution killed worker process accessing database  login credentials are correct  able to ping server to make sure its not down

User · Answer

For me  adding Trusted Connection True to the connection string helped

User · Answer

When you starting application  Run as administrator  This way I avoided this error

User · Answer

I had to do 2 things  Do what Joseph Wu said and change the authentication to be SQL and Windows  But I also had to go to Server Properties  gt  Advanced and change  quot Enable Contained Databases quot  to True

User · Answer

the following points work for me  Try    start SSMS as administrator make sure SQL services are running  Change startup type to  Automatic       In SSMS  in service instance property table  enable below

User · Answer

From here      Root Cause  Maximum connection has been exceeded on your SQL Server Instance       How to fix it             F8 or Object Explorer   Right click on Instance --  Click Properties      Select  Connections  on  Select a page  area at left   Chenge the value to 0  Zero  for  Maximum number of concurrent connections 0   Unlimited     Restart the SQL Server Instance once       Apart from that also ensure that below are enabled    Shared Memory protocol is enabled Named Pipes protocol is enabled TCP IP is enabled

User · Answer

To add on top of  Pranav Singh and  Rahul Tripathi answer  After doing all the mentioned by those 2 users  my  net app still wasnt connecting to the database  My solution was  Open Sql Server Configuration Manager  go to Network configuration of SQL SERVER  click on protocols  right click on TCP IP and select enabled  I also right clicked on it opened properties  Ip directions  and scrolled to the bottom  IPAII   and there in TCP Port  I did setup a port  1433 is supposed to be default

User · Answer

My problem resolved by this what changes i have done in  net core Do this changes in Appsetting json Server     Database     Persist Security Info False User ID      Password     MultipleActiveResultSets False Encrypt False TrustServerCertificate False Connection Timeout 30  and Do following changes in Package console manager Scaffold-DbContext  quot Server     Database     Persist Security Info False User ID      Password     MultipleActiveResultSets False Encrypt False TrustServerCertificate False Connection Timeout 30  quot  Microsoft EntityFrameworkCore SqlServer -OutputDir Models -Context DatabaseContext -f  Happy coding

User · Answer

Turn out to be some SQL service was stopped somehow on server  Restarting SQL Server service manually was the solution   I know this is foolish but worked anyway  Thanks   PareshJ for the useful comment

User · Answer

For SQL2008     open Management Studio Rt click on instance  go to properties select Security Under Server Authentication  check SQL Server and Windows Authentication Mode hit OK   Restart the server using configuration manager

User · Answer

This is what helped me  src

User · Answer

Sometimes specifying the database  instead of default  solves this error

User · Answer

I ve gotten this error because the user trying to login was lacking permissions   I don t recommend doing this  but I fixed it by granting the user db owner globally  It was a local instance  so not a huge security concern

User · Answer

I got that error message in code line containing SqlConnection Open   running my  NET code as x64 application  Running as x86 causing no errors   Solution was to deactivate the Force protocol encryption option for TCP IP in   windir  System32 cliconfg exe  Force protocol encryption

User · Answer

SQL 2016 solution workaround here  could also work in earlier versions    This may not work or be appropriate in every situation  but I resolved the error by granting my database user read write schema ownership as follows in SSMS   Database   Security   Users   User   Properties   Owned Schemas   check db datareader and db datawriter

User · Answer

You can also get this error  somewhat unhelpfully  if the database name specified in the connection string doesn t exist  Check your Db Name carefully

User · Answer

Here is the solution I found  Go to SQL Server Management  Disable Memory Shared  TCP IP and Pipes named  Restart the server and try again

User · Answer

In my case I had the following by mistake in my connection string  Encrypt True  Changing to Encrypt False  Solved the problem  quot Server     Initial Catalog     Persist Security Info False User  ID     Password     MultipleActiveResultSets False Encrypt False TrustServerCertificate False Connection Timeout 30  quot

[sql-server] A connection was successfully established with the server, but then an error occurred during the login process. (Error Number: 233)

Examples related to sql-server

Examples related to sql-server-2008-r2