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.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ryan McCauleyEnterprise Analytics ManagerCommented:
Yes, you should be able to ignore this error since you've created the SPN manually - it's just telling you that the service account isn't able to create/refresh the SPN on its own. To verify that you're connecting with Kerberos, you can use the following query:

SELECT auth_scheme FROM sys.dm_exec_connections WHERE session_id = @@spid

If that says "Kerberos" instead of "NTLM" then you're covered. To further confirm (assuming you have a second SQL Server handy), set up a new linked server and set the Security to "Be made using the login's current security context" - this will tell SQL Server to impersonate your login to the second server. For this to work, the service account has to have a proper SPN to connect as you through one server to another - if you can verify the connection, then you've got a proper SPN and Kerberos is working.

It might be worth figuring out why you can't create an SPN though - take a look at this:


Ensure your SQL Server service is running as a domain account (but not a domain admin - that's a bad idea, as it seems you know) and then troubleshoot the error details a bit further.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Anthony PerkinsCommented:
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,
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.