Post reply

Cannot Generate SSPI Context

  • March 12, 2012 at 11:12 am

    #252428

    Hi,

    I'm receiving the below error when trying to connect to SQL Server 2008 R2 from a remote computer on the network using windows authentication. But i was able to connect with SQL Server authentication.

    "Cannot Generate SSPI Context"

    Thanks,

  • March 12, 2012 at 1:57 pm

    #1458167

    The MSDN website has a step by step procedure to trouble shoot this. Take a look at this URL.

    -Roy

  • March 12, 2012 at 2:31 pm

    #1458187

    Thanks Roy! The following fixed the issue.

    1.Switched the sqlserver service logon account to ‘Local System’

    2.Rebooted the server

    3.Switched the sqlserver service logon account to ‘Domain/Account’

    4.Rebooted the server

  • March 13, 2012 at 2:28 am

    #1458325

    I've also seen this also happens when SQL starts before AD.

    In an old job, the AD servers took ages to come up after testing a scheduled power outage, say they took 10 minutes to boot, but SQL only took 5 minutes, just a simple restart of the SQL services resolved it for us once AD was back up and running, just incase you ever run into something like this.

  • March 13, 2012 at 7:29 pm

    #1458960

    Hm..That's good to know. Thanks for sharing it.

  • July 18, 2012 at 1:58 pm

    #1514529

    Thanks that was helpful.

  • August 4, 2014 at 4:52 am

    #1734786

    Although 2 years later, still very useful to me. Many thanks! 🙂

  • April 25, 2016 at 7:48 am

    #1874236

    We encountered this error recently - rather out of the blue - no good reason for it really. The service account stopped sending out Service Provider Name information to the domain. This resulted in any connection using domain permissions from connecting to the SQL 2008 instance. We tried switching to Local Service Account but that did not fix the issue. After playing with the SetSPN.exe, which we never got to manually issue the SPN info, we changed the service account to another domain account and it fixed the issue. We believe it has something to do with the "Include Inheritable Permissions from the Object's Parents" of the domain account security but why it changed is unknown.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply