Home Forums SQL Server 2012 SQL 2012 - General Connection Failed:: The target principal name is incorrect. Cannot generate SSPI context RE: Connection Failed:: The target principal name is incorrect. Cannot generate SSPI context

  • May 31, 2017 at 3:47 pm

    #1944830

    hurricaneDBA - Wednesday, May 31, 2017 3:10 PM

    Hi Sue Yes I tried that but setsnp doesn't have the option -l anymore I'll send a snapshot of the options tomorrow from the office I ran setsnp -X which is supposed to list all duplicates and the server name didn't appear in the list Kal

    According to Microsoft docs for your Windows version, it is still an option:
    Setspn

    This article has additional information on the duplicate check and different things to check:
    SPN and UPN uniqueness

    Sue