February 6, 2014 at 2:23 pm
Help !
I have restarted sqlsrv in single user mode by using the -m; at the beinging of the startup parameters.
I have stopped all the services (sql agent, sql server integration services, sql browser)
SQL Server starts up with out windows admin domain account.
In Managment studio in object explorer i can see that i am connected but i want to run a query to do some database maintenance but it wont le me connect to run the query - it keeps saying it is in single user mode and only one connection is allowed.
Please help !
February 6, 2014 at 2:35 pm
while using SSMS, IIRC Object Explorer is treated as a separate connection and query pane as a separate connection. Disconnect from Object Explorer and try running your query and see how it goes.
PS SQLCMD is safe bet while sql server is running in Single User mode.
February 6, 2014 at 2:38 pm
When you start an instance of SQL Server in single-user mode, SQL Server Management Studio can connect to SQL Server. Object Explorer in Management Studio might fail because it requires more than one connection for some operations. To manage SQL Server in single-user mode, execute Transact-SQL statements by connecting only through the Query Editor in Management Studio, or use the sqlcmd utility.
FYI http://technet.microsoft.com/en-us/library/ms188236.aspx
February 6, 2014 at 2:43 pm
Object explorer appears to be disconnected beacuse I have an option to connect and i cannot see any connections in the object exploer - its just blank !
February 6, 2014 at 2:52 pm
Close your SSMS and try reopening it as an admin. Don't click on connect. click on new query and then connect. This should work...
Is it throwing the same error message from SQLCMD as well?
February 6, 2014 at 3:00 pm
I have just tried closing ssms, reopening ssms as an admin, closing down the connection logon box, then click new query - the connect to box appears with the service account (windows authentication using the account that is running the sqlsrv.exe) and it fails to connect. Also when i try and open the sqlcmd box it opens the closes.!!!!
February 7, 2014 at 7:05 am
Something else has grabbed the single connection, an application srevice most likely. Do the following
-m"SQLCMD"
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply