Login failed for user 'sa'.

From: Gordzilla (gordzilla2000_at_hotmail.com)
Date: 08/21/04 

Date: Sat, 21 Aug 2004 00:12:23 -0400

SQL was running along fine. Changed the service account from local system
to a Domain user account using Enterprise Manager.
Everything worked fine and all databases are accessible. However, my event
log is filling up with the following every 6 seconds:

Event Type: Information
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 17055
Date: 8/20/2004
Time: 10:47:47 PM
User: N/A
Computer: XXXX
Description:
18456 :
Login failed for user 'sa'.

Any ideas?
SBS2000 box running all service packs including SQL SP3

Relevant Pages

  • sql service password in cluster changed by wrong method
    ... Then she changed it back to the domain user account using ... the Services applet. ... to be done within the SQL Enterprise Manager. ... Service Account through the SQL EM, tried to change the password and we get ...
    (microsoft.public.sqlserver.clustering)
  • Re: Change the domain setting for the MS SQL 2000 Server
    ... The reason why I did not post that solution is that SQL ... service account using ... I can set the service setting to use ... >> or to use a domain user account. ...
    (microsoft.public.sqlserver.server)
  • Re: SPN for SSL over common name
    ... you can't register those SPNs under the SQL Server's ... service account is the MSSQL SPN. ... That SPN should be registered under ... Lastly, since the SQL Server is not being used for delegation anywhere, ...
    (microsoft.public.inetserver.iis.security)
  • Cannot Use Non-Administrator Account to Start SQL Server and Force Encryption
    ... I changed the service account of a named instance (product ... a certificate from a Microsft Certificate Server ... the SQL Service. ... SQL Server could not spawn FRunCM thread. ...
    (microsoft.public.sqlserver.security)
  • Re: Builtin Administrators Group and SQL Agent Jobs
    ... > I checked and 'Change a process level token' and 'Act as> part of the OS' were not granted to the service account. ... >>> All jobs are owned by SA and the problem remains. ... >>>>> for DBA's and gave that login full access to all SQL ...
    (microsoft.public.sqlserver.security)