Link to home
Start Free TrialLog in
Avatar of VSACIT
VSACIT

asked on

When a SQL 2012 was setup in a domain if a SPN creation error is in the SQL error log and the SPN is created manually and the error still occurs in the log is that an issue?

I have a VMWare Windows 2012 R2 server running SQL 2012 and I keep getting the below error. If I manually create the SPN can I ignore this error? I can make it go away by using a domain administrator account to start the SQL Service but I do not like this option. Attached is the SQL Error log

The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Server.domain.org ] for the SQL Server service. Windows return code: 0x21c7, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
ASKER CERTIFIED SOLUTION
Avatar of Ryan McCauley
Ryan McCauley
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If that says "Kerberos" instead of "NTLM" then you're covered.
There is one other wrinkle:  You need to ensure that the Windows account used for the linked server has delegation enabled,