Mittwoch, 25. Juli 2012 23:54
An application I've installed on a client machine outputs the error "Cannot to generate SSPI context" when it tries to connect to SQL server (located on a Windows 2000 machine containing SQL server 2000 on the same domain). I've tried going through many Microsoft articles such as "How to troubleshoot the 'Cannot generate SSPI context' error message" (http://support.microsoft.com/kb/811889), but I've had no luck. The application tries to connect using a .DSN file (don't know if this is useful info). The funny thing is that I can connect fine using sql server 2008 on the client machine, but not through the application.
Any ideas? Thanks in advance.
I'm kind of a noob (as you can probably tell) and I don't know if I've supplied enough info for this issue.
Server: Windows 2000 Service Pack 4, SQL Server 2000
Client: Windows XP, SQL Server 2008 (same domain as server)
- Bearbeitet jack_bauer Donnerstag, 26. Juli 2012 15:13
Donnerstag, 26. Juli 2012 05:34
One common cause of the SSPI is that the client machine clock differs more then 5 minutes from the server time; have you already check that?
- Als Antwort markiert jack_bauer Donnerstag, 26. Juli 2012 17:25
Donnerstag, 26. Juli 2012 15:46
Thanks for your post Olaf.
Yeah, I read that somewhere. The clocks are about 2.5 minutes apart. I'm trying to adjust the clock on the client to match the server's clock, but after I apply the change it just reverts back to the previously set time. The client seems to have the correct time while the server does not. Any ideas on how I can get the clocks to match up? Thanks.
Donnerstag, 26. Juli 2012 17:24Thanks Olaf!! Changing the time seemed to have worked! I have read this solution somewhere else, but I didn't think to try it since the clocks were only about 2.5 minutes apart. Thanks!!
Donnerstag, 26. Juli 2012 17:30
Your welcome and I am glad that I could help.
And this is one of this small crazy issues causing grey hairs; it could drive someone nuts ... just this little silly clock.
Sonntag, 2. September 2012 21:41
thanks OlafThe problem has been resolved because of the different date and time