No process is on the other end of the pipe SQL Server 2012

Question

I ve got this error   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    I know  there are similar questions on this site  and the answer is  to enable TCP IP and pipes  But I enabled both  and still doesn t work     I am using Microsoft SQL Server 2012 and the user has full permissions

User · Answer

I face this issue for the second time and all previous answers failed  fortunately the following request do the job   Alter login  user  with CHECK POLICY   OFF go  Alter login  user  with CHECK POLICY   ON go

User · Answer

For me the password expired for my login user  and i got the same exception  Then i login with Windows Authentication mode and change the password for the associated user  and it solved my problem

User · Answer

In my case the database was restored and it already had the user used for the connection  I had to drop the user in the database and recreate the user-mapping for the login   Drop the user DROP USER  MyUser     It might fail if the user owns any schemas  Those has to assigned to dbo before dropping the user  Get the schemas owned by the user using first query below and then alter the owner of those schemas using second query  HangFire is the schema obtained from previous query   select   from information schema schemata where schema owner    MyUser  ALTER AUTHORIZATION ON SCHEMA   HangFire  TO  dbo         Update user mapping for the user  In management studio go to Security- gt  Login - gt  Open the user - gt  Go to user mapping tab - gt  Enable the database and grant appropriate role

User · Answer

I have the same proplem  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     My connection is   server POS06 SQLEXPRESS    AttachDbFilename C     Datas mdf Initial Catalog   Datas  User ID  sa  Pwd 12345  Connect Timeout 10    But My SQL is POS06 MSQL2014   Change the connection string to   server POS06 MSQL2014     AttachDbFilename C     Datas mdf Initial Catalog   Datas  User ID  sa  Pwd 12345  Connect Timeout 10    it worked

User · Answer

If you are trying to login with SQL credentials  you can also try changing the LoginMode for SQL Server in the registry to allow both SQL Server and Windows Authentication    Open regedit Go to the SQL instance key  may vary depending on your instance name   Computer HKEY LOCAL MACHINE SOFTWARE Microsoft Microsoft SQL Server MSSQL14 SQLEXPRESS MSSQLServer  Set LoginMode to 2      Restart SQL service and SQL Server Management Studio and try again

User · Answer

To solve this  connect to SQL Management Studio using Windows Authentication  then right-click on server node Properties- Security and enable SQL Server and Windows Authentication mode  If you re using  sa  make sure the account is enabled  To do this open  sa  under Logins and view Status     If this didn t work  you may need to reinstall SQL Server

User · Answer

Please check this also  Also check in configuration TCP IP Names PipeLine and shared memory enabled

User · Answer

Another reason for this error could be incorrect or non-existent database name   Forcing the TCP IP connection  by providing 127 0 0 1 instead of localhost or    can reveal the real reason for the error  In my case  the database name specified in connection string was incorrect   So  here is the checklist    Make sure Named Pipe is enabled in configuration manager  don t forget to restart the server   Make sure the database you are connecting to exists  Make sure SQL Server Authentication  or Mixed Mode  is enabled

User · Answer

make sure that you have specified user in Security-  Logins  if no - add it and try again

User · Answer

The server was set to Windows Authentication only by default  There isn t any notification  that the origin of the errors is that  so it s hard to figure it out  The SQL Management studio dont alert  even if you create a user with SQL Authentication only   So the answer is  Switch from Windows to SQL Authentication    Right click on the server name and select properties  Select security tab  Enable the SQL Server and Windows Authentication mode  Restart the SQL Server service    You can now connect with your login password

User · Answer

Follow the other answer  and if it s still not working  restart your computer to effectively restart the SQL Server service on Windows

User · Answer

Yup  this error might as well be  something failed  good luck figuring out what  - In my case it was a wrong username  SQL Server 2019 RC1

User · Answer

Also you can try to go to services and restart your Sql server instance

User · Answer

In my case  Assign a sysadmin role to the user   Login as windows authenticated user Go to  Security- gt Login- gt Right click user- gt Assign server role as sysadmin

User · Answer

So  I had this recently also  for integrated security  It turns out that my issue was actually fairly simple to fix but mainly because I had forgotten to add  Trusted Connection True  to my connection string    I know that may seem fairly obvious but it had me going for 20 minutes or so until I realised that I had copied my connection string format from connectionstrings com and that portion of the connection string was missing   Simple and I feel a bit daft  but it was the answer for me

User · Answer

Always try to log in using those credentials with SQL Management Studio  This might reveal some more details that you don t get at runtime in your code  I had checked the SQL   Windows authentication  restarted the server but still no luck  After trying to log in using SQL Management  I got this prompt   Somehow the password had expired although the login was created just minutes before  Anyway  new password set  connection string updated and all s fine

User · Answer

Had this error too  the cause was simple  but not obvious  incorrect password  Not sure why I didn t get just  Login failed  from freshly installed SQL 2016 server

[sql-server] No process is on the other end of the pipe (SQL Server 2012)

Examples related to sql-server

Examples related to sql-server-2012