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:

MSSQL error

I am using Microsoft SQL Server 2012 and the user has full permissions.

try pinal dave solutions http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/ — GeoVIP, Dec 03 '14 at 10:47
This worked for me when I reconnected from server authentication to windows authentication. — ganji raajkumar, Dec 28 '16 at 13:22
What worked for me (sql express 2016) ... Removing mixed authentication leaving just windows auth, restarting service, switch it back to mixed auth, restart service. until i did this nothing fixed the No process error — Rostol, Mar 07 '17 at 01:42
For what its worth, check the connection string in your config file. For me someone had modified one of the server names and checked it in. My code was trying to hit a database that didn't exist on my server. — camainc, Dec 11 '18 at 21:31
@camainc: I believe Sql Server does not store its connection strings — MSIS, Sep 28 '22 at 20:22

Iter Ator · Accepted Answer · 2021-12-23T12:34:03.027

220

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 does not warn you, 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.

Here are the directions by Microsoft: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode?view=sql-server-ver15

edited Dec 23 '21 at 12:34

answered Dec 03 '14 at 12:14

Iter Ator

8,226
20
73
164

5

The option was correctly checked, so I checked 'Windows Authentication', I restart the service then I check 'Windows Authentication + SQL Authentication' to fix that problem. So happy! – Groco Sep 04 '17 at 19:39
5

To clarify @Groco's comment: Log in using `Windows Authentication` >> Right-Click your server >> `Properties` >> `Security` (Under `Select a page`) >> Under `Server Authentication` select `SQL Server and Windows Authentication mode`. Close SQL Server Management Studio, restart the SQL Server service, and try logging in again. – Minh Tran Sep 13 '18 at 21:48
1

The issue I had was that `Server Authentication` was set to `Windows Authentication mode`. And regardless of the correct password input, I was always greeted with `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.)`. Throughout the error, I was able to log in using `Windows Authentication` – Minh Tran Sep 13 '18 at 21:53
thank you so much. reatart the Sql Service fixed my problem. – user1282609 Jul 05 '20 at 01:57
1

I tried logging in using "sa", and got the same error. – RonJohn Nov 16 '20 at 13:51
1

For those like me who saw this answer and chased it down also see the answer below "Another reason for this error could be incorrect or non-existent database name.". I chased the Auth Settings and network settings only to find it was the age old "underscore versus dash" issue on the DB name :-{ – Cueball 6118 Jun 02 '21 at 02:23
This also fixed the same issue I was having in SQL Server 2019 – nallan Jul 22 '21 at 13:45

score 65 · Answer 2 · edited Mar 20 '19 at 22:11

65

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.

enable sa admin

If this didn't work, you may need to reinstall SQL Server

edited Mar 20 '19 at 22:11

Iter Ator

8,226
20
73
164

answered Nov 11 '15 at 20:59

nzchris

659
1
5
3

After doing this, restart SQL Server. Then try to log in. – Webucator Sep 09 '20 at 20:50

score 36 · Answer 3 · answered Nov 17 '16 at 04:57

36

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

answered Nov 17 '16 at 04:57

No Name

719
6
14

3

This solved my issue after trying all the other fixes. – mini998 Dec 21 '17 at 12:20
1

Uh, shouldn't this come with a big warning label that restarting the sql server service just because you can't connect will break other things that have sucessfully connected? – undrline - Reinstate Monica Mar 16 '20 at 15:51
This worked great for me. I can see how easy it is for people to neglect considering this solution. – TechnicalTim May 07 '20 at 18:11

Joe Walters · Answer 4 · 2018-12-14T01:54:09.843

35

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.

edited Dec 14 '18 at 01:54

answered Dec 14 '18 at 01:21

Joe Walters

641
6
7

2

I tried all comments but it didn't work. Your solution worked perfect for me. Thank you very much. – Zhong Ri Feb 06 '19 at 18:10
this was the last thing that I tried after all the other stuff of checking tcp is enabled, adding mixed mode authentication and restarting sql browser service and it worked. thanks – Myke Black Sep 17 '19 at 08:14

Mohammad Dehghan · Answer 5 · 2020-02-17T05:26:15.543

18

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.

edited Feb 17 '20 at 05:26

answered May 10 '15 at 07:53

Mohammad Dehghan

17,853
3
55
72

what happened to configuration manager in express 2016? I don't see it available? Oh I have to run SQLServerManager13.msc now – Kirsten Jan 20 '18 at 07:16
1

When I changed to 127.0.0.1 I got error message Message=A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Source=Core .Net SqlClient Data Provider – Kirsten Jan 20 '18 at 07:26
1

@kirsteng Check your installed SQL Server instances. Did you install a default instance (MSSQLSERVER)? – Mohammad Dehghan Jan 20 '18 at 10:16
The SQL Server Authentication in mixed mode did it for me. Guys if you do a fresh installation of SQL Server Express, when you want to add a user for your progamming needs, you need to change it to mixed mode otherwise only windows authentication will be avilable. – Eduardo Sep 02 '18 at 12:24
This (sort of) worked. Once I changed the localdb nonsense to 127.0.0.1 it got through. – Eric Nov 27 '18 at 19:59
It was the database name for me. There was nothing else for me to do except fix the name. I think that should be emphasized here. I will attempt to fix that. – Sam Hobbs Feb 16 '20 at 20:42
I was doing a DevExpress XAF Blazor tutorial. That documentation says that the framework will create the Db the first time it runs. Ha. Once I created both the primary Db and the "EasyTest" Db the app ran. Thanks MD. – pdschuller Dec 20 '20 at 02:32

score 9 · Answer 6 · answered Mar 22 '16 at 07:04

9

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

answered Mar 22 '16 at 07:04

Muhammad Bilal

1,008
13
14

score 8 · Answer 7 · answered May 01 '18 at 22:46

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.

score 5 · Answer 8 · answered Oct 18 '17 at 18:53

5

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

answered Oct 18 '17 at 18:53

Groco

1,301
15
19

score 5 · Answer 9 · answered May 16 '18 at 14:12

5

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.

answered May 16 '18 at 14:12

Bence Végert

728
10
12

you save my day!! – learner Apr 08 '20 at 06:56

score 5 · Answer 10 · answered Oct 30 '19 at 15:31

5

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.

answered Oct 30 '19 at 15:31

Anssssss

3,087
31
40

score 3 · Answer 11 · answered Oct 03 '19 at 15:30

3

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.

answered Oct 03 '19 at 15:30

Stefan

59
5

score 2 · Answer 12 · answered Nov 27 '16 at 10:52

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.

CyberDude · Answer 13 · 2020-09-06T18:31:44.713

2

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.

edited Sep 06 '20 at 18:31

answered Sep 06 '20 at 16:18

CyberDude

8,541
5
29
47

Same exact thing! I had just created the login just a few minutes before. – Aliza Berger Sep 19 '22 at 18:44

score 2 · Answer 14 · answered Jul 06 '22 at 03:14

This might help others. After writing my db routines at home, all working fine. Brought it to work and got this error as well. Might assert same error, different reason. I mistyped the database name when fixing up my code. Ooohh! More coffee ;) Looking back now, kind of makes sense in my case the login/user was good (an admin account) but with a bad database name, there was nothing on the end of the pipe. Why not say "Database does not exists...? And be clear.

