May 12, 2008 at 8:21 am
During a 1 hr period over the weekend, SQL Agent logged a group of three errors over and over again:
Message
[298] SQLServer Error: 848, SQL Network Interfaces: The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you. [SQLSTATE HY000]
followed by:
Message
[298] SQLServer Error: 848, Cannot generate SSPI context [SQLSTATE HY000]
and then:
Message
[382] Logon to server '(local)' failed (SaveAllSchedules)
I haven't been able to find much information about these online. Anybody have any ideas?
I'm working with the networking team to determine if there was anything network-wise going on but haven't heard back from them. These problems happened for an hour and then stopped. Everything seems ok now.
Thanks,
Rob
May 12, 2008 at 8:48 am
Networking group confirmed there was some switch maintenance happening during those times.
Still... some of those messages from SQL are a bit alarming.
May 12, 2008 at 9:01 am
Those are alarming and you should definitely take action, but I guess it's a strange occurence, perhaps a half transmission of the network conversation and SQL Server isn't sure what's going on.
Thanks for the update. I'm sure someone else will run into this.
May 15, 2008 at 3:23 pm
For what it's worth I just had the same issue when a network switch went bad. After it was resolved the cluster service was a bit flaky, but after restarting the cluster service (and the network being fixed) the message has gone away.
May 15, 2008 at 3:30 pm
SSPI is related to kerberos authentication, u should check the trafice on ur router or ur firewall for any strange trafice.
..>>..
MobashA
December 4, 2008 at 5:04 pm
We also got this same error when our core routers and some switches were down for maintenace. No jobs run, no jobs show failed. What a pain.
We get the SSPI error when our domain controllers are rebooted - for a couple seconds until the server finds a new one to authenticate against.
We have alerts set up for severity 17 - 25 errors, but these didn't trigger any of them. These agent alerts didn't have the typical severity number on them though. Must a new 'containing text' alert be set up?
November 5, 2009 at 3:42 am
We had the same issue dont know what actually happened but all our logins were locked up for about 2mins and came back to normal by itself...... :w00t:
December 21, 2009 at 3:20 pm
Just had the same Issue and error....when running a wherescape red SQL Job.
Luckily we found that the account SQL services and agent were running under were locked out....Enabled the account and all is good again.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy