Sometimes making a change in something for which the impact is not known, could cause a heavy loss. A similar situation happened when one of my clients called me and told that he is in big trouble and losing a lot of money every minute. Without wasting any moment, I asked what is the issue, then he told that he changed some setting in SQL Server, restarted SQL and now no one is able to connect. The application is completely down! Let us see how we can fix the error: Could not connect because the maximum number of ‘1’ user connections has already been reached.

• Sql Server 2014 Error 233
• Sql Server Error 233 Shared Memory Providers
• Microsoft Sql Server Error 53

We quickly started desktop sharing and we noticed the below error while connecting from SSMS.

It is unlikely that it is a firewall issue, since connection was established. Even less so when it says 'shared memory provider' - this indicates that you are connecting to an SQL Server instance on your local machine. With no knowledge of your envrionment it is difficult to understand what may be going.

TITLE: Connect to Database Engine
——————————
Cannot connect to DBSERVER.
——————————
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
——————————
No process is on the other end of the pipe
——————————
BUTTONS:
OK
——————————

This was a very generic error, so I asked to check the Application Event Log.

Log Name: Application
Source: MSSQLSERVER
Event ID: 17809
Task Category: Logon
Level: Error
Keywords: Classic
User: N/A
Computer: DBSERVER.SomeDomain.in
Description:
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.

As per above message the number of user connections was set to 1 and all we need to do is change that value to 0 as shown below

Sounds simple, but the situation here was that someone was grabbing connection so quickly that we were not able to connect. I recalled an earlier blog, where I wrote about single user mode.

So, we followed the blog, start SQL with /mSQLCMD parameter, connected to the SQL server instance in single user mode via SQLCMD and then executed following command.

Then we restarted SQL Server and after which we were able to connect successfully using SSMS and application also started working.

Reference: Pinal Dave (https://blog.sqlauthority.com)

I've got this error:

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.

Sarath Avanavu

Sql Server 2014 Error 233

Iter AtorIter Ator

12 Answers

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:

1. Right click on the server name and select properties;
2. Select security tab;
3. Enable the SQL Server and Windows Authentication mode;
4. Restart the SQL Server service.

You can now connect with your login/password.

French BoiethiosIter AtorIter Ator

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

Iter Ator

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

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

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

Mohammad Dehghan

Sql Server Error 233 Shared Memory Providers

Mohammad Dehghan

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.

1. Open regedit
2. Go to the SQL instance key (may vary depending on your instance name):ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL14.SQLEXPRESSMSSQLServer
3. Set LoginMode to 2

4. Restart SQL service and SQL Server Management Studio and try again.

I face this issue for the second time and all previous answers failed, fortunately the following request do the job:

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.

Microsoft Sql Server Error 53

I have the same proplem'A connection was successfully established with the server, but then an error occurredduring the login process. (provider: Shared Memory Provider, error: 0 - No process ison the other end of the pipe.)'

My connection is:

server=POS06SQLEXPRESS; AttachDbFilename=C:..Datas.mdf;Initial Catalog= Datas; User ID= sa; Pwd=12345; Connect Timeout=10;

But My SQL is POS06MSQL2014

Change the connection string to

server=POS06MSQL2014 ; AttachDbFilename=C:..Datas.mdf;Initial Catalog= Datas; User ID= sa; Pwd=12345; Connect Timeout=10;

it worked.

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.

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

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

ayaio

protected by Community♦Jan 31 '17 at 4:43

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?

This program has all the professional capabilities to delete a program provided in another application. This is a completely offline installer for IObit Uninstaller. Iobit uninstaller 8.4.0.7 key. IObit Uninstaller Pro 8The PRO IObit Uninstaller 7 activation key is the ideal application with several features, such as removing built-in applications for Windows 8, 8.1 and Windows 10. For the strength of the structure, IObit Uninstaller always creates a restore point of the structure before each uninstallation and provides superior management of the restore point of the structure. This program gives you another incredible opportunity for your browser to detect the extension or malicious plug-ins and optimize your system by cleaning and speeding up the online adware experience.

Not the answer you're looking for? Browse other questions tagged sql-serversql-server-2012 or ask your own question.