July 19, 2007 at 3:30 pm
Hi All,
I have a client who has a 2003 domain server with SQL database loaded on it. It's been working fine for over three years, but after a weekend, they have 3 stations that will log into their SQL program, but will give a SSPI Context error after anywhere between 20min. to 1hour. The other 5 stations have been working fine, but as of today there is one more station that has began giving the same SSPI errors. The only fix is to log out of windows, and log back in, but this is not practical. Any ideas on what could be causing this, and more to the point how to fix it since it seems to be spreading.....
July 19, 2007 at 4:34 pm
It's a domain token issue. Check the times on those workstations v the server, sometimes if they're out of synch you get this.
July 20, 2007 at 7:34 am
The time is maybe off by a few seconds. Is that enough to still cause this? They also just lost another workstation that is getting the same issue....
July 20, 2007 at 8:17 am
A few seconds shouldn't matter. I've seen this typically when I've changed a service account on a server. You can search for the SETSPN utility and try to reset the SPN of the SQL Server on the AD network. That might work.
You might need to call MS. These can be tricky to track down.
July 23, 2007 at 4:38 am
I have seen this error when the windows account has locked out and SPN problems.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply