No, the SQL server agent service is stopped.
Even when I change the startup parameters and start SQL server from Management Studio, I get the same error.
Thanks,
Main Topics
Browse All TopicsHi all,
Hopefully this is a straightforward question.
I need to execute "DBCC CHECKDB" on my database, but to do so, I must be in single-user mode.
I know how to start the database in singleuser mode from the command line by typing "sqlservr -m", but when I try to access the database using SQL Server Management Studio, but it gives me the message "Login failed for user 'DOMAINNAME\administrator'
Any ideas on how I can go about executing DBCC?
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
krinpit,
Have a look at http://blogs.msdn.com/sql_
Also, have you checked for other services/applications/user
cheers,
Business Accounts
Answer for Membership
by: fostejoPosted on 2007-01-18 at 05:02:22ID: 18340377
krinpit,
/en-us/lib rary/ms188 236.aspx
It's likely that the SQL Server Agent is using the only available connection, as described in http://msdn2.microsoft.com
cheers,