Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

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

Using SQL Server 2012 on Windows 2008 R2

I have been getting errors in SQL Logs for failed login for NT AUTHORITY\SYSTEM.

All of SQL Server's services are running under their own Domain accounts, except for SQL Server Browser service. Once I had shut down this service, the errors immediately stopped and so I believe this was the cause.

I believe there are three(3) solutions to this:

  1. Giving database permissions to NT AUTHORITY\LOCAL SERVICE account
  2. Running this service under a different account
  3. Using a non-dynamic port and disabling this service

However, here are my questions :

  • Why is this service attempting to logon to databases? I thought, its purpose was simply to allow users to logon to SQL server using an alias instead of IP address
  • What is the best solution to this error?

Thank you!

share|improve this question

closed as off-topic by Max Vernon, bluefeet, RolandoMySQLDBA, Mark Storey-Smith, Kin Oct 4 '13 at 20:47

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background)." – Max Vernon, bluefeet, RolandoMySQLDBA, Mark Storey-Smith, Kin
If this question can be reworded to fit the rules in the help center, please edit the question.

Well, I agree it should not connect to SQL Server. However, I would a low privilege service account to run it only if you need it Or use only default instance or use ports in connection strings to avoid it completely. – gbn May 9 '13 at 14:53