Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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:

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?

share|improve this question

I don't know if this fix works for everyone, but deleting all the SPNs with MSSQLSvc fixed it for me.

setspn -d [spn name] [server name]

With this you don't have to run it as local system. You can run it with a domain account.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.