Login failed for user ‘NT AUTHORITY\SYSTEM’. [CLIENT: ]

    Problem

    You receive hundreds if not thousands of NT Authority\SYSTEM "Login failed for user ‘NT AUTHORITY\SYSTEM’. [CLIENT: <local machine>]" error messages

    clip_image001

    Errors often occur every minute

    clip_image002

    Explanation

    You’ve probably deleted your Shared Service Provider or created a new one. Unfortunately, some scheduled jobs will remain on your SQL server that reference the now defunct database.

    Solution

  • Launch SQL Server Management Studio and connect to the server that houses your Shared Service Provider
  • Within SSMS expand the SQL Server Agent and select jobs.
  • Locate the jobs that have names that end in "_DeleteExpiredSessions"
  • clip_image003

  • You in the "Steps" tab double click on the first step and check to see if there’s a database, if there’s no database selected you’ve probably deleted said database so you can safely disable the job.
  • clip_image004

  • If you don’t understand these instructions or are confused then STOP! Disabling SQL jobs is dangerous business and can cause undesired outcomes.
Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: ]7.0103

Popularity: 62% [?]

Share and Enjoy:
Share this Post:

6 Responses to “Login failed for user ‘NT AUTHORITY\SYSTEM’. [CLIENT: ]”

  • SantoshKumar says:

    i do got the similar error
    and done the things as per your suggestions but still the same error

  • Ryan Pighin says:

    I am getting the same error except my SQL Server Agent is disabled

  • Chris Cady says:

    Worked like a champ!!!

    Was able to locate the stale SQL job and disable it very quickly using your screenshots.

    Thank you so much!

  • Leave a Reply:

    Name (required):
    Mail (will not be published) (required):
    Website:
    Comment (required):
    XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>