April 12, 2010 at 6:45 am
I added -m; at the beginning of the startup parameters to start the server in single user mode. I then restarted the server. When i tried to connect to the server, I'm getting the below message
"Login failed for user 'DomainName\Admin'. Reason: Server is in single user mode. Only one administrator can connect at this time. (.Net SqlClient Data Provider)"
I tried connecting using sqlcmd. But the same meesage came up.
I stopped all the services[text search, analysis, integration, reporting].
No applications are using this server.
Any idea would be appreciated....
April 12, 2010 at 6:47 am
did you also stop SQLAgent? Is this a cluster?
---------------------------------------------------------------------
April 12, 2010 at 6:48 am
No its not on cluster. I stopped the Agent as well.
April 12, 2010 at 7:56 am
try starting in multi user mode, connect and see if you can spot any other connections.
---------------------------------------------------------------------
April 12, 2010 at 8:54 am
I once faced similar issue and found that one of the applications was continously trying to connect to db. As soon as i restarted server, that app would connect to the database.
I disabled the tcp/ip and then i was able to connect.
April 12, 2010 at 10:09 am
Although the server is having mixed authentication mode, Builtin\Administrators are not part of server admins.We forgot the sql authentication password. So I'm trying to start the box is single user mode so that I can add admin. I even tried disabling TCP/IP and enabling only Shared Memory. But everything was invain 🙁
December 6, 2013 at 2:19 am
There is a small trick which can be used http://sqlserver-help.com/2013/12/06/help-how-to-fix-error-reason-server-is-in-single-user-mode-only-one-administrator-can-connect-at-this-time/
December 6, 2013 at 2:21 am
Please note: 3 year old thread.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 6, 2013 at 8:05 am
GilaMonster (12/6/2013)
Please note: 3 year old thread.
Thanks for the comment. I didn't realize that. Apologies if its incorrect to add a solution to old thread.
One of my customer opened ticket today and he was pointing to this post and told that he is also facing same issue but none of the replies helped. Since I helped him today and wrote a blog, i added a reply.
December 6, 2013 at 8:25 am
if it adds to a thread and completes it by providing a solution I cannot see a problem, might help someone in trouble in the future who comes across the URL in their search.
ITs when people post their issue in an old thread or just repeat something already stated its not best etiquette IMHO.
---------------------------------------------------------------------
January 12, 2016 at 2:15 am
Stop SQL services with command "net stop mssqlserver" and go windows console for create a windows local user with admin access and now go to sql services properties and add this new user created account. Now start SQL services as ''net start mssqlserver /m'' as single user mode and take the sql access with SQLCMD ''sqlcmd -S LocalHost -d master -A'' command. Now run the command "DROP TRIGGER trigger_name ON ALL SERVER
GO
"
and now you are done..restart the sql services as normal ''net start mssqlserver "
Thanks
Subhash
January 13, 2016 at 6:19 am
Please note: 3 year old thread.
January 14, 2016 at 3:27 pm
In management studio, right click on the SQL server and select disconnect.
The Object Explorer is a separate connection to the query window.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply