question

manishpandey999 avatar image
manishpandey999 asked

SQL memory error

The client was unable to establish connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server, the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider : Shared Memory Provider: Error :0 – No process is on the other end of the pipe.) (Microsoft SQL Server, Error:233)

sql server
1 comment
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

manishpandey999 avatar image manishpandey999 commented ·

Hello,

It particular working in all users but except in one users is not working, So any one has solution of problems please help us

0 Likes 0 ·

1 Answer

·
WRBI avatar image
WRBI answered

The 'named pipes' protocol maybe disabled. Try enabling them in the SQL Server network configuration protocols.

Run the following to find out the max number of connections your SQL instance can take:

SELECT @@MAX_CONNECTIONS

If needed you can then do something like:

USE AdventureWorks2012 ;  
GO  
EXEC sp_configure 'showadvanced options', 1;  
GO  
RECONFIGURE ;  
GO  
EXEC sp_configure 'user connections', 325 ; -- Insert your number! 
GO  
RECONFIGURE;  
GO

References

MSDN - Max Connections

MSDN - Configure the user connections Server Configuration Option

Hope this helps you.

Dave

10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.