How to resolve SSPI context error without changing Service Account from MSSQL

Posted by kockiren on Server Fault See other posts from Server Fault or by kockiren
Published on 2014-03-24T08:03:31Z Indexed on 2014/06/10 21:29 UTC
Read the original article Hit count: 387

There is a issue while connecting from new Windows 8.1 Clients to SQL Server 2008 running on Windows Server 2008 R2. The SQL Service running under account Domain\mssqlservice on a machine thats works fine I get this output from setspn -l domain\mssqlservice

C:\>setspn -l domain\mssqlservice 
Registrierte Dienstprinzipalnamen
(SPN) für CN=MSSQLService,CN=Users,DC=domain, DC=local,DC=tld:
        MSSQLSvc/mssql.domain.local.tld:1433
        MSSQLSvc/mssql.domain.local.tld
        MSSQLSERVER/mssql.domain.local.tld:1433

On a windows 8.1 machine that don't work I get this output:

C:\>setspn -l domain\msssqlservice 
FindDomainForAccount: Fehler beim
Aufrufen von DsGetDcNameWithAccountW mit dem R ückgabewert 0x0000054B.
Konto kockiren wurde nicht gefunden.

On this Post I found a solution but, I can't change the Service Account who runs the SQL Service. Some application need this service delegation. But how I can realize that it works on my Windows 8.1 Clients?

© Server Fault or respective owner

Related posts about active-directory

Related posts about windows-server-2008-r2