Browse by Tags

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

Published 26 September 7 5:27 AM | SSQA.net

The above error is obvious when you have setup the SQL Server instance to accept only 1 connection. The default setting for number of user connections is '0' which accepts unlimited connections. With similar settings one of my friend have had...

Filed under: sql server, anti-virus, connections, service, recovery, tcp, restart, maximum, sp_configure

SQL Server Database Mirroring error with TCP port numbers, firewall involvement

Published 13 September 7 10:35 AM | SSQA.net

Lately we have been getting complaints that database mirroring setup on few of our client's site were failing with TCP related errors. For more information these sites are involved within the firewall setup and active directory too. Initial workaround...

Filed under: sql server, database mirroring, error log, tcp, network, firewall, wan, failed, endpoint, setup

An error has occured while establishing a connection to the server. When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider:Named Pipes ....)

Published 26 July 7 7:49 AM | SSQA.net

Error: An error has occured while establishing a connection to the server. When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider:Named Pipes Provider...

Filed under: sql server, performance, management, security, ssms, error, access, sql express, tcp, named pipes, remote