I have SQL 2005 Enterprise. I changed the password to the sa account. I know
I am not using my sa account in any of my applications. And all the service
accounts are using a domain user account. Have other SQL 2005 and not getting
the error message. Not causing any known problems in my apps. Just bother's
me there is this error. Ran Profiler and capture the Audit Login Failed
event. Did a sp_who2 on the SPID. And the apps that come up I know is not
using sa account. So, really not sure where it is coming from.

On Fri, 5 Sep 2008 13:41:01 -0700, Roger
<Roger@discussions.microsoft.com> wrote:

>I have SQL 2005 Enterprise. I changed the password to the sa account. I know
>I am not using my sa account in any of my applications. And all the service
>accounts are using a domain user account. Have other SQL 2005 and not getting
>the error message. Not causing any known problems in my apps. Just bother's
>me there is this error. Ran Profiler and capture the Audit Login Failed
>event. Did a sp_who2 on the SPID. And the apps that come up I know is not
>using sa account. So, really not sure where it is coming from.

sp_who2 only shows connections that connected. Until the connection
is made it has no real SPID. The error message is that no connection
was made, so sp_who2 can only show those who did NOT cause the
message.

You could put the sa password back the way it was and see what
connects that way, or you could simply wait to see what is broken. The
exposure when changing it back is the possibility that whatever is
using sa is not authorized.

Roy Harvey
Beacon Falls, CT