score 1 · Answer 15 · answered Jun 18 '18 at 11:47

1

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

answered Jun 18 '18 at 11:47

elkoo

704
9
23

score 1 · Answer 16 · edited Oct 24 '18 at 08:28

1

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

edited Oct 24 '18 at 08:28

Eric Aya

69,473
35
181
253

answered Oct 24 '18 at 01:04

cschaefer

259
4
8

You can also usually restart the SQL service for your specific database by locating it in `services.msc` – Zimano Nov 01 '19 at 11:51

score 1 · Answer 17 · answered Jan 19 '21 at 09:56

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-> Login -> Open the user -> Go to user mapping tab -> Enable the database and grant appropriate role.

score 1 · Answer 18 · answered Feb 09 '21 at 04:23

1

In my case: Assign a sysadmin role to the user.

Login as windows authenticated user
Go to: Security->Login->Right click user->Assign server role as sysadmin

answered Feb 09 '21 at 04:23

Ricardo D. Ferrancullo III

423
9
12

Talk about a "sledgehammer approach" - this dangerous and should not even be considered as a solution. – Rab Mar 17 '21 at 15:17

score 1 · Answer 19 · answered Apr 06 '21 at 08:41

In my case, login works fine remotely, via VPN. But connecting from the server where sql server was installed, it failed.

Turns out, the instance name is not the default eg. SQLEXPRESS. Hence, it needs to be explictly specified when connecting.

Server name: .<instance_name> eg. ".\I01"

I don't have to do this if I'm connecting remotely, just <server_hostname>,<port_number>

score 1 · Answer 20 · answered Mar 12 '23 at 19:57

1

In my case the Database was not created yet (not existent), but the error in EF Core 7.0.3 was

"No process is on the other end of the pipe"

answered Mar 12 '23 at 19:57

Omu

69,856
92
277
407

score 0 · Answer 21 · answered Aug 19 '23 at 19:31

0

Right-Click your server name >> Go to Properties >> to Security >>Under Server Authentication >> select SQL Server and Windows Authentication mode >>restart the SQL Server service, and login.

answered Aug 19 '23 at 19:31

Korir Cornelius

11
1
2

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

21 Answers21

Linked