January 5, 2006 at 10:05 am
After several major power outages and power spikes at our office last night, we're haveing a problem logging into our production SQL Server. The UPS system was fried, but the net admins finally got the server to boot and connect to the RAID card. The problem we have is that the server refuses our attempts to connect via Enterprise Manager, Query Analyzer or OSQL. We're getting this message from the event logs:
Error: 17809, Severity: 20, State: 1
Could not connect. The maximum number of '2' configured user connections are already connected. The system administrator can change the maximum to a higher value using sp_configure.
The trick here is how I can change the max user connections without logging into sel server? Any help here would be greatly appreciated.
January 5, 2006 at 10:09 am
What do you use the SQL Server for? Applications? Stop the SQL Server services, stop any applications that connect to the databases. Restart the MSSQLServer service (not the SQLServerAgent service). Try to connect. If you can connect, make the changes to the connection amount. Then start the SQLServerAgent service and the applications.
-SQLBill
January 5, 2006 at 10:29 am
We were so close... we had done all of your suggestions with the exception of SQLServerAgent service. Once I shut that one off I was able to login and reconfigure.
Thanks for you quick response!
-Russell
January 5, 2006 at 11:53 am
Glad to help.
-SQLBill
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply