Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On a SQL Server 2005 clustered - I set the maximum concurrent connections to 1 and now the SQL server cluster cannot start. I guess it needs at least two connections (one for each node).

Can I recover from this by restoring the master database?

share|improve this question

You might not have to restore the DB, try these instructions first:

  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type the following command, and then press ENTER. sqlcmd.exe -E -S servername
  3. When you successfully connect to the instance of SQL Server 2005, execute the following Transact-SQL statements at the SQL Server prompt. sp_configure 'user connections', Go Reconfigure Go

  4. Restart the SQL Server service for the change to take effect.

Instructions found here

share|improve this answer
The server is on a cluster, and the cluster is not starting because there aren't enough connections. Any ideas? – AAguilar Mar 7 '13 at 13:21
Oh sorry about that. Maybe you could try starting the server with a minimal configuration? Like this: – crazylpfan Mar 8 '13 at 23:59

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.