January 6, 2016 at 1:21 am
Hi Experts,
Getting below alert on SCOM.
SQL Server cannot authenticate using Kerberos because the Service Principal Name (SPN) is missing, misplaced, or duplicated.
Please advise.
January 6, 2016 at 8:31 am
January 6, 2016 at 9:24 pm
To fix this problem you need to update the MP to the SQL related MPs 6.6.4.0
January 7, 2016 at 2:38 am
Thanks Guys,
Added SPN success fully but still getting below error in SQL Error log.
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/ABC-SYS.sys.abc.in:5432 ] for the SQL Server service. Windows return code: 0x2098, state: 20. 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.
Used below script to add SPN
SetSPN -S MSSQLSvc/MSSQLSvc/ABC-SYS.sys.abc.in:5432 abc\rkn
SetSPN -S MSSQLSvc/MSSQLSvc/ABC-SYS.sys.abc.in:2014 abc\rkn
January 10, 2016 at 12:54 am
Anyone on this
January 10, 2016 at 1:27 am
Quick question, did you just add the SPMs or did you remove them before adding them again?
😎
The article benjamin.reyes posted a link to has good instructions on how to handle this problem.
January 11, 2016 at 9:36 pm
Eirikur Eiriksson (1/10/2016)
Quick question, did you just add the SPMs or did you remove them before adding them again?😎
The article benjamin.reyes posted a link to has good instructions on how to handle this problem.
Thanks Eirikur,
Added SPN after checking whether SPN exists.
January 12, 2016 at 1:49 am
The errors in SCOM does not goes away instantly.
I have to wait for some time for the error to go away, may be you need to contact your SCOM administrator.
January 14, 2016 at 10:25 pm
This was removed by the editor as SPAM
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply