No Process Is on the Other End of the Pipe

Question

I receive this error when I try to connect to SQL Server 2005. I have enabled TCP/IP, Named Pipes, and restarted the server but that is not working.

score 9 · Answer 1 · answered Dec 23 '15 at 00:51

For me the issue was that the SQL server was in Windows Authentication mode only, even though I set it to mixed during the install.

In the object explorer, right click on the server, properties and then the Security page and set Server authentication to SQL Server and Windows Authentication mode.

score 4 · Answer 2 · answered Aug 26 '10 at 07:09

FYI, I've just had the same error.

I switched to Windows authentication, disconnected, then tried to login again with SQL authentication. This time I was told my password had expired. I changed the password and it all worked again.

score 4 · Accepted Answer · edited Sep 24 '18 at 15:50

4

I tried the troubleshooting steps in both microsoft tech articles, and oddly no luck.

I managed to fix the solution by changing my authentication from SQL Server Auth to Windows Auth. Though I am not sure the technical reason why this works?

edited Sep 24 '18 at 15:50

Boiethios

38,438
19
134
183

answered Jan 17 '09 at 20:23

Sheehan Alam

60,111
124
355
556

i had the same error since the user querying the db did not had permissions so i guess its a permissions issue – bresleveloper Aug 19 '13 at 06:22

score 3 · Answer 4 · answered Nov 28 '12 at 10:21

3

It may help to make sure the database specified in the initial catalog exists.

answered Nov 28 '12 at 10:21

mafu

31,798
42
154
247

score 2 · Answer 5 · answered Aug 21 '13 at 21:53

2

I encountered this problem when the password for the login that I was attempting to connect with had expired.

answered Aug 21 '13 at 21:53

arcain

14,920
6
55
75

score 2 · Answer 6 · answered Mar 02 '11 at 23:45

2

I got this error when I (deliberately) reduced the configuration of maximum SQL Server memory to 16Mb and restarted.

So it might be a memory issue.

answered Mar 02 '11 at 23:45

Neil Miller

21
1

score 1 · Answer 7 · answered May 13 '19 at 19:44

1

One another reason for this error message could be the case when you've deleted the database your application uses, and you didn't run the following commands from your visual studio:

Add-Migration MigrationNameHere
Update-Database

answered May 13 '19 at 19:44

Igor Micev

1,514
1
17
23

score 0 · Answer 8 · answered Dec 11 '15 at 10:18

1st check the Window's Event Log for the following error:

Could not connect because the maximum number of ’1′ user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection has been closed.

To solve the problem do the following:

Open Microsoft SQL Server Management Studio
Open a new query

Type the under given code and press the execute button

sp_configure ‘show advanced options’, 1;
GO
reconfigure
GO
sp_configure ‘user connections’, 0;
GO
reconfigure
GO

Source: http://www.windowstechupdates.com/microsoft-sql-server-error-233-no-process-is-on-the-other-end-of-the-pipe/

score 0 · Answer 9 · answered May 23 '17 at 13:46

0

In my case make sure that your connection string has ;password=

answered May 23 '17 at 13:46

zapoo

1,548
3
17
32

score 0 · Answer 10 · answered Jan 16 '09 at 22:56

0

I assume you have seen this: http://technet.microsoft.com/en-us/library/ms175496.aspx

how about this? http://blogs.msdn.com/sql_protocols/archive/2006/07/26/678596.aspx

answered Jan 16 '09 at 22:56

Sam

7,543
7
48
62

score 0 · Answer 11 · answered Feb 13 '20 at 19:19

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)

This error will occur when the login does not have an active "Default Database" assigned. In my case this occurred after taking a DB Offline. The previous DBA had assigned a non-system DB as the Default DB for a login. After that DB was taken offline, the login failed threw this error 233.

To Check & Fix this... Login to the SQL Server Instance via SSMS using a different login. Go to... >> Security >> Logins >> {Login Name} >> General

Check the "Default Database" is set to an active DB (I reverted back to 'master').

Logout & then try logging in again using the login that was just updated.

score 0 · Answer 12 · answered May 28 '20 at 19:25

0

in my case :

it was blocked by Symantec AV and firewall

just for trial I have to disable symantec n firewall

i think i'll have further checking

answered May 28 '20 at 19:25

rtfmpliz

159
1
6

score 0 · Answer 13 · answered Jul 30 '22 at 12:46

If you have created the migrations, you could execute them in the Startup.cs as follows.

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
 {
      using (var serviceScope = app.ApplicationServices.GetService<IServiceScopeFactory>().CreateScope())
      {
            var context = serviceScope.ServiceProvider.GetRequiredService<ApplicationDbContext>();
            context.Database.Migrate();
      }
      
      ...

This will create the database and the tables using your added migrations.

If you're not using Entity Framework Migrations, and instead just need your DbContext model created exactly as it is in your context class at first run, then you can use:

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
 {
      using (var serviceScope = app.ApplicationServices.GetService<IServiceScopeFactory>().CreateScope())
      {
            var context = serviceScope.ServiceProvider.GetRequiredService<ApplicationDbContext>();
            context.Database.EnsureCreated();
      }
      
      ...

No Process Is on the Other End of the Pipe

13 Answers13

Linked